Debugging multiple targets via Blackhawk USB2000

Johan W���lger said:

I am positive that I did run this setup in previous CCS versions (both CCS4 and some earlier CCS5 versions), and I don't remember doing any manual configurations before launching two simultaneous debug sessions. Any ideas what might go wrong or if I should do some setup or configurations before trying the simultaneous debbuging?

CCS Debug Crash is a recent thread which mentions a Blackhawk Update Package was required to stop a CCS 5.3 crash when using a single BlackHawk USB2000 (but doesn't give the version of the update).

A single BlackHawk USB2000 is working with CCS 5.5, using Blackhawk CCSv5.5 Emulation Update version 5.5.0.340

However, when attempted to use the BlackHawk USB2000 with CCS 6 beta 3 with Blackhawk Emulators version 6.0.0.102:

1) Attempting to test the connection failed,since it caused the dbgjtag.exe to crash:

2) Attempting to connect using the Blackhawk USB2000 caused CCS 6 to crash (and exit without any error messages).

On the second session in CCS, what happens if you attempt to test the connection rather than connecting to the target?

One session works just as flawlessly as it has ever done.

I launched one session (the 28035 project) and then did a test connection on the 28335 project. Nothing crashes, but the log doesn't look very promising (please see the printout below). If I launch the Blackhawk control panel both devices appear and look healthy. The CCS updater can't seem to find any more updates.

[Start]

Execute the command:

%ccs_base%/common/uscif/dbgjtag.exe -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

C:\Users\johwol\AppData\Local\.TI\693494126\
    0\1\BrdDat\testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'bhemujscl.dll'.

An already open status was returned while soft opening the controller.

-----[An error has occurred and this utility has aborted]--------------------

This error is generated by TI's USCIF driver or utilities.

The value is '-110' (0xffffff92).
The title is 'SC_ERR_OCS_ALREADY_OPEN'.

The explanation is:
This utility opened the controller but found it already in use.
You must exit other debuggers and utilities that access the
controller because this utility must be the only client.

[End]

Hello Johan,

Could you tell me a bit more about your setup? Specifically, what exact emulator are you using for each target?

Also, any reason why you are launching two separate debug sessions instead of one debug session that can communicate with both devices?

Thanks

ki

Hello Ki,

I am using Blackhawk USB 2000 emulators. Do you need any more information about them such as revision or serial number? Any hint where that can be found if that is the case?

The exact setup I am using consists of one custom board with three different TMS320:s on it. Each with its own JTAG interface. The two I am trying to connect to for simultaneous debugging is a 28035 and a 28335. I don't really follow on your suggestion about doing that with one debugging session. The processors are obviously running two completely different SW stacks. Just guessing about what you are suggesting, but my feeling is that if I did manage to launch both projects for debuggingg in the same session in the same instance of CCS, it would be quite hard to keep track of which files and breakpoints that belong to which project. If possible, I would prefer to keep the two projects apart in different instances of CCS, but on the same machine as I used to do in older versions of CCS.

Best,

Johan

Johan W���lger said:

I am using Blackhawk USB 2000 emulators. Do you need any more information about them such as revision or serial number? Any hint where that can be found if that is the case?

I'm sorry, don't know know why I asked you this. You clearly started you are using Blackhawk USB2000 from the start.

Johan W���lger said:

I don't really follow on your suggestion about doing that with one debugging session.

An example is covered here:

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

Johan W���lger said:

but my feeling is that if I did manage to launch both projects for debuggingg in the same session in the same instance of CCS, it would be quite hard to keep track of which files and breakpoints that belong to which project.

The debugger can manage that for you.

Johan W���lger said:

If possible, I would prefer to keep the two projects apart in different instances of CCS, but on the same machine as I used to do in older versions of CCS.

It really does come down to preference.

I'll see if I can reproduce your issue (now that you have pointed out to me that you already mentioned the emulator type you are using! :P)

ki