• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 403 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.

omap3530 boot problem

jinjun
Prodigy 20 points

Other Parts Discussed in Thread: OMAP3530

Hi, I am trying to boot OMAP 3530 EVM board with linux kernel image on a local network and encounter error during kernal boot mount fs.

I was following the "OMAP3530 Software Developer Guide" in DVSDK 4 section 2.1 to setup host and target environment. When bootargs is configured to 'console=${console} rw mem=99M@0x80000000 mpurate=720 omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M root=/dev/nfs nfsroot=192.168.1.101:/home/jjkang/targetfs,nolock', no more output is seen on the console after "Starting Kernel..." (please refer to booterror1.txt 7041.booterror1.txt for printenv and error)

I then changed bootargs to 'mem=128M console=ttyS0,115200n8 noinitrd rw root=/dev/nfs nfsroot=192.168.1.101:/home/jjkang/targetfs,nolock'. The kernal boots with error "Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)". (please refere to booterror2.txt 3515.booterror2.txt for printenv and error)

Could anyone tell me what I did wrong?

Thanks in advance!

  • 0
    TI__Expert 6735 points

    Jinjun:

    Could you try a setup like this?

    setenv ipaddr 192.168.1.102
    setenv serverip 192.168.1.101
    setenv rootpath  /home/jjkang/targetfs
    setenv tftpuimage 'tftp ${bootfile}'
    setenv nfsargs 'console=${console} rw mem=99M@0x80000000 mpurate=720 omap_vout.vid1_static_vrfb_alloc=y omapfb.vram=0:3M root=/dev/nfs nfsroot=${serverip}:${rootpath},nolock'
    setenv tftp_nfs_boot 'setenv bootargs ${nfsargs}; run tftpuimage; bootm ${loadaddr}'
    setenv bootcmd run tftp_nfs_boot

    regards,

    Michael T

    PS: Please mark this post as answered via the Verify Answer button below if you think it answers your question.  Thanks!

  • 0 in reply to Michael T
    Prodigy 20 points

    Michael,

    Thank you very much for the prompt response! I tried your suggestion, and the kernel boot stops at "...done, booting the kernel."  4846.tt2.log I altered the line setenv ipaddr 192.168.1.102 to setenv ipaddr 192.168.1.103 as that is the ip I get from dhcp.


    Best regards,

    JinJun