Because of the holidays, TI E2E™ design support forum responses will be delayed from Dec. 25 through Jan. 2. Thank you for your patience.

  • State Resolved
  • Locked Locked
  • Replies 1 reply
  • Subscribers 53 subscribers
  • Views 944 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Using DSS to connect to a embedded target with multiple Blackhawk emulators connected

Angelo Schneider
Prodigy 70 points

Hello everyone,

currently we investigate the option to have several Blackhawks connected via USB to a Windows 7 machine. Each Blackhawk has its own target connected via JTAG connector.

I'm planning to write scripts that are integrated into a Jenkins CI Server build process. Those scripts need to be able to connect selectively to a specific target using the DSS library.

Did anyone do something like this already? I have trouble to imagine how the debugSession is opened.

In principle I assume I only need to change this line: debugSession = debugServer.openSession("Blackhawk USB560-BP Emulator, 20-pin JTAG Cable_0/<CORE>");

To debugSession = debugServer.openSession("Blackhawk USB560-BP Emulator (S/N:LG5073), 20-pin JTAG Cable_0/<CORE>");

The "S/N:LG5073" part is the internal serial number of the emulator.

In the Blackhawk control panel the device shows up like this:

Just wondering what your experiences are. I start playing with this next week ;D

Best Regards

Angelo

  • 0
    TI__Guru**** 169234 points

    This thread was worked directly with Blackhawk. For the benefit of others, the discussion is as follows:

    email said:

    I've emailed Angelo directly from our support account over the last few days and explained how to relate the emulator SN and USB index shown in our control panel to the I/O port in the CCS CCXML file.    Based on out last email correspondence, he understands it and can plan that into his build process.

    More  details....

    For example, in his picture, LF4904 uses index 0 (I/O port = 0) and LG5073 uses index 1 (I/O port = 1).  I also explained that the index depends on the USB device's VID/PID/REV/SN and Windows can adjust the index, such that, if he attached LG5073, the index will be 0, then if he attaches LF4904, it gets index 0 and LG5073 is changed to 1.  A strange Windows/USB thing. 

    Anyway, I told him that we have a cmdline utility that checks what is attached/enumerated and can return text with index and serial number.  So, he can match that output to his build process scripts  emulator serial number and CCXML file to select the proper information.

    We also created a similar LAN560 utility for a customer.  That request was slightly different, as they had a pool of LAN560 emulators on the network connected to various target boards and their dev team would automatically connect to the first available board. The utility would return status of the emulator (i.e. in-use, available, not-found) and their script would spawn CCS accordingly.

    BHDeviceList.exe is the name of the utility (it is not something we nromally distribute with our CCS updates).

    Regards,

    Rafael