cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Highlighted
Observer
Observer
4,607 Views
Registered: ‎06-16-2016

64MB QSPI only 32 MB available

Hi,

   I have succeed in booting linux-3.15 from 32MB-qspi flash on custom board.Now I'm trying to upgrade it to 64MB(dual quad spi),I got a qspi partition like this:

   major  minor  #blocks  name

     31     0     5120    mtdblock0
     31     1     128     mtdblock1
     31     2     4096    mtdblock2
     31     3     4096    mtdblock3
     31     4     64      mtdblock4

     31     5     4096    mtdblock5
     31     6     47104   mtdblock6


   U-boot startup QSPI identify only to 32 MB,but Linux read 64 MB:

   U-boot:

   U-Boot 2013.10 (Aug 03 2016 - 14:33:46)

   Memory: ECC disabled
   DRAM: 1 GiB
   myir_board_init
   MMC: zynq_sdhci: 0
   ---lower_mio:6 upper_mio_cs1:0 upper_mio:0
   SF: Detected W25Q256 with page size 256 Bytes, erase size 32 KiB, total 32 MiB
   *** Warning - bad CRC, using default environment

   Linux:

   brd: module loaded
   loop: module loaded
   --->mtdsize > 16M!
   --->1
   m25p80 spi0.0: w25q256 (65536 Kbytes)
   7 ofpart partitions found on MTD device spi0.0
   Creating 7 MTD partitions on "spi0.0":
   0x000000000000-0x000000500000 : "qspi-boot"
   0x000000500000-0x000000520000 : "qspi-bootenv"
   0x000000520000-0x000000920000 : "qspi-bitstream"
   0x000000920000-0x000000d20000 : "qspi-kernel"
   0x000000d20000-0x000000d30000 : "qspi-devicetree"
   0x000000d30000-0x000001130000 : "qspi-rootfs"
   0x000001130000-0x000003f30000 : "data"
   CAN device driver interface
   libphy: MACB_mii_bus: probed

 

   When I write files to QSPI always prompt this error:

   Z-turn# flashcp -v BOOT.bin /dev/mtd0
   Erasing block: 60/60 (100%)
   Writing kb: 3792/3799 (99%)
   Verifying kb: 0/3799 (0%) flashcp: verification mismatch at 0x0

 

   Does anyone know why?

   Thanks in advance for any ideas.

0 Kudos
1 Reply
Highlighted
Participant
Participant
4,245 Views
Registered: ‎05-12-2014

Hi,

If you are using the Zynq SoC, then I believe only 32MB can be addressed; unless you are utilising additional address bit such as the EXTADD bit of the S25FL512S device.

 

 

0 Kudos