Quantcast
Channel: Tools
Viewing all articles
Browse latest Browse all 91752

Forum Post: RE: Using DSS to connect to a embedded target with multiple Blackhawk emulators connected

$
0
0

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

[quote user="email"]

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).

[/quote]

Regards,

Rafael


Viewing all articles
Browse latest Browse all 91752

Trending Articles