i.MX ProcessorsのトピックRe: IMX6 FT2232H OpenOCD config

IMX6 FT2232H OpenOCD config

Alex_Smart — Thu, 03 Oct 2024 15:36:10 GMT

I have a IMX6 quad Sabreboard and trying to connect to this piece of equipment with OpenOCD via FT2232H based debugger. However, no luck so far.

Here is OpenOCD output:

openocd -f interface/ftdi/ft2232h.cfg -f board/fsl_imx6q_sabresd.cfg Open On-Chip Debugger 0.12.0 (2024-09-16) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 d52e355daa09f17ce64819122cb067b8a2ee0d4b For bug reports, read http://openocd.org/doc/doxygen/bugs.html DEPRECATED! use 'adapter driver' not 'interface' DEPRECATED! use 'ftdi vid_pid' not 'ftdi_vid_pid' DEPRECATED! use 'ftdi channel' not 'ftdi_channel' DEPRECATED! use 'ftdi layout_init' not 'ftdi_layout_init' DEPRECATED! use 'adapter speed' not 'adapter_khz' adapter speed: 200 kHz Warn : Transport "jtag" was already selected Warn : imx6q.sdma: nonstandard IR value ../OpenOCD-20240916-0.12.0/bin/../share/openocd/scripts/board/fsl_imx6q_sabresd.cfg:145: Error: invalid command name "imx6q.cpu.0.0" in procedure 'script' at file "embedded:startup.tcl", line 28 at file "../OpenOCD-20240916-0.12.0/bin/../share/openocd/scripts/board/fsl_imx6q_sabresd.cfg", line 145

I read this topic, and this is basically what I need https://community.nxp.com/t5/i-MX-Processors/How-to-burn-U-boot-using-JTAG-for-IMX6Q/m-p/985128

but that solution didnt wotk either.

Is there some other cfg files or something?

Re: IMX6 FT2232H OpenOCD config

Bio_TICFSL — Fri, 04 Oct 2024 14:14:04 GMT

Hello,

You can view the following thread:

https://community.nxp.com/t5/i-MX-Processors/OpenOCD-Problem-i-MX6/td-p/229332

https://community.sparkfun.com/t/openocd-on-freescale-i-mx6/26385

Regards

Re: IMX6 FT2232H OpenOCD config

Alex_Smart — Sat, 05 Oct 2024 10:16:32 GMT

Thanks. It did help and I found a Jlink. Now there is a different issue: JTAG-DP STICKY ERROR

Open On-Chip Debugger 0.12.0 (2024-09-16) [https://github.com/sysprogs/openocd] Licensed under GNU GPL v2 libusb1 d52e355daa09f17ce64819122cb067b8a2ee0d4b For bug reports, read http://openocd.org/doc/doxygen/bugs.html Info : auto-selecting first available session transport "jtag". To override use 'transport select <transport>'. Warn : imx6.sdma: nonstandard IR value Info : Hardware thread awareness created Info : Hardware thread awareness created Info : Hardware thread awareness created Info : Hardware thread awareness created Info : Listening on port 6666 for tcl connections Info : Listening on port 4444 for telnet connections Info : J-Link ARM V8 compiled Jun 19 2012 11:29:30 Info : Hardware version: 8.00 Info : VTarget = 3.306 V Info : clock speed 1000 kHz Info : JTAG tap: imx6.cpu tap/device found: 0x4ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver: 0x4) Info : TAP imx6.sdma does not have valid IDCODE (idcode=0x4323803a) Info : JTAG tap: imx6.sjc tap/device found: 0x2191c01d (mfg: 0x00e (Freescale (Motorola)), part: 0x191c, ver: 0x2) Error: JTAG-DP STICKY ERROR Error: [imx6.cpu.0] Examination failed Warn : target imx6.cpu.0 examination failed Error: JTAG-DP STICKY ERROR Error: [imx6.cpu.1] Examination failed Warn : target imx6.cpu.1 examination failed Error: JTAG-DP STICKY ERROR Error: [imx6.cpu.2] Examination failed Warn : target imx6.cpu.2 examination failed Error: JTAG-DP STICKY ERROR Error: [imx6.cpu.3] Examination failed Warn : target imx6.cpu.3 examination failed Info : [imx6.cpu.0] starting gdb server on 3333 Info : Listening on port 3333 for gdb connections

What is that?