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.

Olimex XDS100V2 @ Win7 64bit @ CCS5.3.0 / CCS4.2.4

Other Parts Discussed in Thread: TMS320F28016, CONTROLSUITE

Dear community,

I'm trying to get my Olimex XDS100V2 emulator to work with the Olimex TMS320F28016 board. As software I'm using the CCS5.3.0 (free version) and (since I assumed it would help) the CCS4.2.4. My OS is Win7 64bit (without any Admin rights). Both CCS versions are NOT installed in the "program files" directory.

The problem is, when I load the very basic cpu_timer example (from TI website) into the RAM and start Debugging the program does not work properly. When I try to debug the program step by step I can see that the initialization part is executed and even the step into the infinte for-loop at the end of the "main" function. When I try to let the program run freely (not step by step) the timer-counter-variable in the watch window is not increased by the interrupt routine. Instead it seems as if the F28016 would do a reset since the infinte loop is left and the initialization functions are called again. I've also tried other TI examples and strictly followed the procedure as described in the pdf "C280x/C2801x C/C++ Header Files and Peripheral Examples Quick Start" but none of those exemplary code works as intended...

There is no error message or other obvious behaviour at all when I look in the messages I get within CCS. Even the "test connection" tool in CCS5 doesn't show any errors.

When I try to operate the whole assembly (hard- and software) on my other PC with WinXP (with full Admin rights) everything works fine.

Can anyone give me a hint where to search for the cause of that strange behaviour.

Thanks a lot!

  • Hans,

    I can't imagine why the code would run differently on a Win7 PC vs WinXP. I am assuming all other factors are the same between the two PCs - (ie) version of CCS, version of controlSuite, emulator, board etc. Do you, by any chance, have another Win7 PC to test it out with in case there is something specific to this one PC's environment?

  • Problem solved:

    To my deep shame I must admit that I have had different power supplies for both setups (one was at home, the other at work). The supply at work was not able to deliver the full current (somewhat around 300-400 mA) and (as it is quite a simple one) doesn't indicate the overcurrent situation by e.g. a LED. This current limitation in turn explains the controllers reset due to temporary undervoltage.

    Sorry.