Stefan Roese denx.de> writes:
>
> Hi Prakash,
>
> On Friday 15 January 2010 14:23:35 prakash bedge wrote:
> > In October 09 month, I had asked whether U-boot supports M29W128GH, a CFI
> > compilant chip and I got a yes reply. Please refer below URL for reference.
> >
> > http://www.mail-archiv
Hi All,
At last flash detection passed. :)
I have to set one DCR register for enable flash write.
But now I am facing the debug message "flash is busy" always on save
command.
Analyzing the root cause.
Thanks all of you for your help and support.
Regards,
Prakash Bedge
On Wed, Jan 20, 2010 at 6
Hi Prakash
Please quote properly and don't top post. Your emails are very hard to
understand.
prakash bedge wrote:
> Hi Albert and Stefan,
>
> I have used the proper commands.
> i.e.
> mw.b 0xfc00 0xf0
> mw.b 0xfc55 0x98
> md.b 0xfc10
> But still no positive results.
> Last time I
Hi Albert and Stefan,
I have used the proper commands.
i.e.
mw.b 0xfc00 0xf0
mw.b 0xfc55 0x98
md.b 0xfc10
But still no positive results.
Last time I forgot to tell here, that I have commneted the for(;;) loop in
"hang" function after flash_init result testing in lib_ppc/board.c and the
prakash bedge a écrit :
> Hi Baren and Stefan
>
> What I find is *VERY* helpful when trying to understand flash control issues
> is to *manually* do the QRY write sequence (see your flash data sheet) by
> using memory write/read commands from the u-boot command prompt
> I tested the same using "mw
On Tuesday 19 January 2010 17:22:33 prakash bedge wrote:
> What I find is *VERY* helpful when trying to understand flash control
> issues is to *manually* do the QRY write sequence (see your flash data
> sheet) by using memory write/read commands from the u-boot command prompt
> I tested the same
Hi Baren and Stefan
What I find is *VERY* helpful when trying to understand flash control issues
is to *manually* do the QRY write sequence (see your flash data sheet) by
using memory write/read commands from the u-boot command prompt
I tested the same using "mw" and "md" commands from uboot promp
In message <4b55ba83.4050...@ge.com> Jerry Van Baren wrote:
>
> What I find is *VERY* helpful when trying to understand flash control
> issues is to *manually* do the QRY write sequence (see your flash data
> sheet) by using memory write/read commands from the u-boot command
> prompt. This way
Stefan Roese wrote:
> On Tuesday 19 January 2010 07:24:10 prakash bedge wrote:
>> I have tried the code in the URL link you have provided. But still I am
>> facing the same problem. I am getting the error in "flash_detect_cfi" as
>> flash not found. It fails at initial stage at read CFI query comma
On Tuesday 19 January 2010 07:24:10 prakash bedge wrote:
> I have tried the code in the URL link you have provided. But still I am
> facing the same problem. I am getting the error in "flash_detect_cfi" as
> flash not found. It fails at initial stage at read CFI query command.
> The code you have p
Hi Stefan,
Thanks for information.
I have tried the code in the URL link you have provided. But still I am
facing the same problem. I am getting the error in "flash_detect_cfi" as
flash not found. It fails at initial stage at read CFI query command.
The code you have provided is for M29W128GL.(Nu
Hi Prakash,
On Friday 15 January 2010 14:23:35 prakash bedge wrote:
> In October 09 month, I had asked whether U-boot supports M29W128GH, a CFI
> compilant chip and I got a yes reply. Please refer below URL for reference.
>
> http://www.mail-archive.com/u-boot@lists.denx.de/msg24531.html.
Link n
Hi Stefan,
In October 09 month, I had asked whether U-boot supports M29W128GH, a CFI
compilant chip and I got a yes reply. Please refer below URL for reference.
http://www.mail-archive.com/u-boot@lists.denx.de/msg24531.html.
So I have used Uboot for my PPC440 based board.
When I flashed U-boot
13 matches
Mail list logo
