Spectrum DIgital XDS510USB Issue after upgrading to CCS4.2.1.00004

Scott,

Although it is always preferable to use the latest versions of software (bug fixes, etc.), the thread you mentioned is specific to Blackhawk and the fact that CCSv4.1.3 requires updates to the emulation device drivers.

What target did you configure and what hardware are you trying to connect? The Bad Silicon Rev error is usually tied to the fact the processor is different than the one configured (if there are no bugs happening with your specific configuration, of course).

This issue can also be caused by some issues with the communications (the silicon rev number may have been corrupted during JTAG communications with the target). Can you test the integrity of the JTAG channel by following the procedure linked below?

http://processors.wiki.ti.com/index.php/Debugging_JTAG_Connectivity_Problems#If_using_Spectrum_Digital_emulators

Also check another post that also shows this issue in a specific hardware (C6727):

http://e2e.ti.com/support/development_tools/code_composer_studio/f/81/t/87568.aspx

If everything is working correctly, I would go for the usual suspects (clean the workspace, use a different workspace, try a different board/emulator combination, etc.). Check the page below for details:

http://processors.wiki.ti.com/index.php/Troubleshooting_CCS

Hope this helps,

Rafael

Thanks.  Customer has tried all these steps with the same error.  Customer also updated the drivers/firmware when asked during install.  Same error.  He found a Wiki on debug issues.  I ran the sdconfigEx.exe program from Spectrum.  There is a utility to test the emulator and scan chain.  He ran 100 loops and it returned 0 errors.  He does not think it is a board/hardware issue.

Other ideas?

Scott,

What device are they trying to connect to?

John

LM3S6918

Scott,

I can reproduce this.  

When using CCSv4.1.3 I don't get this error.  We are going to have to follow up with Spectrum to see what is going on.

Regards,

John

Great.  I have filed a defect to make it set that to the appropriate value when you select a Stellaris device.  Looks like the value varies by device so someone switched the default to something that works for other devices but doesn't work for Stellaris.

John