[U-Boot-Users] Stops booting after RAM info

[Andrejs Cainikovs <AndrejsC@GlobalAutomationSystems.com>]

Wolfgang Denk wrote:
> In message <4857C743.7060300@GlobalAutomationSystems.com> you wrote:
>   
>> As far as I know CFG_MAX_FLASH_BANKS should be set to 1 always.
>> Multiple flash banks in u-boot are not supported.
>>     
>
> Huuuu? Who claims so?
>
> What do you think how these boards are working then:
>
> include/configs/ADCIOP.h:#define CFG_MAX_FLASH_BANKS	2	/* max number of memory banks		*/
> include/configs/BAB7xx.h:#define CFG_MAX_FLASH_BANKS     2           /* max number of memory banks    */
> include/configs/CCM.h:#define CFG_MAX_FLASH_BANKS	2	/* max number of memory banks		*/
> ...
>
> ???
>   
Huh!? Well, there is some time since we have implemented the flash 
support for our board (Atmel AT91RM9200 based),
but at the moment we have done that, as far as I remember it was 
impossible to support both chips we have.
>   
>>  > Flash:  0 kB
>> This message is saying that u-boot was unable to detect the flash chip 
>> itself.
>> The easiest way to get you flash working:
>> 1. add flash id in include/flash.h (check your flash datasheet)
>>     
>
> NO!!!! Use the CFI driver instead!!!
>
>   
>> 2. based on board/../flash.c get it working (probably you will need only 
>> sector organization, also a datasheet material)
>>     
>
> NO!!!! Do not add custom drivers unless *really*, I mean REALLY
> necessary.
>   
Our boards flash driver is the same as in board/atmel/at91rm9200dk/flash.c
The only thing that was modified is the flash identification routine, as 
there was no support for AT49BV642D.
The flash organization for this chip is the same as in AT49BV6416 which 
exists in the sources, so we haven't changed a lot.

So, I think that's all are board dependent what and where are easier 
and/or faster to implement.
> Best regards,
>
> Wolfgang Denk
>
>   
Kind regards,
Andrejs Cainikovs.