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.

CCSTUDIO: dbgauth.exe - A required dynamic library could not be located

Part Number: CCSTUDIO
Other Parts Discussed in Thread: AM625

Tool/software:

We have CCS 12.7.1 installed on a Windows 10 computer.  
We are trying to use the dbgauth.exe program in ccs/ccs_base/common/uscif with an XDS110 USB debugger to unlock an HS-FS AM625 device using the steps documented in the AM62x Academy (https://dev.ti.com/tirex/explore/node?node=A__AV550pCGyc49wIO5c90bPw__AM62-ACADEMY__uiYMDcq__LATEST, step 7):
./dbgauth -c ~/.ti/<ccs_version>/0/0/BrdDat/ccBoard0.dat -x xds110 -s cs_dap_0 -o unlock -m 3 -f ~ debug_unlock_cert.der
However, when we run this command, we get the following error message that does not have sufficient information to debug the problem:
Successfully opened certificate file .\.ti\debug_unlock_cert.der.
Read 1687 bytes from certificate file .\.ti\debug_unlock_cert.der.
RUNTIME ERROR(XDS) : (Error -600 @ 0x0)
A required dynamic library could not be located.
The library isn't on the search path.
(Emulation package 12.7.0.00130)

The unlock routine failed; the target device is still locked.
Check the unlock key and board configuration.
 We are not sure what required library could not be located.  However, we assume it has something to do with the debugger since the command runs fine when just using the "--help" option.
  We have verified that the XDS110 USB debugger works and is able to connect to other devices on the same system.
  Please let us know if you need any additional information.
Thanks,
Erik
  • Hi Erik,

    Thanks for reaching out to Texas Instruments E2E support forum.

    However, when we run this command, we get the following error message that does not have sufficient information to debug the problem:

    This error above means the software and device drivers are not properly installed. 

    Please refer Library Error section of the JTAG debugging guide.

    Please refer below screenshot.

      

    Regards,

    Tushar