[U-Boot] Why spi flash probe runs twice on Xilinx Zynq board ?
Heshsham Abdul Basit
hf.basit at gmail.com
Mon Jun 30 13:02:35 CEST 2014
On 30 June 2014 16:30, Jagan Teki <jagannadh.teki at gmail.com> wrote:
> On Mon, Jun 30, 2014 at 4:18 PM, Heshsham Abdul Basit
> <hf.basit at gmail.com> wrote:
> > Thanks for your comments Thomas and Jagan!
> >
> >
> > On 30 June 2014 15:58, Jagan Teki <jagannadh.teki at gmail.com> wrote:
> >>
> >> I guess - your using Xilinx github u-boot-xlnx
> >>
> >
> > Yes
> >
> >>
> >> The reason for two prints is like, for
> >> 1) Initial probe print, by default done in env calls
> >> 2) Added in sf probe again on auto-boot commands [1]
> >>
> >> [1]
> >>
> https://github.com/Xilinx/u-boot-xlnx/blob/master/include/configs/zynq-common.h
> >>
> >
> > Ok. I will study it.
> >
> >
> > BTW is it technically possible to completely get rid of the second
> probing
> > which I boot from flash?
>
> Do you have any issue with the second print, it's probing once aging
> before reading?
>
>
The only problem is , it is taking significant time for my application. I
though if I remove this second probing I could save some time!
> >
> > Thanks
> >
> >>
> >> On Sat, Jun 28, 2014 at 10:51 PM, Heshsham Abdul Basit
> >> <hf.basit at gmail.com> wrote:
> >> > Hi,
> >> >
> >> > I am re-sending this email because earlier I forgot to put the subject
> >> > line
> >> > properly. I am struggling to figure out few things in u-boot , but I
> >> > failed
> >> > to get a good resource or help.
> >> >
> >> > This is a section of the log from u-boot running on Avnet Microzed
> >> > board:
> >> >
> >> >
> >> > [Thu Jun 26 17:40:53.656 2014]
> >> >
> >> > [Thu Jun 26 17:40:53.656 2014]
> >> >
> >> > [Thu Jun 26 17:40:53.656 2014] U-Boot 2013.07 (Jun 26 2014 - 17:34:41)
> >> >
> >> > [Thu Jun 26 17:40:53.656 2014]
> >> >
> >> > [Thu Jun 26 17:40:53.656 2014] 1 GiB
> >> >
> >> > [Thu Jun 26 17:40:53.671 2014] SF: Detected
> >> > S25FL129P_64K/S25FL128S_64K with page size 64 KiB, total 16 MiB
> >> >
> >> > [Thu Jun 26 17:40:53.703 2014] *** Warning - bad CRC, using default
> >> > environment
> >> >
> >> > [Thu Jun 26 17:40:53.703 2014]
> >> >
> >> > [Thu Jun 26 17:40:53.703 2014] In: serial
> >> >
> >> > [Thu Jun 26 17:40:53.703 2014] Out: serial
> >> >
> >> > [Thu Jun 26 17:40:53.703 2014] Err: serial
> >> >
> >> > [Thu Jun 26 17:40:53.703 2014] U-BOOT for suheb_24
> >> >
> >> > [Thu Jun 26 17:40:53.703 2014]
> >> >
> >> > [Thu Jun 26 17:40:53.703 2014]
> >> >
> >> > [Thu Jun 26 17:40:53.703 2014] SF: Detected
> >> > S25FL129P_64K/S25FL128S_64K with page size 64 KiB, total 16 MiB
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] SF: 5242880 bytes @ 0x520000 Read: OK
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] Description: PetaLinux Kernel
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] 0x010000f0
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] 4620145 Bytes = 4.4 MiB
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] Description: Flattened Device
> Tree
> >> > blob
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] 0x01468114
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] 9766 Bytes = 9.5 KiB
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] Hash algo: crc32
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] Hash value: 9a94aca8
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] Hash algo: sha1
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] Hash value:
> >> > 97b81e3014decb706ff19e61e1227dace97d4232
> >> >
> >> > [Thu Jun 26 17:40:54.453 2014] crc32+ sha1+ Uncompressing Kernel
> Image
> >> > ...
> >> > OK
> >> >
> >> > .
> >> > .I noticed that the following lines are coming twice:
> >> >
> >> > SF: Detected S25FL129P_64K/S25FL128S_64K with page size 64 KiB, total
> 16
> >> > MiB
> >> >
> >> > This corresponds to the function spi_flash_probe from
> >> > drivers/mtd/spi/spi_flash.c
> >> >
> >> >
> >> > I need to know:
> >> >
> >> > 1- Why it is probed twice?
> >> > 2- The name and location of the file from where it is called (twice).
> >> > 3- The second time it is being probed is considerably slow, why it is
> >> > so?
> >> >
> >> >
> >> > I have searched many forums and have looked in the code but still I am
> >> > not
> >> > able to figure out these things.
> >> >
> >> >
> >> >
> >> > Thanks and regards,
> >> >
> >> > Abdul Basit
> >> >
> >> > _______________________________________________
> >> > U-Boot mailing list
> >> > U-Boot at lists.denx.de
> >> > http://lists.denx.de/mailman/listinfo/u-boot
> >> >
> >>
> >> thanks!
> >> --
> >> Jagan.
> >
> >
>
>
>
> --
> Jagan.
>
More information about the U-Boot
mailing list