[U-Boot-Users] BDI2000 problems flashing virgin custom 8548 board

[Ben Warren <bwarren@qstreams.com>]

Hi Robert,

robert lazarski wrote:
> On 8/30/07, Ben Warren <bwarren@qstreams.com> wrote:
>   
>> Did you try
>> mdh 0xf8000000 ?
>>     
>
> Well after playing a bunch of option bingo I got here:
>
> 5ep8548a>mdh 0xf8000000
> 0_f8000000 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f8000010 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f8000020 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f8000030 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f8000040 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f8000050 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f8000060 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f8000070 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f8000080 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f8000090 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f80000a0 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f80000b0 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f80000c0 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f80000d0 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f80000e0 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
> 0_f80000f0 : f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7 f9f7  ................
>
> Is that actually a read from our flash - are those numbers believable?
> We put a scope on the chip select of the flash chip put couldn't
> trigger a signal, so we're in doubt.
>
>   
That's pretty ugly. If you don't see CS0 toggle, you're not reading the 
chip. If you can, probe the nOE pins directly on the flash chip 
(hopefully not BGA :-( ). Maybe you have other chip selects that overlap 
in address space? Just to be safe set the valid bit to 0 on all other 
chip selects. But before you do that...

One other thing I just thought of - you need to make sure the Local Bus 
Access Windows are set properly. My chip has separate ones for DDR and 
for Local Bus, and yours may as well. The config file you sent has the 
LAWBAR for local bus set to 0x000c0000, when it should be 0xf8000000, I 
think. If this is set wrong, I don't think you'll be able to access the 
memory range. Info is in the 'System Configuration' section of your 
reference manual.

> I still can't erase or write the flash even though I tried your unlock
> commands. I am trying to figure out if those addresses work for the
> S29GL01GP - I don't think you mentioned your exact chip - could you
> please let me know your spansion model number?
>
>   
We're using S29GL064M (just a baby)
> Still trying to dig into the 12.2 spec section ;-) .
>
> Thanks!
> Robert
>   
Fun stuff, eh?

Ben