Jump to content

StefanSch

Members
  • Content Count

    25
  • Joined

  • Last visited

  • Days Won

    2

StefanSch last won the day on January 10

StefanSch had the most liked content!

1 Follower

About StefanSch

  • Rank
    Member

Recent Profile Visitors

338 profile views
  1. When using the latest version of Energia the wire (I2C) has now the function setClock to set to 400k use setClock(400000UL);
  2. Hm, did you move the shortcut or die Energia folder to the desktop. Strange questions but have no other ideas.
  3. Are you using the lastest version of Energia or have you patched this lib into an older one? Your references to the lib files confuses me a little bit.
  4. the Software Serial lib is for devices without hardware serial module integrated.This device has a hardware serial module. Just use Serial like in the standard examples shown.
  5. As mentioned Engeria is already configured to start and LFXT - this of course means to enable the PORTJ pins for the XTAL functions. So LFXT should start if you have connected an LFXT properly. For HFXT you can go the the page (linked above) and take this peace of code and put in into your Energia setup function: PJSEL0 |= BIT4 | BIT5 | BIT6 | BIT7; // For XT1 and XT2 // Disable the GPIO power-on default high-impedance mode to activate // previously configured port settings PM5CTL0 &= ~LOCKLPM5; CSCTL0_H = CSKEY_H; // Unlock CS registers CSCTL4 |= LFXTDRIVE_3 | HFXTDRIVE_3; CSCTL4 &= ~(LFXTOFF | HFXTOFF); do { CSCTL5 &= ~(LFXTOFFG | HFXTOFFG); // Clear XT1 and XT2 fault flag SFRIFG1 &= ~OFIFG; } while (SFRIFG1 & OFIFG); // Test oscillator fault flag CSCTL0_H = 0; // Lock CS registers It does set the PORTJ for the LFXT again but this does not hurt. If you do not come out of this part of code then you have an issue with the Oscillator. Esp. for the HFXT you need to check for the right load capacitors !!! Then once they are running you can select which internal clocks should use it: e.g. CSCTL2 = SELA__LFXTCLK | SELS__HFXTCLK | SELM__DCOCLK;
  6. Sounds very strange. Might it be possible that some defender software is blocking some parts of Energia, e.g. java?
  7. The LFXT (32kHz) will be started automatically if a crystal is detected. The HF needs to be started manually with accessing the control register of the clock. Example codes can be found on TI web page or in the Resource Explorer: e.g. http://dev.ti.com/tirex/explore/node?node=AEx-fMK50j-eiYFtcGa.aw__IOGqZri__LATEST
  8. The FR5969 use a hardware serial interface and the buffer size is set to 16 byte here. Do do not think that this would be the issues as while data coming in also data a take out of the buffer from the software. Of course you can give it a try with a bigger buffer - just check the HardwareSerial.cpp file. Note: take the one in the Energia update directory: e.g. for windows c:\Users\xxxxxxxxx\AppData\Local\Energia15\packages\energia\hardware\msp430\1.0.5\cores\msp430
  9. Which device are you using with the launchpad. This devices are having quite low memory and with using such a big function like printf the memory can easily overflow.
  10. May have a look at this post: https://e2e.ti.com/support/data-converters/f/73/t/639597?ADS7142-Library-or-I2C-details-for-ADS7142
  11. Hi, can you provide some example code showing this issue.
  12. Error says it can not find the executable for DSLite. Have you checked if the file is there. Maybe there was in issue and the tool DSLite did not even got installed.
  13. This line should also not be there. #include <SoftwareSerial.h> The F5529 has a hardware UART for the Serial. The SoftwareSerial.h is only used internally in Energia on devices where a Hardware UART is not available.
  14. Hi, I2C should now also be solved. The fix is pushed the github. But the master there has a lot of fixes and cleanup so that it is not easy to take the file in put it into the current release as fix. The here attached version should do that but could not test it on the current release version so far. If you like to give it a try i would be happy on any feedback. twi.c
  15. To solve the UART issue go to the pins_energia.h file for the selected device MSP-EXP430G2452LP and try to update / modify this lines: static const uint8_t DEBUG_UARTRXD = 4; /* Receive Data (RXD) at P1.2 */ static const uint8_t DEBUG_UARTTXD = 3; /* Transmit Data (TXD) at P1.1 */ This seems to be wrong in the current version but i have no idea why this worked before as i could not find an update where this has been changed. To solve the issue with I2C you need to select the other I2C interface with setModule(0); The default mapping of the I2C interface to the pins 8 and 9 change a while ago but with the setModule you still can select the other I2C interface if available.
×
×
  • Create New...