On Tuesday 29 September 2009, Øyvind Harboe wrote:
If no -expected-id's listed then do not check ID's.
Not really. First, there's the BYPASS case. Second,
it isn't not checking ... it's just spewing different
noise than came from the message posted earlier today.
(And not what I'd call better
From: openocd-development-boun...@lists.berlios.de [mailto:openocd-
development-boun...@lists.berlios.de] On Behalf Of David Brownell
Sent: dinsdag 29 september 2009 20:44
To: simon qian
Cc: openocd-development@lists.berlios.de
Subject: Re: [Openocd-development] OUT macro redefined under
OK. I'm convinced that we're in pretty good shape now
and that we should let this be until the next crossroads.
--
Øyvind Harboe
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Openocd-development
We can, and sometimes we want to, write to memory while the CortexA8
core is running,
but for gbd to load a program and the i-caches to be cleared to core
must be halted.
So I think there must be a monitor halt after the monitor omap3_dbginit
No. I just do
arm-none-linux-gnueabi-gdb
Magnus Lundin wrote:
We can, and sometimes we want to, write to memory while the CortexA8
core is running,
but for gbd to load a program and the i-caches to be cleared to core
must be halted.
Yes, thanks!
Attachment now gives me:
-- cut --
arm-none-linux-gnueabi-gdb
GNU gdb 6.8
Copyright
David Brownell wrote:
I think that's not quite following the model which the code in
the src/helper/startup.tcl file is expecting ... a closer match
would use reset-assert-pre (or maybe post) not reset-start.
I have done some more testing and trying to understand the reset
handling in
1. put reset_on_init patch that I submitted earlier and make it
dependent on hardware used to access JTAG.
Where is this patch?
2. put in udev rules a small program that will de-assert srst. I am not
sure if would be committed to openocd tree?
Comments or ideas?
Remove the initial scan of
