On Mon, Dec 28, 2009 at 2:45 AM, David Brownell davi...@pacbell.net wrote:
On Monday 21 December 2009, Yegor Yefremov wrote:
My board rev: LMWLV-B
Could you forward the USB IDs and device string of your
board? I notice that tcl/interface/luminary-lm3s811.cfg
doesn't include the USB IDs, so
Otherwise the new alignment checking algorithm thinks that the
address is not aligned, because it is way beyond the last sector.
--
My blog: http://www.esden.net
My projects: http://open-bldc.org,
http://openmulticopter.org,
http://multicopter.org
The already announced Open-BLDC board config file. ;)
Cheers Esden
--
My blog: http://www.esden.net
My projects: http://open-bldc.org,
http://openmulticopter.org,
http://multicopter.org
0002-Added-Open-BLDC-board-config-file.patch
Description: Binary data
I'm fooling with a cable modem that has a MIPS 4kc processor and cfi
type flash chip from ST: M28W160CT. Flash configuration is as follows:
flash bank cfi 0x9000 0X20 2 2 $_TARGETNAME
openocd-0.2.0 has no problem detecting the flash with flash_probe
Some other differences I've noted
On 2009-12-26 21:10, David Brownell wrote:
You could however use %ld and cast the value to long,
given that this GCC is ancient enough that z loses.
See the attached patch... (as a bonus I've converted byte to bytes
in two files, as it should probably be this way...).
4\/3!!
From
On 2009-12-24 08:34, David Brownell wrote:
BTW the help message for stm32x mass_erase is wrong - it's missing the
info about the required bank number (0).
Feel free to submit a patch...
See the attached patch - now help stm32x prints all the parameters
4\/3!!
From
On Monday 28 December 2009, Piotr Esden-Tempski wrote:
Otherwise the new alignment checking algorithm thinks that the
address is not aligned, because it is way beyond the last sector.
Looks like a good patch, I'll merge.
___
Openocd-development
On Monday 28 December 2009, Yegor Yefremov wrote:
On Mon, Dec 28, 2009 at 2:45 AM, David Brownell davi...@pacbell.net wrote:
On Monday 21 December 2009, Yegor Yefremov wrote:
My board rev: LMWLV-B
Could you forward the USB IDs and device string of your
board? I notice that
On Monday 28 December 2009, Freddie Chopin wrote:
On 2009-12-24 08:34, David Brownell wrote:
BTW the help message for stm32x mass_erase is wrong - it's missing the
info about the required bank number (0).
Feel free to submit a patch...
See the attached patch - now help stm32x prints
On 2009-12-24 21:55, David Brownell wrote:
On Thursday 24 December 2009, Freddie Chopin wrote:
On 2009-12-24 08:34, David Brownell wrote:
That's a bunch of very off-topic messages for what looks
more like you mis-spelled 'address' ...
Ups [; Isn't there a way to thorow something like unknown
On Dec 28, 2009, at 8:52 PM, David Brownell wrote:
On Monday 28 December 2009, Piotr Esden-Tempski wrote:
Otherwise the new alignment checking algorithm thinks that the
address is not aligned, because it is way beyond the last sector.
Looks like a good patch, I'll merge.
Very nice! I am
-Original Message-
From: openocd-development-boun...@lists.berlios.de [mailto:openocd-
development-boun...@lists.berlios.de] On Behalf Of Øyvind Harboe
Sent: Thursday, December 24, 2009 1:09 AM
To: Austin, Alex
Cc: Laurent Gauch; openocd-development@lists.berlios.de
Subject: Re:
The refactor is not to support our patch, just to clean up the ft2232
driver. My comment is in response to something that was said should
probably be done anyway, not specifically to support our device. I
think support for our device could be done without said refactor, but
the code would be
On Monday 16 November 2009, Andrew Rogers wrote:
Do you think that if I were to break this patch down into many really
small patches it would be put into the master openocd branch?
Well, one humongous patch won't get merged, so it's got to get
broken down into logical chunks in any case. I'd
I'm asking -- and in part, answering -- this question to help
get most folk on the same page (as the saying goes) about
this work, which should help future discussions. Feel free
to follow up with corrections and other significant points.
Serial Wire Debug (SWD) is a two-wire protocol that ARM
Here are a few technical comments on Simon's patch.
I'll start by using the diffstat output as a prop, and may
include details later ... possibly in separate threads.
src/jtag/commands.h | 21 ++-
src/jtag/core.c | 29
src/jtag/driver.c | 79 +++
We
I'm so sorry that I'm asking such basic question but I cannot find the
answer (I checked/asked google, openmoko mailing lists, irc, archives
etc.). On OpenOCD website it was stated to ask question on this mailing
list.
The config file liked from OpenMoko wiki
On Saturday 14 November 2009, Andrew Rogers wrote:
SWD is not finished yet, a long way to go. Adding the actual hardware
drivers is a almost the last thing on my list. I want to get the
framework in place first.
I don't entirely agree about almost the last thing, since that
can make
Ask they guys who wrote the page to update it. It's hopelessly out
of date by the looks of it.
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
http://www.zylin.com/zy1000.html
ARM7 ARM9 ARM11 XScale Cortex
JTAG debugger and flash programmer
I'm not quite up to speed on the SWD stuff yet, but I want
to follow this closely enough that I can implement hardware
acceleration of the SWD protocol on the ZY1000(an embedded
OpenOCD host).
What embedded hosts offers is very low processing power(on par
with an arm7/9 or so), but also very low
Zach did a round of cleaning that up, but it needs
one more I guess.
Definitely something we want to merge post 0.4 though, I
fear there are some sticky issues w.r.t. deleting the right
bits of code in there...
--
Øyvind Harboe
US toll free 1-866-980-3434 / International +47 51 63 25 00
21 matches
Mail list logo
