Forums

TI DM642 JTAG Emulation Just Stops

Started by Randy Yates July 9, 2005
Hi Folks,

I had a strange experience this past week (well, maybe not so strange
for TI...) in which I started a fresh copy of Code Composer Studio
(I'm using 2.18, I think), so that there were no breakpoints or other
debugging session setup, and then loaded and ran (via F5/Run) an
executable into a TMS320DM642. Then during the processing of
subsequent host processor messages (via the PCI bus interface) the
emulator "just stopped." It was in the middle of a perfectly
legitimate portion of the code.

Has anyone seen this behavior before and can you give an reason
for it?
-- 
%  Randy Yates                  % "With time with what you've learned, 
%% Fuquay-Varina, NC            %  they'll kiss the ground you walk 
%%% 919-577-9882                %  upon."
%%%% <yates@ieee.org>           % '21st Century Man', *Time*, ELO
http://home.earthlink.net/~yatescr
There are lots of bugs with CCS 2.18 and 2.2, I even found some
compiler bugs, Try with CCS 3.0
I am using it for last 6 months, its better.

Regards,
Soumit Mukherjee

>There are lots of bugs with CCS 2.18 and 2.2, I even found some >compiler bugs, Try with CCS 3.0 >I am using it for last 6 months, its better. > >Regards, >Soumit Mukherjee > >
Soumit is very right about CCS2.18 CCS2.1x has been found to be very buggy by many people, so I would recommend either CCS2.21(most stable of CCS2.x versions and possibly updatable from your current installation through update advisor)or if you can take it one step further, go for CCS3.1 for best results, instead of CCS3.0! --Bhooshan This message was sent using the Comp.DSP web interface on www.DSPRelated.com
"bhooshaniyer" <bhooshaniyer@gmail.com> writes:

>>There are lots of bugs with CCS 2.18 and 2.2, I even found some >>compiler bugs, Try with CCS 3.0 >>I am using it for last 6 months, its better. >> >>Regards, >>Soumit Mukherjee >> >> > > Soumit is very right about CCS2.18 > > CCS2.1x has been found to be very buggy by many people, so I would > recommend either CCS2.21(most stable of CCS2.x versions and possibly > updatable from your current installation through update advisor)or if you > can take it one step further, go for CCS3.1 for best results, instead of > CCS3.0! > > --Bhooshan
Hi Bhooshan and Soumit, Thank you for your responses. I am constrained to 2.18 right now for certain reasons. However, I am curious why you think that the first minor version of a major release will work better than the 18th minor version of a major release. I have heard that TI rethought the JTAG interface in 3.x with regards to power and reset anomalies with a greatly improved the user experience in these situations. That certainly will be welcome when I can move to 3.x. I can believe the latest compiler version will be improved since I would think it progresses more-or-less linearly and independent of the debugger, but I don't think this is a compiler bug. Also, I was hoping someone could apeak to this specific anomaly rather than generalize. -- % Randy Yates % "Watching all the days go by... %% Fuquay-Varina, NC % Who are you and who am I?" %%% 919-577-9882 % 'Mission (A World Record)', %%%% <yates@ieee.org> % *A New World Record*, ELO http://home.earthlink.net/~yatescr
Randy Yates wrote:

> Hi Folks, > > I had a strange experience this past week (well, maybe not so strange > for TI...) in which I started a fresh copy of Code Composer Studio > (I'm using 2.18, I think), so that there were no breakpoints or other > debugging session setup, and then loaded and ran (via F5/Run) an > executable into a TMS320DM642. Then during the processing of > subsequent host processor messages (via the PCI bus interface) the > emulator "just stopped." It was in the middle of a perfectly > legitimate portion of the code. > > Has anyone seen this behavior before and can you give an reason > for it?
Hi Folks, I've found the answer to my question, and am passing it along in case others may find it useful. The emulator will stop when it encounters an invalid opcode. For some reason my program memory is getting trashed, so the emulator is seeing invalid opcodes. Note also that the disassembly window will render an invalid opcode as a ".word 0xYYYYYYYY" "instruction," instead of a normal mnemonic. --Randy