• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 54 subscribers
  • Views 2081 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.

CCS/XDS560TRACE: Device Signature Issue

Jonathan Riger
Prodigy 90 points

Part Number: XDS560TRACE

Tool/software: Code Composer Studio

I'm having trouble connecting to my Blackhawk XDS560v2 after updating to the latest version of Blackhawk CCSv6.2 Emulation Update.

I'm currently running CCSv7.2.0.201705101800 on Window 10 64-bit.

Device Manager Output

Windows cannot verify the digital signature for the drivers required for this device. A recent hardware or software change might have installed a file that is signed incorrectly or damaged, or that might be malicious software from an unknown source. (Code 52)

The output of the test connection dialog:

[Start: Blackhawk XDS560v2-USB System Trace Emulator_0]

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\jwr41\AppData\Local\TEXASI~1\CCS\
ti\0\0\BrdDat\testBoard.dat

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

This utility has selected a 560/2xx-class product.
This utility will load the program 'bh560v2u.out'.
E_RPCENV_IO_ERROR(-6) No connection: emulator was not found
Download failed for file C:\ti\ccsv7\ccs_base\common\uscif\xds560v2.out

An error occurred 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 '-250' (0xffffff06).
The title is 'SC_ERR_ECOM_EMUNAME'.

The explanation is:
An attempt to access the debug probe via USCIF ECOM has failed.

[End: Blackhawk XDS560v2-USB System Trace Emulator_0]

Any help would be appreciated. Thank you

  • 0
    TI__Guru**** 168894 points
    Hi,

    Unfortunately I am unable to reproduce this issue here. I am using Windows 10 Pro/64 (version 1511, build 10586.1176) with the latest Blackhawk Emulation pack update.

    Can you try to uninstall/reinstall the device drivers? Perhaps this helps in properly instantiating your Debug Probe.

    The directory C:\Program Files (x86)\Blackhawk\Emulation\Drivers contains the file Drivers-ReadMe.txt. At the end of this file there are instructions on how to update/reinstall the device drivers. This can help you with improper instantiation.

    Hope this helps,
    Rafael
  • 0 in reply to desouza
    Prodigy 90 points

    Hi Rafael, 

    Thanks for the reply. I've been working with blackhawk support to resolve this issue. I finally have the problem resolved, the issue is with Secure Boot being enabled in the UEFI bios. The secure boot required the driver to be signed and apparently the Blackhawk driver was not properly signed.

    After disabling secure boot, the emulator is working again.

    Thanks,

    Jonathan

  • 0 in reply to Jonathan Riger
    TI__Guru**** 168894 points
    Jonathan,

    Thank you for reporting back your findings. Interestingly, yesterday I received an internal e-mail with communications between Blackhawk and a colleague that discussed the exact same problem (the secure boot on UEFI BIOS).

    I imagine an update will be available soon via the CCS Update.

    Regards,
    Rafael
  • 0 in reply to desouza
    Prodigy 90 points
    Hi Rafael,

    I just download and installed the latest of the Blackhawk Emulation Update (v6.2.0.009) and it no longer requires disabling secure secure boot in the BIOS. Thank you for your support,

    Jonathan
  • 0 in reply to Jonathan Riger
    Prodigy 150 points
    Hi All,
    I am having the exact same problem as described at the start of this thread and I already have Blackhawk Emulation Update (v6.2.0.009) installed. I'm running CCSv7.4.0.201711260800 on a Windows 10 Pro 64-bit machine. This is a new Code Composer installation on a brand new machine. Everything worked fine on my old (similar) machine. Any ideas?

    Thanks,
    Stuart