• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 357 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.

kernel init nor

Dennis McLeod
Intellectual 925 points

I have burned a filesystem to the nor flash in partition 3 (0x08460000 - 0x0b65ffff). Now I'm trying to figure out how to make the kernel use that for its rootfs. From examining the code,  ti8148_evm_init calls ti814x_mux_init and then calls board_nor_init. The mux settings are perfect, the GPMC settings are perfect. The question is, when board_nor_init calls platform_device_register.. how does that end up creating /dev/mtdblock3 ?   I don't get any errors until the kernel tries to open mtdblock3.. which eventually ends in a kernel panic. I get the following output: 

VFS: Cannot open root device "mtdblock3" or unknown-block(2,0)

Please append a correct "root=" boot option; here are the available partitions:

Kernel panic - not syncing: VFS: unable to mount root fs on unknown-block(2,0)

<backtrace>

So it's interesting that it says "here are the available partitions" and then lists nothing. What could be going on here? 

  • 0
    Guru 31670 points

    Dennis,

    Can you share the complete boot logs?

  • 0 in reply to Renjith Thomas
    Intellectual 925 points

    I think I have the MTD partitions bit working. Instead of letting board_nor_init call register_platform_device I set the config options for PHYSMAP instead. Then all the other stuff like gen_probe started working (for the most part, our chip uses CFI version 1.6 which was unsupported, but it works if i override the response and make it 1.5) as expected. Which brings me back to an earlier question (from an earlier post): 

    The root filesystem provided in EZSDK/filesystems/arago-base-tisdk-image-dm814x-evm.tar.gz has problems when I try to extract it. Maybe I'm doing something wrong though. Given the command 'tar xvfz arago....tar.gz'  I get output that contains lines like: 

    tar: ./dev/hda14: Cannot mknod: Operation not permitted

    tar: ./dev/zero: Cannot mknod: Operation not permitted

    tar: ./dev/console: Cannot mknod: Operation not permitted

    tar: ./dev/mtd5: Cannot mknod: Operation not permitted

    tar: Exiting with failure status due to previous errors

    What's going on with that?  I am still able to create a JFFS2 image from the filesystem, but it sure looks like important stuff may not be getting included. 

    Lastly, when I boot the kernel now it complains that it can't find init. It says to append an 'init=' entry to commandline. I double checked the extracted arago FS tree and did see init in the usual /sbin/init .. So it's not clear why the kernel didn't find it. Maybe due to previous errors with extraction? 

  • 0 in reply to Dennis McLeod
    Guru 31670 points

    Dennis,

    Untar using sudo or as root.