On Jan 14, 2009, at 11:38 AM, Alan Carvalho de Assis wrote:
Here we start initializing the jtag chain.
Info : 50 279 jlink.c:317 jlink_init(): J-Link JTAG Interface ready Debug: 51 279 jlink.c:446 jlink_reset(): trst: 0, srst: 0Debug: 52 279 openocd.c:151 handle_init_command(): jtag interface init completeDebug: 53 279 jtag.c:2240 jtag_init_inner(): Init JTAG chain Debug: 54 279 jtag.c:434 jtag_call_event_callbacks(): jtag event: JTAG controller reset (RESET or TRST) Debug: 55 279 jtag.c:1487 jtag_reset_callback(): - Debug: 56 279 jtag.c:1487 jtag_reset_callback(): - Debug: 57 279 jtag.c:1487 jtag_reset_callback(): - Debug: 58 279 jtag.c:1487 jtag_reset_callback(): - Debug: 59 280 jtag.c:434 jtag_call_event_callbacks(): jtag event: JTAG controller reset (RESET or TRST) Debug: 60 280 jtag.c:1487 jtag_reset_callback(): - Debug: 61 280 jtag.c:1487 jtag_reset_callback(): - Debug: 62 280 jtag.c:1487 jtag_reset_callback(): - Debug: 63 280 jtag.c:1487 jtag_reset_callback(): - Info : 64 314 jtag.c:1607 jtag_examine_chain(): JTAG tap: imx31.sjc tap/device found: 0x2b900f0f (Manufacturer: 0x787, Part: 0xb900, Version: 0x2)Info : 65 314 jtag.c:1645 jtag_examine_chain(): JTAG Tap/device matchedInfo : 66 314 jtag.c:1607 jtag_examine_chain(): JTAG tap: imx31.cpu tap/device found: 0x07b3601d (Manufacturer: 0x00e, Part: 0x7b36, Version: 0x0)Info : 67 314 jtag.c:1645 jtag_examine_chain(): JTAG Tap/device matched Warn : 68 314 jtag.c:1560 jtag_examine_chain(): Tap/Device does not have IDCODE Info : 69 314 jtag.c:1645 jtag_examine_chain(): JTAG Tap/device matchedInfo : 70 314 jtag.c:1607 jtag_examine_chain(): JTAG tap: imx31.smda tap/device found: 0x2190101d (Manufacturer: 0x00e, Part: 0x1901, Version: 0x2)Info : 71 314 jtag.c:1645 jtag_examine_chain(): JTAG Tap/device matched
We managed to read the IDCODEs and match them.
Debug: 72 314 jtag.c:434 jtag_call_event_callbacks(): jtag event: JTAG controller reset (RESET or TRST) Debug: 73 314 jtag.c:1487 jtag_reset_callback(): - Debug: 74 314 jtag.c:1487 jtag_reset_callback(): - Debug: 75 314 jtag.c:1487 jtag_reset_callback(): - Debug: 76 314 jtag.c:1487 jtag_reset_callback(): - Error: 77 317 jtag.c:1718 jtag_validate_chain(): Could not validate JTAG scan chain, IR mismatch, scan returned 0x0c2011. tap=imx31.whatchacallit pos=9 expected 0x1 got 0 Warn : 78 317 jtag.c:2260 jtag_init_inner(): Could not validate JTAG chain, continuing anyway...
Then for some reason we reset the jtag chain and try to do a validate. We get an IR mismatch and bail. I would guess the scan chain is in an inconsistent state at this point but we proceed anyway.
Debug: 79 317 openocd.c:157 handle_init_command(): jtag init complete Debug: 80 317 jtag.c:434 jtag_call_event_callbacks(): jtag event: JTAG controller reset (RESET or TRST) Debug: 81 317 jtag.c:1487 jtag_reset_callback(): - Debug: 82 317 jtag.c:1487 jtag_reset_callback(): - Debug: 83 317 jtag.c:1487 jtag_reset_callback(): - Debug: 84 317 jtag.c:1487 jtag_reset_callback(): - Info : 85 328 arm11.c:1595 arm11_examine(): found ARM1136 Debug: 86 328 arm11.c:1625 arm11_examine(): IDCODE 07b3601d IMPLEMENTOR 41 DIDR 15110004Debug: 87 334 arm11.c:328 arm11_check_init(): Bringing target into debug mode
We reset again and successfully find the ARM1136. The last line indicates we are attempting to halt the target under debug mode but since it doesn't return, I would guess is it unsuccessful. Since this isn't finishing, we never finish the init process and the servers are never started.
Is the JLink config expecting RCLK? Does the imx31 support RCLK? What speed is the JLink interface being set to? I suspect this is a data corruption issue on the jtag interface.
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
-- Rick Altherr [email protected]"He said he hadn't had a byte in three days. I had a short, so I split it with him."
-- Unsigned
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Openocd-development mailing list [email protected] https://lists.berlios.de/mailman/listinfo/openocd-development
