AnsweredAssumed Answered

quadspi  booting imx6sx-sd

Question asked by chendrashekar pabbaraju on May 3, 2019
Latest reply on May 3, 2019 by igorpadykov

Board name:(imx6solox SABRE-SDB)

Problem:when i'm trying to boot from quadspi i'm facing issue with filesystem mounting

 

what i did:

created jffs2 file system in host PC using  the command

=>mkfs.jffs2 -p -r rootfs_default/ -s 0.25 -e 64 -n -o fs_qspi.jffs2 -l -f 

 

and in

u-boot environment :

 

"qspiargs=setenv bootargs console=${console},${baudrate} " \
        "root=/dev/mtdblock1 rw " \
        "rootfstype=jffs2 rootwait \0" \
    "qspiboot=echo booting from quadspi.....;" \
        "run qspiargs; " \
        "sf probe 1:0; " \
        "sf read ${loadaddr}  ${spi_image_addr} ${spi_image_len}; " \
        "sf read ${fdt_addr} ${spi_fdt_addr} ${spi_fdt_len}; " \
        "bootz ${loadaddr} - ${fdt_addr};\0" \

 

written u-boot,dtb,zimage in spi bus 1 and cs 0

file system in bus 1 and cs 2

 

 

and facing issue with rootfs mounting:

 

jffs2: Node at 0x005fdfec with length 0x0000002c would run over the end of the erase block
[  166.796508] jffs2: Perhaps the file system was created with the wrong erase size?
[  166.804182] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x005fdff0: 0x002c instead
[  166.815428] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x005fdff4: 0x565f instead
[  166.826566] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x005fe000: 0xb5ea instead
[  166.836377] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x005fe004: 0x16e0 instead
[  166.845871] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x005fe008: 0x0404 instead
[  166.855523] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x005fe00c: 0xbbbb instead
[  166.865092] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x005fe010: 0xbdb0 instead
[  166.874647] jffs2: jffs2_scan_eraseblock(): Magic bitmask 0x1985 not found at 0x005fe014: 0x316c instead
[  213.964236] VFS: Mounted root (jffs2 filesystem) on device 31:1.
[  213.975651] devtmpfs: mounted
[  214.022831] Freeing unused kernel memory: 2048K
[  214.040557] jffs2: warning: (1) jffs2_do_read_inode_internal: Truncating ino #7721 to 28812 bytes failed because it only had 0 bytes to start with!
[  214.071701] jffs2: warning: (55) jffs2_do_read_inode_internal: Truncating ino #60 to 109664 bytes failed because it only had 0 bytes to start with!
[  214.088609] jffs2: warning: (54) jffs2_do_read_inode_internal: Truncating ino #256 to 88 bytes failed because it only had 0 bytes to start with!
[  214.233343] jffs2: warning: (54) jffs2_do_read_inode_internal: Truncating ino #384 to 1839 bytes failed because it only had 0 bytes to start with!
[  214.515220] request_module: kmod_concurrent_max (0) close to 0 (max_modprobes: 50), for module binfmt-0000, throttling...
[  214.588715] jffs2: warning: (54) jffs2_do_read_inode_internal: Truncating ino #896 to 9124 bytes failed because it only had 0 bytes to start with!
[  214.667649] jffs2: warning: (54) jffs2_do_read_inode_internal: Truncating ino #1024 to 196330 bytes failed because it only had 0 bytes to start with!
[  214.857412] jffs2: warning: (54) jffs2_do_read_inode_internal: Truncating ino #1408 to 83 bytes failed because it only had 0 bytes to start with!
[  214.930433] jffs2: warning: (54) jffs2_do_read_inode_internal: Truncating ino #1536 to 1548 bytes failed because it only had 0 bytes to start with!

 

 

but when i use sf probe 1:0 or sf probe 1:2 in u-boot stage

i'm getting the output as

 

=> sf probe 1:2
SF: Detected n25q256 with page size 256 Bytes, erase size 64 KiB, total 32 MiB

 

is there anything wrong in creating jffs2 with

 

=>mkfs.jffs2 -p -r rootfs_default/ -s 0.25 -e 64 -n -o fs_qspi.jffs2 -l -f 

 

this command???

Outcomes