From: Salko, M. <mar...@si...> - 2024-05-29 13:37:05
|
Dear openocd users/developers. I have an issue with connecting to our product using the xds110 debuger, and openocd with gbd. I have openocd built using mingw-w64, from gitlab repository with following commit: 2c8376b - target/xtensa: avoid IHI for writes to non-executable memory (this is because support for ti am243x was added recently) I'm trying to connect to a running cpu, then reset it and run it again, I'd like to essentially do a step by step trace. This is an error I'm getting from open ocd, when gdb connects to the first core: oocd ('err', 'Error: JTAG-DP STICKY ERROR\r\n') oocd ('err', 'Error: Failed to read memory at 0xe000ed00\r\n') oocd ('err', 'Error executing event gdb-attach on target am243.cpu.sysctrl:\r\n') gdb connects using command: "target extended-remote localhost:3333" >From the schematic we use 5 pin jtag with emu0/1 pins pulled up high, so I think design wise this is fine (debugging tools provided) This is my board.cfg: source [find interface/xds110.cfg] transport select jtag reset_config srst_only srst_push_pull adapter srst delay 20 set SOC am243 source [find target/ti_k3.cfg] adapter speed 250 gdb_port 3333 bindto 0.0.0.0 init reset halt wait_halt sleep 100 poll am243.cpu.main0_r5.0 arp_examine >From reading the documentation on arms side, sticky DP is an abort condition? As far as CoreSight is concerned. And there is a register to clear it, so maybe that is what I have to do, However I have no experience in working directly with jtag or DP registers. Any suggestions/help would be highly appreciated. With best regards, Martin. |