Hi all,
On Tue, Aug 19, 2008 at 3:56 PM, Øyvind Harboe <[EMAIL PROTECTED]> wrote:
> I've committed this patch, even if it is work in progress, as
> there are also other changes to jtag.c going on at this time
> and synchronizing work takes priority.
>
I have given it a try, I cann connect with gdb, however I have further
error later, telling me that the "target has not been examined yet".
Is this a problem that is going to cause bad behavior with gdb ? Is
this what you mean Oyvind when you say the patch is work in progress ?
Here is the beginning of the log I get with using the gdbinit script
Alan sent me for i.MX31
Open On-Chip Debugger 1.0 (2008-08-19-20:07) svn:946M
$URL: svn://svn.berlios.de/openocd/trunk/src/openocd.c $
jtag_speed: 10
Info: JTAG device found: 0x2b900f0f (Manufacturer: 0x787, Part:
0xb900, Version: 0x2)
Info: JTAG device found: 0x07b3601d (Manufacturer: 0x00e, Part:
0x7b36, Version: 0x0)
Warning:Device does not have IDCODE
Info: JTAG device found: 0x1190101d (Manufacturer: 0x00e, Part:
0x1901, Version: 0x1)
Info: found ARM1136
Warning:no telnet port specified, using default port 4444
Warning:no gdb port specified, using default port 3333
Warning:no tcl port specified, using default port 6666
Info: accepting 'gdb' connection from 0
Error: Target not examined yet
Warning:acknowledgment received, but no packet pending
Error: Target not examined yet
Error: unexpected error -4
Runtime error, file "?", line 1:
Unknown command: endian_little
In procedure 'endian' called at file "?", line 1
In procedure 'unknown' called at file "?", line 1
Error: JTAG communication failure, check connection, JTAG interface,
target power etc.
Error: trying to validate configured JTAG chain anyway...
Warning:value captured during scan didn't pass the requested check:
captured: 0x00 check_value: 0x01 check_mask: 0x1f
Warning:in_handler reported a failed check
Warning:value captured during scan didn't pass the requested check:
captured: 0x00 check_value: 0x01 check_mask: 0x1f
Warning:in_handler reported a failed check
Error: 'arm11 target' JTAG communication error SCREG SCAN OUT 0x00
(expected 0x10)
Warning:in_handler reported a failed check
Warning:value captured during scan didn't pass the requested check:
captured: 0x00 check_value: 0x01 check_mask: 0x1f
Warning:in_handler reported a failed check
Error: 'target arm11' expects IDCODE 0x*7B*7****
Runtime error, file "?", line 1:
register idcode not found in current target
register control not found in current target
register pport_memory_remap not found in current target
Runtime error, file "?", line 1:
Unknown command: long_0x53FC0000_=_0x040
In procedure 'long' called at file "?", line 1
In procedure 'unknown' called at file "?", line 1
In procedure 'long_0x53FC0000' called at file "?", line 1
In procedure 'unknown' called at file "?", line 1
In procedure 'long_0x53FC0000_=' called at file "?", line 1
In procedure 'unknown' called at file "?", line 1
Runtime error, file "?", line 1:
Unknown command: long_0x53F80000_=_0x074B0B7D
In procedure 'long' called at file "?", line 1
In procedure 'unknown' called at file "?", line 1
In procedure 'long_0x53F80000' called at file "?", line 1
In procedure 'unknown' called at file "?", line 1
In procedure 'long_0x53F80000_=' called at file "?", line 1
In procedure 'unknown' called at file "?", line 1
Runtime error, file "?", line 1:
Alan: has this script worked for you with openocd ? You had asked me a
while ago, but I only have had time to test it yesterday evening.
Oyvind: I think there are a lot of other things that need to be fixed
in jtag.c so that the bad i.MX31 jtag chain can be supported (the
target not examined yet error for instance) ? Is it worth doing it now
or should we wait for Duane to have progressed in his changes ?
Regards
Valentin
_______________________________________________
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
