Actions
Forum Thread Details
  • State Not Answered
  • Replies 5 replies
  • Subscribers 300 subscribers
  • Views 522 views
  • Users 0 members are here
Related

About U-Boot for picozed

Former Member

Hi  all,

       I have a DVSK board(Picozed, QSPI+eMMC ). And download u-boot-xlnx-xilinux-v2015.4, using different config to build uboot, It's get different result.

       1）make zynq_picozed_defconfig to build uboot, and create boot image, download to QSPI flash. The uboot can recognize the eMMC flash and cannot using sf command.  The detail info:

       U-Boot 2015.07 (Jun 20 2016 - 13:55:28 +0800)

 
Model: Zynq PicoZed Board
DRAM:  ECC disabled 1 GiB
MMC:   zynq_sdhci: 0
Using default environment
 
In:    serial
Out:   serial
Err:   serial
Model: Zynq PicoZed Board
Net:   Gem.e000b000
Hit any key to stop autoboot:  0
Copying Linux from QSPI flash to RAM...
Unknown command 'sf' - try 'help'
zynq-uboot> mmcinfo
Device: zynq_sdhci
Manufacturer ID: fe
OEM: 14e
Name: MMC04
Tran Speed: 52000000
Rd Block Len: 512
MMC version 4.4.1
High Capacity: Yes
Capacity: 3.5 GiB
Bus Width: 4-bit
Erase Group Size: 512 KiB
HC WP Group Size: 4 MiB
User Capacity: 3.5 GiB
Boot Capacity: 16 MiB ENH
RPMB Capacity: 128 KiB ENH
zynq-uboot>              

       2）make zynq_zed_defconfig to build uboot, The uboot can recognize the SPI flash and cannot using mmcinfo command.  The detail info:

U-Boot 2015.07 (Jun 20 2016 - 13:53:03 +0800)
 
Model: Zynq Zed Development Board
DRAM:  ECC disabled 512 MiB
MMC:   zynq_sdhci: 0
SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, total 16 MiB
*** Warning - bad CRC, using default environment
 
In:    serial
Out:   serial
Err:   serial
Model: Zynq Zed Development Board
Net:   Gem.e000b000
Hit any key to stop autoboot:  0
Copying Linux from QSPI flash to RAM...
SF: Detected S25FL128S_64K with page size 256 Bytes, erase size 64 KiB, total 16 MiB
device 0 offset 0x100000, size 0x500000
SF: 5242880 bytes @ 0x100000 Read: OK
device 0 offset 0x600000, size 0x20000
SF: 131072 bytes @ 0x600000 Read: OK
Copying ramdisk...
device 0 offset 0x620000, size 0x5e0000
SF: 6160384 bytes @ 0x620000 Read: OK
Wrong Image Format for bootm command
ERROR: can't get kernel image!
zynq-uboot> mmcinfo
sdhci_set_clock: Internal clock never stabilised.
 
And I want to know  how to config to recognize the QSPI and eMMC in uboot?  
 
 Thanks a lot.
Parents
  • 0

    Hi gomo,

    If you look under the hood for PetaLinux, when SPI+eMMC boot mode is set within the project configuration the following config options are set:

    #define CONFIG_ZYNQ_SDHCI1t0xE0101000
    #define CONFIG_ZYNQ_QSPI

    Also, the following configuration options become removed:

    #define CONFIG_ZYNQ_SDHCI0t0xE0100000

    You will also need to setup appropriate U-Boot ENV macros to boot from QSPI+eMMC but the details of those can vary based upon how your Linux is being configured.  PetaLinux is a good example of how to do some of these different boot options because you can change things within the config menu and then go back and see which pieces of source code were modified to accommodate the changes.

    Regards,

    -Kevin

Reply
  • 0

    Hi gomo,

    If you look under the hood for PetaLinux, when SPI+eMMC boot mode is set within the project configuration the following config options are set:

    #define CONFIG_ZYNQ_SDHCI1t0xE0101000
    #define CONFIG_ZYNQ_QSPI

    Also, the following configuration options become removed:

    #define CONFIG_ZYNQ_SDHCI0t0xE0100000

    You will also need to setup appropriate U-Boot ENV macros to boot from QSPI+eMMC but the details of those can vary based upon how your Linux is being configured.  PetaLinux is a good example of how to do some of these different boot options because you can change things within the config menu and then go back and see which pieces of source code were modified to accommodate the changes.

    Regards,

    -Kevin

Children
No Data