Am 15.02.2011 08:37, schrieb Nick Pelling:
Hi Daniel,
At 16:43 11/02/2011 +0100, Daniel Bäder wrote:
S3CPC100 from Samsung is also detected as imx51 with this patch. Without this
patch it works.
May I ask which S5PC100 platform are you working with?
I'm am working with a board design
Am 30.12.2010 13:51, schrieb Antonio Borneo:
On Thu, Dec 30, 2010 at 11:54 AM, Marek Vasut wrote:
} broken_cpus[] = {
- { 0x8000, 0x04770002, 0x6000, "imx51" },
+ { 0x8000, 0x04770002, 0x1ba00477, 0x6000, "imx51" },
Hi Marek,
your patch goes in the right directio
David Brownell schrieb:
On Thursday 25 March 2010, Daniel Bäder wrote:
When using uint32_t in LOG_xxx functions the PRIx32 or PRId32 macros are needed
in the format string instead of x and d to compile with cygwin.
The attached patch corrects this.
What version of Cygwin complains?
I did a
When using uint32_t in LOG_xxx functions the PRIx32 or PRId32 macros are needed
in the format string instead of x and d to compile with cygwin.
The attached patch corrects this.
>From 6ce7282be99d073f4ef9d71feda770b67eb12080 Mon Sep 17 00:00:00 2001
From: Daniel Bäder
Date: Thu, 25 Mar 2010
David Brownell schrieb:
> On Tuesday 13 October 2009, Daniel Bäder wrote:
>> there should the possibility to do a memwrite without increment
>> because you need it for nand flash (at least on Samsung processors)
>> I don't know if this option is the right way to do this.
Øyvind Harboe schrieb:
> Can anyone come up with a reason why we should have the
> "arm11 no_increment" option?
there should the possibility to do a memwrite without increment because you
need it for nand flash (at least on Samsung processors)
I don't know if this option is the right way to do th
Øyvind Harboe schrieb:
>> So, every data word is written but at every other address.
>
> Not so quick! :-)
>
> Is 0 being written to every other address, or is every other address
> being written to?
>
> See this comment from the arm11 code:
>
> * The repeated TAP_IDLE's do not cause a repeat
Øyvind Harboe schrieb:
> Does anyone have an s3c6410 PCB out there they
> could donate to us?
I am currently working on a S3C6410 based board but I have only some samples
here.
I hope that we can go in production in october and that I can convince my boss
to donate one.
Øyvind Harboe schrieb:
> What interface are you using?
>
> Perhaps this is a bug in the interface pathmove driver code rather
> than arm11 code?
I am using a FT2232 based interface (DLP-2232M + glue logic) with libftd2xx
under Cygwin under WindowsXP.
When I checkout a older version (i.e. 1504) a
I found a solution, in arm11_dbgtap.c
arm11_MOVE_DRPAUSE_IDLE_DRPAUSE_with_delay has TAP_IDLE 3 times repated.
If you change it to one it works, with two or more it fails.
Daniel Bäder schrieb:
in the recent svn builds under cygwin/mingw the arm11 memwrite with burst
enabled is not working
in the recent svn builds under cygwin/mingw the arm11 memwrite with burst
enabled is not working anymore.
with burst disabled it is working correct but is painfully slow (81s for 32k
w/o burst, 0,5s with burst).
SVN 2485M:
> mww 0 0 8
> mdw 0 8
0x: 0
11 matches
Mail list logo