From: Hiago F. <hia...@gm...> - 2022-09-01 19:08:01
|
Hi Tommy, Here is the schematic of the board I'm using: [image: image.png] This is the FTDI chip. Now I created this configuration file here: *adapter driver ftdiftdi vid_pid 0x0403 0x6011ftdi channel 1ftdi layout_init 0x00f8 0x000b# only JTAG supportedtransport select jtag# set a safe JTAG clock speed, can be overriddenadapter speed 1000# board has an i.MX8MM with 4 Cortex-A53 coresset CHIPNAME imx8mmset CHIPCORES 4# Source SOC Configurationsource [find target/imx8m.cfg]* And I'm getting this error: *Open On-Chip Debugger 0.11.0+dev-00808-g9cd714cd1 (2022-08-19-13:38) Licensed under GNU GPL v2 For bug reports, read http://openocd.org/doc/doxygen/bugs.html <http://openocd.org/doc/doxygen/bugs.html> Info : Hardware thread awareness created Info : Listening on port 6666 for tcl connections Info : Listening on port 4444 for telnet connections Info : clock speed 1000 kHz Info : JTAG tap: imx8mm.cpu tap/device found: 0x5ba00477 (mfg: 0x23b (ARM Ltd), part: 0xba00, ver: 0x5) Info : imx8mm.a53.0: hardware has 6 breakpoints, 4 watchpoints Info : starting gdb server for imx8mm.a53.0 on 3333 Info : Listening on port 3333 for gdb connections Info : starting gdb server for imx8mm.m4 on 3334 Info : Listening on port 3334 for gdb connections Info : gdb port disabled Info : accepting 'gdb' connection on tcp/3334 Error: Target not examined yet Error executing event gdb-attach on target imx8mm.m4: Info : New GDB Connection: 1, Target imx8mm.m4, state: examine deferred Error: Target imx8mm.m4 not examined yet, refuse gdb connection 1! Error: attempted 'gdb' connection rejected* There is a cfg file from NXP that looks like the same I'm trying to do here, but I'm not sure why my code isn't working: *# SPDX-License-Identifier: GPL-2.0-or-later## Configuration file for NXP MC-IMX8MP-EVK on-board internal JTAG## Using this interface requires enabling "remote mode" for the board using the# NXP bcu tool (see https://github.com/NXPmicro/bcu <https://github.com/NXPmicro/bcu>)## bcu set_gpio remote_en 1 -board=imx8mpevk## The REMOTE_EN gpio is accessible through the same FTDI adapter but it's# behind an I2C GPIO expander.#adapter driver ftdiftdi vid_pid 0x0403 0x6011ftdi channel 0ftdi layout_init 0x00f8 0x000bftdi layout_signal RESET_B -data 0x0010 -oe 0x0010# Called SYS_nRST in schematicsftdi layout_signal nSRST -data 0x0020 -oe 0x0020ftdi layout_signal IO_nRST -data 0x0040 -oe 0x0040ftdi layout_signal ONOFF_B -data 0x0080 -oe 0x0080ftdi layout_signal GPIO1 -data 0x0100 -oe 0x0100ftdi layout_signal GPIO2 -data 0x0200 -oe 0x0200ftdi layout_signal GPIO3 -data 0x0400 -oe 0x0400ftdi layout_signal GPIO4 -data 0x0800 -oe 0x0800* Do you know if I need to define all these layout_signals as well? Thank you! On Thu, Sep 1, 2022 at 2:41 PM Tommy Murphy <tom...@ho...> wrote: > Looks like a problem with the reset configuration? > > > https://github.com/openocd-org/openocd/blob/6db57051d070fc8d6bb54d21413e5e8610972651/src/target/aarch64.c#L1966 > > Maybe the except needs to use SRST? > |