On Mon, Mar 24, 2014 at 9:31 AM, S Durga Prasad Paladugu durgaprasad.psdp@gmail.com wrote:
Hi,
I have a below query on u-boot bootup.
When UBOOT does not detect NOR flash during bootup it throws up an error message that indicates that uboot did not detect NOR flash and stops there. But when uboot does not detect QSPI flash it just gives a warning message that uboot sf_probe_failed, and comes to the uboot prompt.
Why is this behavior different for NOR flash and QSPI flash.
As per my understanding wrt code is concern.
Yes - this can be an implementation logic where the SPI/QSPI flash code is more handy with the users while using spi/sf commands. Due to this we couldn't need/have any architecture initialization calls unlike with NAND/NOR - arch/arm/lib/board.c
The initialization code that resides in arch' board file generally have safe monitored where something can't get at the time of board init phase, they might give an err/warn to exit. this is not the case in spi/qspi where most of the initialization is done through user interaction unlike in arch' board files.
Did you see any special need/requirement to behave SPI/QSPI similar to NOR?
thanks!