David Brownell escreveu:
>> +
>> +#jtag scan chain
>> +jtag newtap $_CHIPNAME cpu -irlen 4 -ircapture 1 -irmask 0xf -expected-id
>> $_CPUTAPID
>
> I'm thinking the DAP should be labeled as "dap" not "cpu" ...
IMHO it should be kept as is... when I first saw that, moving to 0.2.0,
I could unders
Hi Gary,
I was a little bit conservative with the frequency. The following quote
is taken from the datasheet of the AT91SAM9260:
"Note the maximum JTAG clock rate on ARM926EJ-S cores is 1/6th the clock
of the CPU. This gives 5.45 kHz maximum initial JTAG clock rate for an
ARM9E running from th
Hi Gary,
I think the 8 kHz is the problem here. I have read somewhere that the
CPU speed must be 16 times faster than the jtag speed for reliable
operation.
This means that with a 32 kHz clock, the jtag speed must be 2 kHz, or
lower. I have tried myself and it seems to work correctly at 4 kHz a
On Friday 07 August 2009, Spencer Oliver wrote:
> Oops - looks like a bug was introduced during the cortex reg cleanup.
> fix has been commited to svn.
Sorry about that ... this would be one reason many folk
dislike count-down array iterators, even though they are
a bit faster on most CPUs: it's
On Friday 07 August 2009, Xiaofan Chen wrote:
> +if { [info exists CPUTAPID ] } {
> + set _CPUTAPID $CPUTAPID
> +} else {
> + # force an error till we get a good number
> + set _CPUTAPID 0x3ba00477
But that *is* a "good" number ... strike that comment
> +}
> +
> +#jtag scan chain
> +jtag ne
The following patch will add chip support for LM3S1968 and
board config file for EK-LM3S1968. Tested against SVN2578.
Index: tcl/target/lm3s1968.cfg
===
--- tcl/target/lm3s1968.cfg (revision 0)
+++ tcl/target/lm3s1968.cfg (rev
On Fri, Aug 7, 2009 at 9:18 PM, Xiaofan Chen wrote:
> On Fri, Aug 7, 2009 at 5:10 PM, Spencer Oliver wrote:
>> Oops - looks like a bug was introduced during the cortex reg cleanup.
>> fix has been commited to svn.
>
> Thanks. This fixed the issue I have with EK-LM3S1968 and the
> on-board FTDI inte
On Fri, Jul 31, 2009 at 8:24 PM, Xiaofan Chen wrote:
I am also having problem with J-Link with the EK-LM3S1968. It
is not able to flash the flash. I've tried V3 and V6 IAR OEM version of
J-Link. Take note the on-board ftdi interface works fine with the same
svn version 2570.
>>>
On Fri, Jul 31, 2009 at 9:33 PM, Xiaofan Chen wrote:
>> Not really. It seems that some Ubuntu 9.04 updates yesterday messed up with
>> OpenOCD now. Actually it crashed now with ftdi interface.
>>
>
> The same result for Arch Linux with the latest svn version V2571.
> Again release version V0.2.0 wo
> -Original Message-
> From: openocd-development-boun...@lists.berlios.de
> [mailto:openocd-development-boun...@lists.berlios.de] On
> Behalf Of David Brownell
> Sent: 05 August 2009 18:37
> To: openocd-development@lists.berlios.de
> Subject: [Openocd-development] [patch] don't display i
On Fri, Aug 7, 2009 at 5:10 PM, Spencer Oliver wrote:
>>
>> I'm using openocd under Ubuntu64 with libftdi and a TI
>> Luminary Stellaris Microcontroller (Cortex-M3)
>>
>> Since R2554 i got a segmentation fault while writing program
>> to flash memory. I think i could be a problem with David
>> Brow
> -Original Message-
> From: openocd-development-boun...@lists.berlios.de
> [mailto:openocd-development-boun...@lists.berlios.de] On
> Behalf Of David Brownell
> Sent: 05 August 2009 18:36
> To: openocd-development@lists.berlios.de
> Subject: [Openocd-development] [patch] warning on "j
> Better explanation for the TAP "-ircapture" parameter.
> ---
> doc/openocd.texi |5 -
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> --- a/doc/openocd.texi
> +++ b/doc/openocd.texi
> @@ -2198,7 +2198,10 @@ Every TAP requires at least the followin
>
> @itemize @bullet
> @item @
> I found a solution to my problem. It seems that this module
> needs one clock cycle in state RUN TEST/IDLE between the
> setting of the vector catch and the reset. Then it works
> perfectly. I tested it with the RTCK-feature and on 1 kHz, 2
> kHz and 4 kHz. It didn't work at 8kHz, because the
>
> I'm using openocd under Ubuntu64 with libftdi and a TI
> Luminary Stellaris Microcontroller (Cortex-M3)
>
> Since R2554 i got a segmentation fault while writing program
> to flash memory. I think i could be a problem with David
> Brownell's patch.
>
Oops - looks like a bug was introduce
On Fri, Aug 7, 2009 at 2:33 PM, Marcel Jost wrote:
> Hi
>
> I'm using openocd under Ubuntu64 with libftdi and a TI Luminary Stellaris
> Microcontroller (Cortex-M3)
>
> Since R2554 i got a segmentation fault while writing program to flash
> memory. I think i could be a problem with David Brownell's
16 matches
Mail list logo
