• State Resolved
  • Locked Locked
  • Replies 10 replies
  • Subscribers 78 subscribers
  • Views 1765 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

MSP430FR5739: Codebase size causes FET failure: MSP430: Failed Soft Reset: Could not communicate with FET

soren
Prodigy 140 points
Part Number: MSP430FR5739
Other Parts Discussed in Thread: UNIFLASH, MSP430WARE, MSP-EXP430FR5739

Hi,

I am pretty stumped on this one. I am trying to program the MSP430FR5739 (connected to a EXP-MSP430FR5739 board); initially everything went fine, but at some point it failed when flashing the code.
If I commented out section of the code, it was able to flash the chip. From what I can tell, it is related to the output size.

To make sure it was not RAM issue, i bumped the stack size. Even at 768 bytes, I still got the error. It seems to be related to how it allocates the FRAM on the chip. I am not familliar enough with the .cmd file syntax that I am able to figure out how to adjust code base size (.text?).

Looking at the CCS Memory Allocation view, I can see the total FRAM is 15744 bytes (as expected). In total 2184 bytes are in use (13%), but it still fails. If I comment out sections of my code, the FRAM usage drops to 1864 bytes (11%), it works correctly.

Is there any way I can tweak the memory allocation to allow for larger code base? 13% utilization should not be that big of an issue IMHO. The .cmd file is default generated by CCS; however I tried to define __LARGE_CODE_MODEL__ but it did not help.

I have very few constants defined and I dont need a lot of memory, I just need more programming bytes.

Thanks!

Edit: I have uploaded the two project files. One is able to debug just fine, the other fails with the "MSP430: Failed Soft Reset: Could not communicate with FET" error. The only difference is PPM.c line 43 is commented out in the working version. It is setting a single value in a struck; it cannot be the source of the failure.

I also tried to use UniFlash to flash the .hex file to the chip; with exact same error message.

PPMEncoder_notworking.zipPPMEncoder_working.zip

  • 0
    Prodigy 140 points
    The MSP430 Flash tool does not indicate any issue and firmware is apparently current.

    C:\ti\msp\MSP430Ware_3_80_05_04\msp_flasher>MSP430Flasher.exe
    * -----/|-------------------------------------------------------------------- *
    * / |__ *
    * /_ / MSP Flasher v1.3.10 *
    * | / *
    * -----|/-------------------------------------------------------------------- *
    *
    * Evaluating triggers...done
    * Checking for available FET debuggers:
    * Found USB FET @ HID0012:COM4 <- Selected
    * Initializing interface @ HID0012:COM4...done
    * Checking firmware compatibility:
    * FET firmware is up to date.
    * Reading FW version...done
    * Setting VCC to 3000 mV...done
    * Accessing device...done
    * Reading device information...done
    *
    * ----------------------------------------------------------------------------
    * Arguments :
    * ----------------------------------------------------------------------------
    * Driver : loaded
    * Dll Version : 20409001
    * FwVersion : 30394216
    * Interface : TIUSB
    * HwVersion : E 2.0
    * JTAG Mode : AUTO
    * Device : MSP430FR5739
    * EEM : Level 5, ClockCntrl 2
    * VCC OFF
    * ----------------------------------------------------------------------------
    * Powering down...done
    * Disconnecting from device...done
    *
    * ----------------------------------------------------------------------------
    * Driver : closed (No error)
    * ----------------------------------------------------------------------------
    */
  • 0 in reply to soren
    TI__Expert 6635 points
    Hi Soren,

    I am looking into this and will provide updates as soon as I can.

    Thanks,

    Mitch
  • 0 in reply to Mitch Ridgeway
    Prodigy 140 points

    HI Mitch,

    Did you have any luck reproducing/fixing this? If you take any of the provided examples and paste in a few hundred lines of code (e.g 200 x PJOUT ^= BIT0;), it comes up with the same failure.

    Thanks,

    Søren

  • 0 in reply to soren
    TI__Expert 6635 points
    Hey Soren,

    I was able to program the FR5739 device (also using the EXP-MSP430FR5739 board) with both projects you provided.

    I also tried copying and pasting several hundred (about 250) lines of code to a blinking LED example and am showing that I am also using 13% of FRAM. I was able to build this project and run it.

    A few things we can do to try to narrow down the cause:
    Have you tried a different FET?
    Can you program other Launchpads with the same FET with no errors?
    Have you tried a different USB port?

    Thanks,

    Mitch
  • 0 in reply to Mitch Ridgeway
    Prodigy 140 points

    Hi Mitch,

    Thank you for looking into this.

    Q: Have you tried a different FET?
    A: No, unfortunately the only FET I have is the one on the board.

    Q: Can you program other Launchpads with the same FET with no errors?
    A: I have not tried. I do have some older MSP's I might be able to try with. The strange thing is that it works up to a certain limit; then it fails with the error message.

    Q: Have you tried a different USB port?
    A: Yes. I even tried to install CCS 8.2 and MSPware on a Windows 7 machine to see if it was a Windows combability issue. It had the exact same results.

    - I did not solder the 32k crystal in, since my project does not use it; is it by any chance required for the FET to work correctly?

  • 0 in reply to soren
    TI__Expert 6635 points
    Hey Soren,

    No, a 32kHz crystal isn't required for the FET to operate properly. I am curious to see if you see this problem with a different FET, but I know you don't have access to one at the moment.

    When you say you have older MSPs, are these older Launchpads or only the physical ICs? De-soldering and re-soldering ICs might introduce more risk into the setup.

    Thanks,

    Mitch
  • 0 in reply to Mitch Ridgeway
    TI__Expert 6635 points
    Hey Soren,

    Are you still having issues? If not I will close out the thread.

    Thanks,

    Mitch
  • 0 in reply to Mitch Ridgeway
    Prodigy 140 points

    Hi Mitch,

    I have another MSP-EXP430FR5739 board on the way; it should arrive early next week. Hopefully it will resolve the issue.

    Have a nice weekend,

    Søren

  • 0 in reply to soren
    TI__Expert 6635 points

    Hey Soren,

    Thanks for the response. Please let me know if you continue to have issues.

    Thanks,

    Mitch

  • 0 in reply to Mitch Ridgeway
    Prodigy 140 points

    Hi Mitch,

    I received the new MSP-EXP430FR5739 board today - it works perfectly. Connected it and pressed the debug button and it flashed just fine. It must have been an issue with the other board.

    I don't have a use for the suspect board - would you be interested in receiving it for troubleshooting?

    Thank you for helping resolving the issue.

    Best regards,

    Søren

**Attention** This is a public forum