• Locked Locked
  • Replies 2 replies
  • Subscribers 53 subscribers
  • Views 297 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMS320VC5501 debug with TMS100v2 on CCSv4

Kevin Vap
Intellectual 1980 points

A customer  has reported the following:

We're trying to debug a C5501 system with a TMS100v2 running Code Composer Studio v4.2.3 and coming across issues with it.   Previously we used CCS v3.x successfully, but new computers require upgrade to CCSv4.  The XDS100 is new to us.

Our assembly only project either returns an error saying "Can't Single Step Target Program" or "Trouble Writing Register PC" or "Trouble Writing Memory Block" when trying to start debug. From what  I can gather, this seems to be a problem with our lnk.cmd file. These errors occur when using the memory sizes and addresses that we've been using for many years on this project, essentially allocating all of it within RAM.

I've tried using the file included with Code Composer Studio for the C55xx series, but that doesn't work either, citing problems with relocating symbols overflowing on building (rather than debugging).

Do you know of any specific settings that we would need to set to get this to work properly? Do the BOOTM pins set to boot from the I2C EEPROM prevent the JTAG emulator from working? Or is this strictly a problem with our linker file? 

Any suggestions what could cause this?  I'm checking on the lnk.cmd file to look for problems.  It seems to be a conversion to CCSv4 environment that is not yet understood.

Thanks for any assistance. 

  • TI__Guru**** 162305 points

    Kevin,

    If they take the .out that was created with 3.3 and load it using v4 does the problem still occur?  The reason I ask is that I am trying to tell if the problem is with the way the project is being built in CCSv4 or if it is an issue debugging with XDS100.  If the 3.3 generated .out works fine that points to a build related issue.

    As far as the BOOTM pin question you may need to ask some on the C5000 team.

     

    Sorry for the late response on this one it came in after the Aug 1 holiday and we missed it.

    Regards,

    John

     

  • in reply to JohnS
    TI__Intellectual 1980 points

    John,

    Thanks for following up.  I've forwarded the question, but haven't received feedback on it.  I believe the customer is temporarily on a higher priority task and will get back to this soon.

    -Kevin