debugging dsplink on omap l138, how to connect with wince on arm

Kevin,

I am going to move this into the WinCE forum to see if they can help.  The wiki describes how to do this for Linux but there is likely an equivalent for WinCE.

Regards,

John

Hi

CCS is regularly used for flashing eboot. However I am not aware of it can be used for debugging in a Win Ce. Can you can share the snap shots of the errors that you are facing?

Can you look through this article to see if it can enable you in the meanwhile?

Deepali

I'm not really getting tons of errors,  though if i follow that guide I get up to launch target connection and it fails to initialize, and can't find the device if i use xds100v2 with omap set

If i use just the c6748 it'll restart the app.

this is probably the most frequent error... so i'm thinking that because the wince driver is using it i may have problems...

Cannot acquire emulator process Possible conflict for device driver usage 

i'm going to try to set up a hello word program without the dsplink and see if i can get it so it doesn't restart the arm and i get debugging.

Deepali,

CCS doesn't support WinCE debug, it won't recognize the symbols produced by the Microsoft compiler.  However the wiki that Kevin was looking at doesn't require CCS to do any debugging on the ARM.

John

we don't want to debug the arm, just the dsp, but I havn't been able to find a way to debug it that works or stomps all over the arm.

basically i want windows ce to be running, and then load an app onto the dsp and debug it.

Kevin,

Can you confirm that you are not connect to the ARM in CCS, just the DSP?  One thing you can do to make sure CCS is not touching the ARM at all is to bypass the ARM in the target configuration file.  Then CCS is not even aware that it is in the scan chain and can't talk to it.

Regards,

John

yes i have tried that, i can't seem to get that to work, it'll restart my board any way, I'm beginning to think that debugging a program seperatly on the dsp is not possible with wince6.0 or that the dsplink driver fights with the emulator

Kevin

DSPLink driver does not interfere with the emulator settings.

Deepali

if it doesn't then could it be a problem with our wince, i've been trying every thing i can find, I was able to get it to connect, load the symbols, and it even showed the program counter to be in my while(1) loop, but I havn't been able to reproduce this even taking the exact same steps it sometimes works, it sometimes doesn't.

so there is no way to adapt http://processors.wiki.ti.com/index.php/Debugging_the_DSP_side_of_a_DSPLink_application_on_OMAP-L138_using_CCS this to work on wince without causing problems? using notify to debug our program just isn't going to work well since we have a lot to port over and not having debuging capability really stinks ;(