From: Oliver G. <oli...@gm...> - 2021-02-22 07:27:46
|
On 19/02/21, Tommy Murphy wrote: > I'm not sure that you have to adjust the scripts at all? > E.g. this shows how to target that device using jlink. > > https://community.nxp.com/t5/i-MX-Processors/How-to-JTAG-debug-iMX8mq/m-p/837227 The imx8mq and the imx8qm are not the same. The naming is a bit confusing here. The distinguish on amount of cores but are part from same CPU/SOC familiy. > If your board includes an FTDI interface for debugging then presumably the second and third scripts that you list might work? > > What did you try so far and how did it go? The first try was this way: sudo openocd -f tcl/interface/jlink.cfg -f tcl/board/nxp_mcimx8m-evk.cfg Open On-Chip Debugger 0.11.0-rc2+dev-00009-gba0f38213-dirty (2021-02-18-11:16) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : Listening on port 6666 for tcl connections Info : Listening on port 4444 for telnet connections Info : J-Link V11 compiled Feb 4 2021 12:59:17 Info : Hardware version: 11.00 Info : VTarget = 3.322 V Info : clock speed 1000 kHz Error: JTAG scan chain interrogation failed: all zeroes Error: Check JTAG interface, timings, target power, etc. Error: Trying to use configured scan chain anyway... Error: imx8mq.cpu: IR capture error; saw 0x00 not 0x01 Warn : Bypassing JTAG setup events due to errors Error: Invalid ACK (0) in DAP response > > The openocd user manual explains what target, board and interface scripts do. I have to check it a bit deeper. Best regards, Oliver |