Re: [Openocd-development] Flashing userinterface feedback (and a bug or two?)
Try the attached patch.
It should cause an error rather than running into an infinite loop.
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
Index: C:/workspace/openocd/src/flash/str9x.c
===
--- C:/workspace/openocd/src/flash/str9x.c (revision 966)
+++ C:/workspace/openocd/src/flash/str9x.c (working copy)
@@ -305,8 +305,9 @@
{
return retval;
}
-
- while (1) {
+
+ int i;
+ for (i=0; i<1000; i++) {
if ((retval=target_read_u8(target, adr,
&status))!=ERROR_OK)
{
return retval;
@@ -315,6 +316,11 @@
break;
alive_sleep(1);
}
+ if (i==1000)
+ {
+ LOG_ERROR("erase timed out");
+ return ERROR_FAIL;
+ }
/* clear status, also clear read array */
if ((retval=target_write_u16(target, adr, 0x50))!=ERROR_OK)
@@ -571,8 +577,10 @@
/* get status command */
target_write_u16(target, bank_adr, 0x70);
-
- while (1) {
+
+ int i;
+ for (i=0; i<1000; i++)
+ {
target_read_u8(target, bank_adr, &status);
if( status & 0x80 )
break;
@@ -578,6 +586,11 @@
break;
alive_sleep(1);
}
+ if (i==1000)
+ {
+ LOG_ERROR("write timed out");
+ return ERROR_FAIL;
+ }
/* clear status reg and read array */
target_write_u16(target, bank_adr, 0x50);
@@ -614,7 +627,9 @@
/* query status command */
target_write_u16(target, bank_adr, 0x70);
- while (1) {
+ int i;
+ for (i=0; i<1000; i++)
+ {
target_read_u8(target, bank_adr, &status);
if( status & 0x80 )
break;
@@ -620,6 +635,11 @@
break;
alive_sleep(1);
}
+ if (i==1000)
+ {
+ LOG_ERROR("write timed out");
+ return ERROR_FAIL;
+ }
/* clear status reg and read array */
target_write_u16(target, bank_adr, 0x50);
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] ARM11 status
On Tue, Aug 26, 2008 at 3:54 AM, Duane Ellis <[EMAIL PROTECTED]> wrote: > Valentin Longchamp wrote: >> I am testing with a jtagkey, but also expermimenting some problems >> with svn revision from tonight. Reset halt does not seem to work for >> me: >> > Valentin, > > We had a series of emails about something with reset - and I am working > on some things dealing with event processing associated with that. > > I am unclear if this (current) problem is associated with earlier issue > - or not. > > ie: Was something that worked previously - and is now not working > Or is it something that has not worked yet. The ARM11 is in the *very* early stages of development and there are no issues with your latest patches and ARM11 that I know about. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] ARM11 status
On Mon, Aug 25, 2008 at 11:00 PM, Valentin Longchamp <[EMAIL PROTECTED]> wrote: > Hi all, > > On Mon, Aug 25, 2008 at 3:32 PM, Alan Carvalho de Assis > <[EMAIL PROTECTED]> wrote: >> Hi Oyvind, >> I am testing it with J-Link and still getting some problems. >> >> Vincent, what JTAG hardware are you using? > > I am testing with a jtagkey, but also expermimenting some problems > with svn revision from tonight. Reset halt does not seem to work for > me: > > > Here is what I get when I issue the reset halt command through telnet: > > [EMAIL PROTECTED]:~/openocd/trunk/src$ ./openocd -f > target/target/mx31.cfg -f target/interface/jtagkey.cfg I would have expected you to use configure interface first.. ./openocd -f target/interface/jtagkey.cfg -f target/target/mx31.cfg > Open On-Chip Debugger 1.0 (2008-08-25-22:50) svn:968M > $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) > Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x0c2011 > Error: Could not validate JTAG chain, continuing anyway... > Info: found ARM1136 > Warning:no telnet port specified, using default port > Warning:no gdb port specified, using default port > Warning:no tcl port specified, using default port > Info: accepting 'telnet' connection from 0 > Error: JTAG communication failure, check connection, JTAG interface, > target power etc. > Error: trying to validate configured JTAG chain anyway... > Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x00 > Error: Could not validate JTAG chain, continuing 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 > Runtime error, file "?", line 1: > > What command line do you use Oyvind ? I have noticed that the iMX31 is *VERY* sensitive on the precise implementation of the JTAG interface. It didn't work w/the parport when we tried it. On our ZY1000 reset halt works though(which uses OpenOCD): http://www.zylin.com/zy1000.html I'm not convinced that the iMX31 will work without RCLK -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] ARM11 status
Valentin Longchamp wrote:
> I am testing with a jtagkey, but also expermimenting some problems
> with svn revision from tonight. Reset halt does not seem to work for
> me:
>
Valentin,
We had a series of emails about something with reset - and I am working
on some things dealing with event processing associated with that.
I am unclear if this (current) problem is associated with earlier issue
- or not.
ie: Was something that worked previously - and is now not working
Or is it something that has not worked yet.
===
About my recent changes
===
To be clear, and to avoid any doubt -
The recent changes (patches I have done) have *NOT* and *SHOULD*NOT*
(YET) effect the process reset and associated things.
That is *the* next set of patches.
If anything was touched in the reset area, by me - the change was
functionally (or should have been functionally) this:
FROM: something like this:
if( 0 == strcmp() ){
value = THIS;
} else if( 0 == strcmp() ){
value = THAT
}
target->some_setting = value;
TO: something like this:
// call a function to lookup the value from a table
n = Jim_Nvp_name2value_simple()
target->some_setting = n->value;
-Duane.
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] ARM11 status
Hi all, On Mon, Aug 25, 2008 at 3:32 PM, Alan Carvalho de Assis <[EMAIL PROTECTED]> wrote: > Hi Oyvind, > I am testing it with J-Link and still getting some problems. > > Vincent, what JTAG hardware are you using? I am testing with a jtagkey, but also expermimenting some problems with svn revision from tonight. Reset halt does not seem to work for me: Here is what I get when I issue the reset halt command through telnet: [EMAIL PROTECTED]:~/openocd/trunk/src$ ./openocd -f target/target/mx31.cfg -f target/interface/jtagkey.cfg Open On-Chip Debugger 1.0 (2008-08-25-22:50) svn:968M $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) Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x0c2011 Error: Could not validate JTAG chain, continuing anyway... Info: found ARM1136 Warning:no telnet port specified, using default port Warning:no gdb port specified, using default port Warning:no tcl port specified, using default port Info: accepting 'telnet' connection from 0 Error: JTAG communication failure, check connection, JTAG interface, target power etc. Error: trying to validate configured JTAG chain anyway... Error: Error validating JTAG scan chain, IR mismatch, scan returned 0x00 Error: Could not validate JTAG chain, continuing 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 Runtime error, file "?", line 1: What command line do you use Oyvind ? Regards Valentin ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] ARM11 status
I am currently busy with other work and will probably look into ARM11 again later this year. Single stepping worked on 1176 last time I used it. Michael Øyvind Harboe wrote: > I've committed a couple of ARM11 fixes. > > Is anyone testing ARM11 out there? > > Single stepping seems to be broken. > > Resume & halt appears to work. > >> reset halt > JTAG device found: 0x2b900f0f (Manufacturer: 0x787, Part: 0xb900, Version: > 0x2) > JTAG device found: 0x07b3601d (Manufacturer: 0x00e, Part: 0x7b36, Version: > 0x0) > Device does not have IDCODE > JTAG device found: 0x2190101d (Manufacturer: 0x00e, Part: 0x1901, Version: > 0x2) > Error validating JTAG scan chain, IR mismatch, scan returned 0x0c2011 > Could not validate JTAG chain, continuing anyway... > found ARM1136 > r0 (INVALID) > r1 43f88000 (INVALID) > r2 43f9 (INVALID) > r3 0001 (INVALID) > r4 69a6 (INVALID) > r5 (INVALID) > r6 (INVALID) > r7 1fffc834 (INVALID) > r8 (INVALID) > r9 0001 (INVALID) > r10 0002 (INVALID) > r11 00f0 (INVALID) > r12 0001 (INVALID) > sp 1f70 (INVALID) > lr (INVALID) > pc 0040569c (INVALID) > cpsr 21d3 (INVALID) > dscr 4003 (INVALID) > Debug entry: JTAG HALT > target state: halted >> setp > Runtime error, file "?", line 1: > Unknown command: setp >> step > STEP PC 0040569c > dscr 4007 (4003) > target state: halted >> step > STEP PC 0040569c > target state: halted >> step > STEP PC 0040569c > target state: halted > ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] stellaris oddity
> - openocd from svn head (pulled some weeks ago) Stuff has happened w/reset & halting lately. Could you rerun w/openocd trunk? -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Flashing userinterface feedback (and a bug or two?)
There was a bug in the ft2232 driver where it did not
return an error in the khz==0 (RCLK) case, but rather
caused a division by 0 fault.
I've just committed a fix.
Index: C:/workspace/openocd/src/jtag/ft2232.c
===
--- C:/workspace/openocd/src/jtag/ft2232.c (revision 963)
+++ C:/workspace/openocd/src/jtag/ft2232.c (working copy)
@@ -273,6 +273,11 @@
int ft2232_khz(int khz, int *jtag_speed)
{
+ if (khz==0)
+ {
+ LOG_ERROR("RCLK not supported");
+ return ERROR_FAIL;
+ }
/* Take a look in the FT2232 manual,
* AN2232C-01 Command Processor for
* MPSSE and MCU Host Bus. Chapter 3.8
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] Flashing userinterface feedback (and a bug or two?)
Thanks for your reply, I've only now gotten back to this topic.
Øyvind Harboe wrote:
Please include a debug_level 3 log. This will tell me the origin of the error.
At first, I've run openocd -d3 and attached gdb and ran "load" of the
same old .elf file from there. Somehow this time it seemed to go into
some sort of infinite loop. I did stop openocd with ctl-c after a few
minutes or so; I've attached the compressed output of that (*.txt.gz
attachment).
I've then decided to update to the current SVN version first, rebuilt
openocd, but it is now getting a floating point exception upon startup.
See the *.txt attachment.
I'll maybe look into that further (git-bisect the FPE down to the point
where it has been introduced), let me see. Maybe I'll not get this done
today.
Christian.
openocd-log-of-gdb-load.txt.gz
Description: GNU Zip compressed data
Author: oharboe <[EMAIL PROTECTED]>
Date: Mon Aug 25 13:18:55 2008 +
STR912 uses RCLK if available
git-svn-id: svn://svn.berlios.de/openocd/[EMAIL PROTECTED]
b42882b7-edfa-0310-969c-e2dbd0fdcd60
[EMAIL PROTECTED]:~$ openocd
Open On-Chip Debugger 1.0 (2008-08-25-16:17) svn:exported
$URL$
jtag_khz: 0
Floating point exception
[EMAIL PROTECTED]:~$ gdb openocd
(gdb) run
Starting program: /mnt/rootextend/chrisarm/bin/openocd
Open On-Chip Debugger 1.0 (2008-08-25-16:17) svn:exported
$URL$
jtag_khz: 0
Program received signal SIGFPE, Arithmetic exception.
0x004456ea in ft2232_khz (khz=0, jtag_speed=0x6bd920)
at /home/chrisarm/src/openocd-svngit--trunk/src/jtag/ft2232.c:291
291 *jtag_speed = *jtag_speed / 10;
(gdb) p *jtag_speed
$1 = 0
(gdb) bt full
#0 0x004456ea in ft2232_khz (khz=0, jtag_speed=0x6bd920)
at /home/chrisarm/src/openocd-svngit--trunk/src/jtag/ft2232.c:291
No locals.
#1 0x004428a6 in jtag_interface_init (cmd_ctx=)
at /home/chrisarm/src/openocd-svngit--trunk/src/jtag/jtag.c:1542
__FUNCTION__ = "jtag_interface_init"
#2 0x00402871 in handle_init_command (cmd_ctx=0x6d2010, cmd=,
args=, argc=)
at /home/chrisarm/src/openocd-svngit--trunk/src/openocd.c:109
retval = 0
initialized = 1
__FUNCTION__ = "handle_init_command"
#3 0x0044b080 in run_command (context=0x6d2010, c=0x6e7920,
words=,
num_words=)
at /home/chrisarm/src/openocd-svngit--trunk/src/helper/command.c:379
retval =
__FUNCTION__ = "run_command"
#4 0x0044c296 in script_command (interp=0x6d2040, argc=,
argv=0x7fff1f6184c0) at
/home/chrisarm/src/openocd-svngit--trunk/src/helper/command.c:117
c = (command_t *) 0x6e7920
context =
retval =
i = 1
tclOutput =
__FUNCTION__ = "script_command"
#5 0x0045a6df in Jim_EvalObj (interp=0x6d2040, scriptObjPtr=0x6eb890)
at /home/chrisarm/src/openocd-svngit--trunk/src/helper/jim.c:8582
expand = 0
argc = 1
cmd =
i = 2
j = 1
len = 2
script = (ScriptObj *) 0x708840
token = (ScriptToken *) 0x709880
cs = (int *) 0x6f7488
retcode =
sargv = {0x6eb6d0, 0x6d2040, 0x7fff1f6184e0, 0x7fff1f6184f0, 0x6eba40,
0x6e6d50, 0x6eb7e4,
0x450c5f}
argv = (Jim_Obj **) 0x7fff1f6184c0
tmpObjPtr = (Jim_Obj *) 0x6eb950
#6 0x0045a6df in Jim_EvalObj (interp=0x6d2040, scriptObjPtr=0x6ebc50)
at /home/chrisarm/src/openocd-svngit--trunk/src/helper/jim.c:8582
expand = 0
argc = 2
cmd =
i = 5
j = 2
len = 5
script = (ScriptObj *) 0x707cd0
token = (ScriptToken *) 0x705e10
cs = (int *) 0x6f772c
retcode =
sargv = {0x6eb950, 0x6eb890, 0x4, 0x6e8510, 0x8, 0x6ebed0, 0x6d2040,
0x6f7950}
argv = (Jim_Obj **) 0x7fff1f6185b0
tmpObjPtr = (Jim_Obj *) 0x6eb890
#7 0x0045ee49 in Jim_CatchCoreCommand (interp=0x6d2040, argc=2,
argv=0x7fff1f6186d0)
at /home/chrisarm/src/openocd-svngit--trunk/src/helper/jim.c:11224
exitCode =
#8 0x0045a6df in Jim_EvalObj (interp=0x6d2040, scriptObjPtr=0x6ebed0)
at /home/chrisarm/src/openocd-svngit--trunk/src/helper/jim.c:8582
expand = 0
argc = 2
cmd =
i = 4
j = 2
len = 4
script = (ScriptObj *) 0x6f7950
token = (ScriptToken *) 0x6e84b0
cs = (int *) 0x6eaa0c
retcode =
sargv = {0x6ebb00, 0x6ebc50, 0x1, 0x6e7d72, 0x6e7d72,
0x60001, 0x1, 0x1}
argv = (Jim_Obj **) 0x7fff1f6186d0
tmpObjPtr = (Jim_Obj *) 0x6006d2040
#9 0x0045baea in Jim_EvalExpression (interp=0x6d2040,
exprObjPtr=0x6ea500,
exprResultPtrPtr=0x7fff1f61)
at /home/chrisarm/src/openocd-svngit--trunk/src/helper/jim.c:6838
A = (Jim_Obj *) 0x1
wC =
Alen = 0
B = (Jim_Obj *) 0x1
dA = 2.2438154347543339e-317
retcode =
wA = 9
dB = 3.64
Re: [Openocd-development] ARM11 status
s/Vincent/Valentin ;-) 2008/8/25 Alan Carvalho de Assis <[EMAIL PROTECTED]>: > Hi Oyvind, > I am testing it with J-Link and still getting some problems. > > Vincent, what JTAG hardware are you using? > > Best Regards, > > Alan > > 2008/8/25 Øyvind Harboe <[EMAIL PROTECTED]>: >> I've committed a couple of ARM11 fixes. >> >> Is anyone testing ARM11 out there? >> >> Single stepping seems to be broken. >> >> Resume & halt appears to work. >> >>> reset halt >> JTAG device found: 0x2b900f0f (Manufacturer: 0x787, Part: 0xb900, Version: >> 0x2) >> JTAG device found: 0x07b3601d (Manufacturer: 0x00e, Part: 0x7b36, Version: >> 0x0) >> Device does not have IDCODE >> JTAG device found: 0x2190101d (Manufacturer: 0x00e, Part: 0x1901, Version: >> 0x2) >> Error validating JTAG scan chain, IR mismatch, scan returned 0x0c2011 >> Could not validate JTAG chain, continuing anyway... >> found ARM1136 >> r0 (INVALID) >> r1 43f88000 (INVALID) >> r2 43f9 (INVALID) >> r3 0001 (INVALID) >> r4 69a6 (INVALID) >> r5 (INVALID) >> r6 (INVALID) >> r7 1fffc834 (INVALID) >> r8 (INVALID) >> r9 0001 (INVALID) >> r10 0002 (INVALID) >> r11 00f0 (INVALID) >> r12 0001 (INVALID) >> sp 1f70 (INVALID) >> lr (INVALID) >> pc 0040569c (INVALID) >>cpsr 21d3 (INVALID) >>dscr 4003 (INVALID) >> Debug entry: JTAG HALT >> target state: halted >>> setp >> Runtime error, file "?", line 1: >>Unknown command: setp >>> step >> STEP PC 0040569c >>dscr 4007 (4003) >> target state: halted >>> step >> STEP PC 0040569c >> target state: halted >>> step >> STEP PC 0040569c >> target state: halted >> >> -- >> Øyvind Harboe >> http://www.zylin.com/zy1000.html >> ARM7 ARM9 XScale Cortex >> JTAG debugger and flash programmer >> ___ >> Openocd-development mailing list >> Openocd-development@lists.berlios.de >> https://lists.berlios.de/mailman/listinfo/openocd-development >> > ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
Re: [Openocd-development] ARM11 status
Hi Oyvind, I am testing it with J-Link and still getting some problems. Vincent, what JTAG hardware are you using? Best Regards, Alan 2008/8/25 Øyvind Harboe <[EMAIL PROTECTED]>: > I've committed a couple of ARM11 fixes. > > Is anyone testing ARM11 out there? > > Single stepping seems to be broken. > > Resume & halt appears to work. > >> reset halt > JTAG device found: 0x2b900f0f (Manufacturer: 0x787, Part: 0xb900, Version: > 0x2) > JTAG device found: 0x07b3601d (Manufacturer: 0x00e, Part: 0x7b36, Version: > 0x0) > Device does not have IDCODE > JTAG device found: 0x2190101d (Manufacturer: 0x00e, Part: 0x1901, Version: > 0x2) > Error validating JTAG scan chain, IR mismatch, scan returned 0x0c2011 > Could not validate JTAG chain, continuing anyway... > found ARM1136 > r0 (INVALID) > r1 43f88000 (INVALID) > r2 43f9 (INVALID) > r3 0001 (INVALID) > r4 69a6 (INVALID) > r5 (INVALID) > r6 (INVALID) > r7 1fffc834 (INVALID) > r8 (INVALID) > r9 0001 (INVALID) > r10 0002 (INVALID) > r11 00f0 (INVALID) > r12 0001 (INVALID) > sp 1f70 (INVALID) > lr (INVALID) > pc 0040569c (INVALID) >cpsr 21d3 (INVALID) >dscr 4003 (INVALID) > Debug entry: JTAG HALT > target state: halted >> setp > Runtime error, file "?", line 1: >Unknown command: setp >> step > STEP PC 0040569c >dscr 4007 (4003) > target state: halted >> step > STEP PC 0040569c > target state: halted >> step > STEP PC 0040569c > target state: halted > > -- > Øyvind Harboe > http://www.zylin.com/zy1000.html > ARM7 ARM9 XScale Cortex > JTAG debugger and flash programmer > ___ > Openocd-development mailing list > Openocd-development@lists.berlios.de > https://lists.berlios.de/mailman/listinfo/openocd-development > ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] jtag_rclk command & STR912 now uses RCLK
Committed
STR912 now uses RCLK if available.
Added jtag_rclk that can be used to set rclk w/fallback to a given
frequency.
> help jtag_rclk
jtag_rclk fallback_speed_khz - set JTAG speed to RCLK or use
fallback speed
Index: C:/workspace/openocd/src/helper/startup.tcl
===
--- C:/workspace/openocd/src/helper/startup.tcl (revision 966)
+++ C:/workspace/openocd/src/helper/startup.tcl (working copy)
@@ -160,4 +160,14 @@
# Fix!!! we're resetting all targets here! Really we should reset only
# one target
reset halt
-}
\ No newline at end of file
+}
+
+
+# If RCLK is not supported, use fallback_speed_khz
+proc jtag_rclk {fallback_speed_khz} {
+ if {[catch {jtag_khz 0}]!=0} {
+ jtag_khz $fallback_speed_khz
+ }
+}
+
+add_help_text jtag_rclk "fallback_speed_khz - set JTAG speed to RCLK
or use fallback speed"
\ No newline at end of file
Index: C:/workspace/openocd/src/target/target/str912.cfg
===
--- C:/workspace/openocd/src/target/target/str912.cfg (revision 966)
+++ C:/workspace/openocd/src/target/target/str912.cfg (working copy)
@@ -2,9 +2,9 @@
# jtag speed. We need to stick to 16kHz until we've finished reset.
-jtag_khz 16
+jtag_rclk 16
proc target_0_pre_reset {} {
- jtag_khz 16
+ jtag_rclk 16
}
proc target_0_post_reset {} {
@@ -9,7 +9,7 @@
proc target_0_post_reset {} {
# We can increase speed now that we know the target is halted.
- jtag_khz 3000
+ jtag_rclk 3000
# -- Enable 96K RAM
# PFQBC enabled / DTCM & AHB wait-states disabled
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] ARM11 status
I've committed a couple of ARM11 fixes. Is anyone testing ARM11 out there? Single stepping seems to be broken. Resume & halt appears to work. > reset halt JTAG device found: 0x2b900f0f (Manufacturer: 0x787, Part: 0xb900, Version: 0x2) JTAG device found: 0x07b3601d (Manufacturer: 0x00e, Part: 0x7b36, Version: 0x0) Device does not have IDCODE JTAG device found: 0x2190101d (Manufacturer: 0x00e, Part: 0x1901, Version: 0x2) Error validating JTAG scan chain, IR mismatch, scan returned 0x0c2011 Could not validate JTAG chain, continuing anyway... found ARM1136 r0 (INVALID) r1 43f88000 (INVALID) r2 43f9 (INVALID) r3 0001 (INVALID) r4 69a6 (INVALID) r5 (INVALID) r6 (INVALID) r7 1fffc834 (INVALID) r8 (INVALID) r9 0001 (INVALID) r10 0002 (INVALID) r11 00f0 (INVALID) r12 0001 (INVALID) sp 1f70 (INVALID) lr (INVALID) pc 0040569c (INVALID) cpsr 21d3 (INVALID) dscr 4003 (INVALID) Debug entry: JTAG HALT target state: halted > setp Runtime error, file "?", line 1: Unknown command: setp > step STEP PC 0040569c dscr 4007 (4003) target state: halted > step STEP PC 0040569c target state: halted > step STEP PC 0040569c target state: halted -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
[Openocd-development] Problems with latest GDB from CVS HEAD and Eclipse
Eclipse and GDB from CVS HEAD are *not* friends. Eclipse seems to be unable to pick up when the target is running/halted w/the latest version of Eclipse + GDB CVS HEAD. I mention this due to Spen's work on no-ack support. -- Øyvind Harboe http://www.zylin.com/zy1000.html ARM7 ARM9 XScale Cortex JTAG debugger and flash programmer ___ Openocd-development mailing list Openocd-development@lists.berlios.de https://lists.berlios.de/mailman/listinfo/openocd-development
