Hi Evan,
w.r.t. the checksum command, I'm thinking it would be better to
implement it as a tcl command so i can be used in Tcl code:
if {![verify_image_checksum]} {#do some stuff here}
You'll probably need to post the ft2232 patch in a separate subject to get
some reaction.
--
Øyvind Harboe
Am 05/26/2011 10:47 PM, schrieb Paul Claessen:
>
> Thanks for your much appreciated quick response.
> I'm using my own .cfg for file an Olimex Tiny. I simply added the
> suggested 'adapter_khz' (with value 1000, although I'm not sure what a
> reasonable value would be; I guess that depends on the t
Evan
> Could you provide a list of what order you give GDB/OpenOCD commands and
> which GDB-Remote commands/responses you see?
I have attached two files. gdb_trace.txt shows two runs through the
same sequence of events:
- attach to the remote target
- reset the target
- set breakpoint
- run to b
From: Michael Schwingen
Sent: Thursday, May 26, 2011 3:26 PM
To: Paul Claessen
Cc: openocd-development@lists.berlios.de
Subject: Re: [Openocd-development] Error: .. adapter speed not selected
Am 05/26/2011 09:12 PM, schrieb Paul Claessen:
In April (2011) I built openocd version 0.5.0-dev-0085
Am 05/26/2011 09:12 PM, schrieb Paul Claessen:
> In April (2011) I built openocd version 0.5.0-dev-00858 and used it
> successfully with an Olimex OpenOCD JTAG Tiny.
> I recently built version 0.5.0-dev-00882 and I now get the following
> error:
>
> Error: An adapter speed is not selected in the
In April (2011) I built openocd version 0.5.0-dev-00858 and used it
successfully with an Olimex OpenOCD JTAG Tiny.
I recently built version 0.5.0-dev-00882 and I now get the following error:
Error: An adapter speed is not selected in the init script. Insert a call to
adapter_khz or jtag_rclk to
The driver works great. Here is my experience with it. I went to openocd,
Downloaded the get repo, built. The first time I flashed code, everything
Worked great. The second time, I ran into issues.
When I was trying to flash, I got the follow:
Error: JTAG-DP STICKY ERROR
Error: MEM_AP_CSW 0x
simon qian writes:
>
>
> It's fast for 27kBytes/s for flash + erase. STM32F200 has 16M internal RC, so
> the JTAG can run at 2.5M.
>
> As I test for STM32F100, flash programming is usually at 13KBytes/s under
> OpenOCD.
>
>
> ST website is not available in China, I don't know the state of ST
Hi!
I'm trying to compile new OpenOCD source (from git) in my
crosscompilation setup but I see these errors:
/../../src/rtos/'`rtos.c
libtool: compile: i686-w64-mingw32-gcc -std=gnu99 -DHAVE_CONFIG_H -I.
-I../../../src/rtos -I../.. -I../../../src -I../../src
-DPKGDATADIR=\"/usr/local/share
> Ah, I forgot to mention the most important - to be able to realize
> transport I have extended "struct jtag_interface" with "transfer_bits"
> and "signal_operate" methods that transfer bitstream out/in of the
> char array and can switch/read specified signal (exactly what you
> need). "queue_exec
> Could you provide a list of what order you give GDB/OpenOCD commands and
> which GDB-Remote commands/responses you see?
I'm remote from my test hardware at the moment - I'll try to do that
as soon as possible
> The way I did it in the RTOS’s was that if the current thread was set to 0
> or 1 th
> Sorry but I only know stm32x... could you pls give a name to the "other one"?
cd src
find . | grep stm32
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
J
Øyvind Harboe writes:
>
> There is more than one stm32 flash driver, use the "other one"
>
Sorry but I only know stm32x... could you pls give a name to the "other one"?
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https
There is more than one stm32 flash driver, use the "other one"
--
Øyvind Harboe
Can Zylin Consulting help on your project?
US toll free 1-866-980-3434 / International +47 51 87 40 27
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
___
Hi Sylvain,
I have exactly the same eval board and also the same OpenOCD issue when trying
to write the binary on the STM32F2 flash:
device id = 0x20006411
Cannot identify target as a STM32 family.
Did you succeed in updating OpenOCD sources?
BR,
Bruno
This patch fixes an obvious bug.
Unless I hear objections, I will merge.
That said, there may be other code that is building upon this broken behavior
that needs to get fixed afterwards.
If I see fixes for those followup bugs in short order, I'd be inclined to wait
until we have a sequence of pa
>> Btw.: There is still an endianness issue with mips target. Drasko adds
>> endianness swapping (that I removed two years ago)
> Why did you remove it ?
I removed swapping in mips_m4k, because for commands like mdw the swapping was
already done in target.c. If a target was selected as big endia
Looking at this patch, it's clearly wrong to cast a pointer to a host 32 bit
integer to a pointer to a sequence of bytes to shift out.
I don't know about the rest of the issues offhand, but I see Drask was
going to have a look at it.
--
Øyvind Harboe
Can Zylin Consulting help on your project
On Wed, May 25, 2011 at 4:28 PM, Mahr, Stefan wrote:
> Hi,
>
> attached patch fixes the endianess so mips/ejtag can be used on a big endian
> host.
>
>
> Btw.: There is still an endianness issue with mips target. Drasko adds
> endianness swapping (that I removed two years ago)
Why did you remov
19 matches
Mail list logo
