Trying to debug u-boot with XDS100v2 on am3352: Target must be connected before loading program

Hi Biser,

I thought I was in that tutorial, but I did not see #4. OK, so I tried that:

Error connecting to the target:
(Error -2131 @ 0x0)
Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).
(Emulation package 6.0.14.5)


The board is running linux at the moment, and having the jtag connected and trying to launch the application in ccs and connect to target all have no visible effect on the console output of the busybox.

Yesterday I got ccs all set up and let it build linux and u-boot. I do not know if there is something more I need to do to tell ccs where the sources are. It built linux/u-boot from a perl script, so I don't know how ccs would know where to look for sources.

Is there some way to tell it? I was actually hoping to just point ccs at existing sources and run the already-built u-boot, without having ccs rebuild it, but I don't know how to do that.

As you can tell, I'm new to ccs.

Thanks,
Dick

I'm not a software expert myself. You can try asking on the CCS forum: e2e.ti.com/.../81

This page has links to CCS information you might find useful too: processors.wiki.ti.com/.../Processor_SDK_Linux_Tools (links under "Code Composer Studio").

>>The board is running linux at the moment
Which Linux SDK version are you using? And on which board?

Some of the ProcessorSDK's have the JTAG clock turned off after Linux boots. But I have always been able to connect CCS to uboot (just hit a key on the uboot console to exit boot).