CCS/OMAP-L138: OMAP L138 BH-USB560BP connection error.

Hi Ramesh,

I'm looping in one of our emulator experts.
However, I wonder if this is an issue with CCS running from Linux. I think you have posted this question in the correct sub-forum (CCS). Perhaps they can diagnose this error you are experiencing.

See these relevant threads:

e2e.ti.com/.../600760
- helpful links and possible solution

e2e.ti.com/.../342015
- similar issue with Ubuntu - installed libusb* and some additional packages to resolve it

Regards,
Mark

Ramesh,

Unfortunately I don't have the same debug probe as you, but did you run the script at the end of the installer to allow user access to the debug probes?
software-dl.ti.com/.../ccsv8_linux_host_support.html

As a side note, Ubuntu 18.04 introduced several changes that caused a number of incompatibilities with older versions of CCS. If I recall correctly, the "Test Connection" was affected for some debug probes. In this case, can you try to simply connect to the device by launching the debugger?

The page you referenced in your post is good and is being actively maintained.

Hope this helps,
Rafael

Thank you so much for the quick response Rafael. I have tried to connect the device by launching the debugger but I'm getting the below error:
Error initializing emulator:
(Error -2083 @ 0x0)
Unable to communicate with the debug probe. Confirm debug probe configuration and connects, reset the debug probe, and retry the operation. (Emulation package 7.0.100.0)

I would like to know which version of Ubuntu works without any issue OMAP L138 using Blackhawk JTAG USB560 BP Emulator.

Installed libusb-1.0-0-dev:i386 and ran the below command still not working.

sudo apt-get update
sudo apt-get install libc6-i386 libx11-6:i386 libasound2:i386 libatk1.0-0:i386 libcairo2:i386 libcups2:i386 libdbus-glib-1-2:i386 libgconf-2-4:i386 libgdk-pixbuf2.0-0:i386 libgtk-3-0:i386 libice6:i386 libncurses5:i386 libsm6:i386 liborbit2:i386 libudev1:i386 libusb-0.1-4:i386 libstdc++6:i386 libxt6:i386 libxtst6:i386 libgnomeui-0:i386 libusb-1.0-0-dev:i386 libcanberra-gtk-module:i386

Thanks,
Ramesh G

Thanks Mark for the response.

I Installed libusb-1.0-0-dev:i386 and ran the below command still not working.

sudo apt-get update
sudo apt-get install libc6-i386 libx11-6:i386 libasound2:i386 libatk1.0-0:i386 libcairo2:i386 libcups2:i386 libdbus-glib-1-2:i386 libgconf-2-4:i386 libgdk-pixbuf2.0-0:i386 libgtk-3-0:i386 libice6:i386 libncurses5:i386 libsm6:i386 liborbit2:i386 libudev1:i386 libusb-0.1-4:i386 libstdc++6:i386 libxt6:i386 libxtst6:i386 libgnomeui-0:i386 libusb-1.0-0-dev:i386 libcanberra-gtk-module:i386

Thanks,
Ramesh G.

Hi Rafael,

Yes I did all the above steps still getting the connection error.

Please note, I tried in CCSV7 and I'm going to try on CCSV8 as well.

Thanks,

Ramesh G

Ramesh,

I think you would be on the right track with CCSv8 due to the reasons above.

By the way, the Linux versions of CCS since 6.2 do not require the full set of 32-bit libraries anymore - only one is still needed (and shown in the link I sent before).

Please let me knwo the outcome of this.

Regards,
Rafael

Rafael,

I tried the below steps on CCSV8 version test connection setup but I'm still having the connection error issue. Please find the attached screenshot.

Please advise.

-Regards,

Ramesh G

Ramesh,

I think there are some issued in acknowledging this Debug Probe in your system. I found an older version (Blackhawk USB560, not BP) and it tested well here.

The main thing to check is if the probe is being acknowledged by the USB stack. Check for an entry for Blackhawk

user@host:~$ lsusb

Bus 002 Device 003: ID 0a5c:5800 Broadcom Corp. BCM5880 Secure Applications Processor
Bus 002 Device 004: ID 0b1e:8007 Electronic Warfare Assoc., Inc. (EWA) Blackhawk USB560-BP JTAG Emulator
Bus 002 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 003 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 003: ID 1bcf:2802 Sunplus Innovation Technology Inc. 
Bus 001 Device 002: ID 8087:0024 Intel Corp. Integrated Rate Matching Hub
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub

To check if the udev rules were correct added, check if the bh-permissions.rules file is present on the correct directory:

user@host:~$ ls /etc/udev/rules.d/
61-msp430uif.rules          71-bh-permissions.rules 99-jlink.rules
70-mm-no-ti-emulators.rules 71-sd-permissions.rules
70-snap.core.rules          71-ti-permissions.rules

If the udev rules are there, issue the following command as a superuser.

user@host:~$ cd ti/ccsv8/ccs_base/common/uscif/
user@host:~/ti/ccsv8/ccs_base/common/uscif$ sudo ./dbgjtag -X emulator,driver=bh560usb.out -S integrity
[sudo] password for user:

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

If the test succeeds with sudo, you will have to restart your system for the rules to be acknowledged.

If the test still is unsuccessful and/or the lsusb does not return the expected outcome, I suspect the Debug Probe may be somehow damaged.

Hope this helps,

Rafael

Rafael

Sorry for the late response. Thanks for the detailed information. We could able to connect to OMAP from linux PC using BH USB560 BP JTAG Emulator but unable to connect from Ubuntu Virtual Machine( Virtual Box or Hyper-V) to OMAP using BH USB 560 BP JTAG Emulator.

Virtual machine not detecting the BH USB. Please help us to connect Virtual Machine (Ubuntu) to OMAP using BH USB 560.

-Ramesh G.