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.
CCS 4.2.0
SD510 USB jtag
C28335 Micro
Sys/Bios 6.31.00.18
XDCTools 3.20.05.76
I am having problems getting motor control data from the debugger into a spreadsheet with Cut (actually Copy) and paste.
I can not copy from the memory window. Data highlights, but does not transfer to the clipboard.
I can copy some data from the watch window by rt clicking and selecting all and ctrl C, but with an array of 500 items about 200 entries are not copied. I can recopy a few times and get more entries but then I have to rearrange them in the text file and manually add the missing data.
I tried graphing the data and exporting a graph, but that failed too. No files were created in the selected folders. I was able to copy the graph to a word document.
I have not seen these issues corrected in release notes for later CCS(4.2.2) releases. Are others having the problem?
Any ideas on how I can get data from the debugger more reliably?
Thanks,
Jan
Jan Stefan said:I can not copy from the memory window. Data highlights, but does not transfer to the clipboard.
you can copy and paste from the memory window via context menu. It does indeed work for me (I tried in 4.2.1) as i was able to copy to the clipboard and paste in my text editor.
Jan Stefan said:I can copy some data from the watch window by rt clicking and selecting all and ctrl C, but with an array of 500 items about 200 entries are not copied. I can recopy a few times and get more entries but then I have to rearrange them in the text file and manually add the missing data.
For this much data, would it be better to look up the array address in the memory view and do a memory save to a file ("Save Memory" in the context menu as seen above)?
Sorry for the slow response.
My target hardware was shipped to a customer and we shifted to another subsystem for a while.
Yes, I was using the ctrl C shortcut rather than a context menu.
Our Motor Control Expert was waiting for captured data and we had already failed at exporting as graphed and watched data.
Thanks for the response.
I will try to explore deeper in the future prior to posting.
Jan