On Jan 16, 2009, at 7:30 AM, Alan Carvalho de Assis wrote:
Hi Rick,On Wed, Jan 14, 2009 at 10:09 PM, Rick Altherr <[email protected]> wrote:Typically you would create a separate config that sources the interface and target configs. See the included board configs for examples. In that file, you would add the jtag_khz line as appropriate. I'm not sure what the default for JLink is. A value of 0 typically means "use RCLK." If you told JLink to use RCLK but the target doesn't support it, I'm not sure what wouldhappen.It didn't work. I tested setting jtag_khz but it still not working. I compared output when using axm0432 interface versus jlink output: JLink always stop here: Info : 91 358 arm11.c:1595 arm11_examine(): found ARM1136 Debug: 92 358 arm11.c:1625 arm11_examine(): IDCODE 07b3601d IMPLEMENTOR 41 DIDR 15110004Debug: 93 364 arm11.c:328 arm11_check_init(): Bringing target into debug modeAXM0432 interface show: Info : 118 485 arm11.c:1595 arm11_examine(): found ARM1136 Debug: 119 485 arm11.c:1625 arm11_examine(): IDCODE 07b3601d IMPLEMENTOR 41 DIDR 15110004Debug: 120 489 arm11.c:328 arm11_check_init(): Bringing target into debug mode Debug: 121 539 openocd.c:160 handle_init_command(): jtag examine complete Debug: 122 539 openocd.c:166 handle_init_command(): flash init complete Debug: 123 539 openocd.c:170 handle_init_command(): mflash init completeDebug: 124 539 openocd.c:174 handle_init_command(): NAND init complete Debug: 125 539 openocd.c:178 handle_init_command(): pld init complete Debug: 126 539 gdb_server.c:2225 gdb_init(): gdb service for target arm11 at port 3333 Warn : 127 539 tcl_server.c:178 tcl_init(): no tcl port specified, using default port 6666 User : 128 539 command.c:494 command_run_line(): Debug: 129 551 arm11.c:662 arm11_poll(): DSCR 00004002 Debug: 130 662 arm11.c:662 arm11_poll(): DSCR 00004002 Debug: 131 759 arm11.c:662 arm11_poll(): DSCR 00004002 Debug: 132 867 arm11.c:662 arm11_poll(): DSCR 00004002 Debug: 133 975 arm11.c:662 arm11_poll(): DSCR 00004002 Do you some other idea?-- Rick Altherr [email protected]"He said he hadn't had a byte in three days. I had a short, so I split itwith him." -- UnsignedBest Regards, Alan
Not really. If just a change in the interface causes the problem, you can probably narrow it down to either a driver bug in OpenOCD or an electrical difference. Try hooking a scope to the JTAG clock and see if it looks reasonable.
-- 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
