• Locked Locked
  • Replies 1 reply
  • Subscribers 54 subscribers
  • Views 518 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.

DRV8301-RM48-KIT demo code runs, code compiles, but cannot erase flash/load debug code

Scott Johnson1
Prodigy 10 points
Other Parts Discussed in Thread: MOTORWARE

Hello folks,

I was very excited to receive my kit. After I installed CCS 5.2 and all of the guicomposer demo code, everything was great. The motorware demos worked out of the box.


But after wasting many hours over the last couple of weeks, I simply cannot coax CCS to debug the code. I can compile, always with two cryptic warnings. It appears to link without errors. I can test the connection to the board ... no problem. But when I start the debugger, it either fails to erase the flash, and aborts trying to load the code, or it seems to load the code, but many of the watch variables are not found.

If I can't program on it, this $500 evm is worth nothing.  I would really appreciate any help you can offer. This experience has been dismal. Thank you in advance.

Scott

  • TI__Guru**** 171309 points

    Scott,

    Can you do a complete rebuild and attach a text file with the output of the project you are building (the one where you see two cryptic warnings)? I wonder if something was missing and a .out was not generated.

    Also, can you try to manually connect to the board and see if you are able to access memory, registers, etc? For details on that, check the short clip below:

    Also, how is CCS configured? According to this page, the debugger built into the development kit is an isolated version of the XDS100v2, which can reduce the overall debug speed. In this case you could always try to reduce the JTAG TCLK speed on the target configuration file you are using and see if the connection is more stable (for details check this post). 

    One last remark: CCSv5.2 is rather old and several bugs were fixed in the latest releases, especially in the emulation device drivers (which directly affects the debugging experience). If the target configuration file I mentioned above is ok, I would download and install an updated CCSv5 release (which has updates to the emulator device drivers, the debugger, etc.) and see if you are able to properly debug on the board.

    If you install this new release in a different directory and use a different workspace you will not have any problems in damaging your existing CCSv5.2 install.

    Hope this helps,

    Rafael