• Locked Locked
  • Replies 5 replies
  • Subscribers 53 subscribers
  • Views 1469 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.

Trouble loading MSP430G2352 code into Launch Pad

Bob Shaw
Prodigy 70 points
Other Parts Discussed in Thread: MSP430G2352

I am using CCS4.2 with the TI Launch Pad.  I have been having an increasing amount of trouble getting the code to load into the target when I click on “debug active project”.  It appears that as the code grew, I more frequently got error messages that the target could not be written to:

-Trouble writing memory: cannot write to target

-Trouble writing memory block at 0xfcd2 on page 0 of length 0x8: could not write device memory

 

In addition, if I do get the code to load, I often get the message:

-Could not run target CPU: could not run device (to breakpoint)

Except that I have no break point set.

 

My target is MSP430G2352.  My include file is msp430G2352 and the .ccxml file is MSP430G2352.  My code size is text-3246 and data48 (yes, I know I am pushing 4k, but not there yet).  I have upgraded my computer to the CCS required 1G memory (actually3G).  Any ideas?

Thanks,

Bob Shaw

soaked_site@powerc.net

  • TI__Guru**** 169894 points

    Bob,

    I've been heavily using my launchpad and did not yet have any connectivity troubles with it - although I am still using the standard G2231 part with close to 2kB of memory.

    One thing that I would check is the USB cable itself - flash writing is heavily dependent on the power supply to the board and, being USB powered, that would be my first suspicion.

    Regarding the breakpoint, whenever you connect to the target a breakpoint is set - either at main() or at the entry point _c_int00 (otherwise the device would start running free after the code is loaded). Again, this may be due to the poor connectivity issues.

    I'll check around and see if anybody has been having trouble with that too.

    I can try to get a G2352 part and test it out here, but that will take a few days.

    Cheers,

    Rafael

  • in reply to desouza
    TI__Guru*** 130875 points

    Hi Bob,

    where have you verified your code size?  Have you checked the map file to ensure you are not going over memory for an allocated memory segment?  Also look at the linker command file.

    If you have been continuously rebuilding, have you tried a fresh workspace in case of simple corruption?

    Best Regards,
    Lisa

  • Prodigy 70 points

    I got the code size from the message at the bottom window in the debugger (if and when the code does load).  This also seems to check out with the map file.  I have tried a new project file within the same workspace and it seemed to help a little (I suspect that this was only a coincidence).  Even with the new project file, I still have some trouble getting the code to load.  I tend to lean toward the suggestion from Rafael regarding the USB cable, although I am not sure what the solution for that is.

  • in reply to desouza
    Prodigy 70 points

    See rply to Lisa.  Any suggestions on how to improve the connectivity?

  • in reply to Bob Shaw
    TI__Guru*** 130875 points

    Hi Bob,

    if you want to check the cable you could try a new one or a different USB port.  I have found the occassional USB port giving me issues with CCS at times for some reason.

    Also it may be work just double check/investigating exactly whether the issue is linked to something like ... code size, hardware or software ...etc.  Ie try to isolate things.

    Please keep us posted.

    Best Regards,
    Lisa