Part Number:TMS320DM6433
Tool/software: Code Composer Studio
We have a mature product based on the TMS320DM6433. The product was developed using CCS V6.x and debugged with a Blackhawk USB560V2 JTAG debugger. As we begin development of a new product, we decided to upgrade to CCS V7. In conjunction with this upgrade, we switched our legacy product to CCS V7 as well. Since making this switch, my debug environment has become completely unreliable.
The initial install of CCS V7 had trouble due to the Blackhawk driver signature. Disabling the requirement for driver signatures in Windows resolved this problem. I can connect to my target with the Blackhawk JTAG debugger, but it doesn't run properly. While stepping through code it often 'quietly' disconnects. That is, no error message is displayed, but code execution stops and variables/memory are not accessible. Often while debugging, the code gets 'stuck' in a printf output loop in which I assume it is trying to send data via USB back to the PC.
Everything works fine if I switch back to CCS V6 on the same computer and using the same Blackhawk debugger.
My system specifics are:
- Windows 10 Pro, 64 bit, V1709 Build 16299.309
- CCS V7.4.0.00015
- Blackhawk Driver V6.2.0.009
I must have my environment running under CCS V7 as it is used by the rest of the developers in my department. Any suggestions would be greatly appreciated.
Regards.