• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 98 subscribers
  • Views 245 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

spi boot problem

JVS Electronics Pvt Ltd-India
Intellectual 490 points

1). we tried to put Uimage in spi Flash and ROOTFS in SD/MMC card and we changed the bootargs

setenv bootargs ‘mem=32M console=ttyS2,115200n8 root=/dev/mmcblk0p2 rw rootwait ip=off'  its booting.
2). Aagain we want to boot from spi flash only, for this we ported ramdisk.gz and Uimage in SPI flash, we changed bootargs like
setenv bootargs ‘mem=32M console=ttyS2,115200n8 root=/dev/ram0 rw initrd=0xc2000000,12M ip=off’
After doing this its getting this kinde of error.

 

 No filesystem could mount root, tried: ext3 ext2 cramfs vfat msdos Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(1,0) Backtrace: [] (dump_backtrace+0x0/0x114) from [] (dump_stack+0x18/0x1c) r7:00008000 r6:c1c13000 r5:c0025a08 r4:c0446f38 [] (dump_stack+0x0/0x1c) from [] (panic+0x64/0x13c) [] (panic+0x0/0x13c) from [] (mount_block_root+0x1e0/0x220) r3:00000000 r2:80000000 r1:c1c23f60 r0:c03b5856 [] (mount_block_root+0x0/0x220) from [] (mount_root+0xc4/0xfc) r8:00000000 r7:00000000 r6:00000000 r5:c0025a08 r4:00100000 [] (mount_root+0x0/0xfc) from [] (prepare_namespace+0x170/0x1c8) r5:c0025a08 r4:c0446a20 [] (prepare_namespace+0x0/0x1c8) from [] (kernel_init+0xf0/0x12c) r5:00000000 r4:c04467e0 [] (kernel_init+0x0/0x12c) from [] (do_exit+0x0/0x6b4) r5:00000000 r4:00000000

Previously its working fine once we changed the ROOTFS from SD/MMC card then only we are getting this error

then what is the problem ? we are not able to boot from spi flash.


  • 0
    Guru 11260 points

    Hi Peter Mathew,

    Could you please Elaborate. on which board what were you trying to do exactly?


    Best Regards
    Prabhakar Lad

  • 0
    Guru 26430 points

    The "bootargs" look good assuming ramdisk.gz was loaded at 0xc2000000 and it uncompresses to less than 12M. You should take look at your "bootcmd" for spi commands to load up kernel and rootfs. Double check the data sizes in the commands. Sometimes kernel and rootfs overlap. Or the sizes specified in the command are smaller that the actual file.