Committed.
Thanks!
1. How do I speed up flash writes. Right now, I get about 2kB/s write to
NOR (see flashUBOOT proc).
the arm11 needs the run_algorithm support. Known problem, sombody
needs to pitch in, it's not super hard.
2. Is there a way to run openocd and flash write command from the
Hello all.
This is my first attempt to contribute to open projects.
Do not judge strictly, please.
The current state of the driver: support imx31. I expect to add support imx35.
For formatting I used the commands like:
indent -st --line-length80 -nbad -bap -bbb -sob -cdb -sc -i4 -ip4 -lp -bli4
-Original Message-
From: openocd-development-boun...@lists.berlios.de [mailto:openocd-
development-boun...@lists.berlios.de] On Behalf Of Harald Welte
Sent: dinsdag 8 september 2009 11:20
To: Øyvind Harboe
Cc: openocd-development@lists.berlios.de
Subject: Re: [Openocd-development]
I can see there is run_algorithm implemented in arm11.c. Can you give me
some pointers on what needs to be added/changed? I can take a stab at
this.
Note that I see a really slow times for coping uboot to DDR memory
(load_image). Is this expected as well?
If I turn on burst writes, things go
On Thu, Sep 10, 2009 at 10:03 PM, michal smulski
michal.smul...@ooma.com wrote:
I can see there is run_algorithm implemented in arm11.c. Can you give me
some pointers on what needs to be added/changed? I can take a stab at
this.
I think David looked at this...
Can you share David?
Note
On Thursday 10 September 2009, Øyvind Harboe wrote:
I can see there is run_algorithm implemented in arm11.c. Can you give me
some pointers on what needs to be added/changed? I can take a stab at
this.
I think David looked at this...
Can you share David?
One issue I have with the ARM
Regarding the run_algorithm. This makes me think about
the refactoring I did for the arm simulation code
W.r.t. run_algorithm, I was thinking about how much work
it would be to write a *small* machine code translator
that would translate generic code in to machine specific
code... Sounds
Øyvind Harboe wrote:
Regarding the run_algorithm. This makes me think about
the refactoring I did for the arm simulation code
W.r.t. run_algorithm, I was thinking about how much work
it would be to write a *small* machine code translator
that would translate generic code in to machine
I've committed this so that testing can commence. The chances
of regressions seem very slight.
Thank you :)
The formatting/coding style is a bit quaint
I use the automatic formatting to match the requirements of style. I also do
not like the result. I use a style similar to the style of
Hello, all.
little cleaning
--
Regards,
Alexei Babich, circuit design engineer, Rezonans plc., Chelyabinsk, Russia
http://www.rez.ru
Jabber ID: imp...@jabber.ru
diff -Naur /mnt/data/clfs2/__hidden/source/openocd/trunk/src/flash/mx3_nand.c trunk/src/flash/mx3_nand.c
---
The SheevaPlug interface is now unusable since rev 2573:
Error: unable to open ftdi device: device not found
Runtime error, file command.c, line 469:
Backing out changes from that revision does indeed fix the issue.
So what was the point of that patch?
Nicolas
Dragonite is similar to the Feroceon core but has no MMU.
This can be found in chips such as the Marvell 8686 wireless chip.
Dragonite support. It is similar to the Feroceon core but has no MMU.
---
src/target/arm966e.c |3 --
src/target/arm966e.h |2 +
src/target/feroceon.c | 89
Make sure the target is actually halted at the end of the transfer and
confirm from the target's r0 content that the right amount of data was
actually received.
feroceon: tighten error checking in bulk_write
---
src/target/feroceon.c | 19 +++
1 files changed, 15 insertions(+),
feroceon.c: put feroceon target definition at the end so to avoid a
bunch of useless forward declarations.
feroceon.c: put feroceon target definition at the end so to avoid a bunch of
forward declarations.
---
src/target/feroceon.c | 165 +++-
1
I'd like to see new subjects broken out into new threads please.
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
Why doesn't target.c doesn't add dragonite_target to the target_types array?
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
Committed.
Thanks!
--
Øyvind Harboe
Embedded software and hardware consulting services
http://www.zylin.com
___
Openocd-development mailing list
Openocd-development@lists.berlios.de
https://lists.berlios.de/mailman/listinfo/openocd-development
17 matches
Mail list logo
