Xtensa Debugger Daemon Not working in Linux

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Xtensa Debugger Daemon Not working in Linux

Jump to solution
1,247 Views
abdob
Contributor III

I have the IMXRT685 board and I am following the Getting Started with Xplorer for EVK-MIMXRT685, Rev. 2.12.0, 01 June 2022 Guide.

On section 2.5 Install Xtensa On Chip Debugger Daemon I install xt-ocd-14.08-linux64-installer from the path /opt/xtensa/XtDevTools/downloads/RI-2021.8/tools/.

The latest versions of the J-link drivers are installed (7.82 and 7.66b which was the latest as of 01 June 2022). 

I am able to perform section 2.6 Program LPC-Link2 with SEGGEER J-Link, extract the SN and update the topology.xml file.

However later in Section 5.2 Build and Debug DSP Application step 2, Launch xt-ocd debugging server.

I cd into /opt/Tensilica/xocd-14.08 and run ./xt-ocd -c topology.xml

I get: 

XOCD 14.08 2021-12-10 23:32:56
(c) 1999-2022 Cadence Design Systems Inc. All rights reserved.
[Debug Log 2022-12-14 10:18:04]
Loading module "gdbstub" v2.0.0.12
ERROR: Error loading module jlink:
./jlink.so : ./jlink.so: cannot open shared object file: No such file or directory
./modules/jlink.so : libjlinkarm.so.6: cannot open shared object file: No such file or directory
/opt/Tensilica/xocd-14.08/modules/jlink.so : libjlinkarm.so.6: cannot open shared object file: No such file or directory
/opt/Tensilica/xocd-14.08/../lib/ocd/jlink.so : /opt/Tensilica/xocd-14.08/../lib/ocd/jlink.so: cannot open shared object file: No such file or directory

On section 2.5 it states "For Linux: When installing xt-ocd on Linux, ensure that the symlink is manually added to the installed J-Link driver: ln -s <jlink-install-dir>libjlinkarm.so.6 <xocd-install-dir>/modules/libjlinkarm.so.6"

However in the jlink drivers file only the file libjlinkarm.so.7 is present, not the libjlink.arm.so.6

If I try to copy the libjlinkarm.so.6 file from the jlink driver directory to the xocd-14.08/modules directory as liblinkarm.so.7 and run it from the modules directory like this:

../xt-ocd -c ../topology.xml

I get this:
XOCD 14.08 2021-12-10 23:32:56
(c) 1999-2022 Cadence Design Systems Inc. All rights reserved.
[Debug Log 2022-12-14 10:22:43]
Loading module "gdbstub" v2.0.0.12
Loading module "jlink" v2.0.2.0
Using JLINK lib v.76602
Jlink USB Serial Number: 725664142
Connected to Jlink Device:
Name:'J-Link LPCXpresso V2 compiled Apr 4 2019 16:54:03'
S/N:725664142
Firmware: J-Link LPCXpresso V2 compiled Apr 4 2019 16:54:03
Requested/Set TCK: 1000kHz/1000kHz
Jlink: Select pipelined SWD
SWD-DP with ID 0x6BA02477
Loading module "jtag" v2.0.0.20
Loading module "xtensa" v2.0.0.48
Starting thread 'GDBStub'
Listening for GDB connection on port 20000
Initialize XDM driver
Error: SWD Wait time-out expired!
SWD-DP with ID 0x6BA02477
SWD-DP with ID 0x6BA02477
SWD-DP with ID 0x6BA02477
SWD-DP with ID 0x6BA02477
Error: XDM initialization failed
ERROR: Couldn't initialize, exit...

So whats the issue here, seems like a dependency issue since the wrong library name was installed?

Has this been tested with linux? I noticed the instructions have "./xt-ocd.exe" on the linux section instead of "./xt-ocd"


Labels (1)
0 Kudos
1 Solution
1,221 Views
abdob
Contributor III

abdob_0-1671152951367.png

I found a jlink drivers version 6.96 (similar to the video) tutorial, that works.

 

View solution in original post

0 Kudos
1 Reply
1,222 Views
abdob
Contributor III

abdob_0-1671152951367.png

I found a jlink drivers version 6.96 (similar to the video) tutorial, that works.

 

0 Kudos