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

GLSDK 6.03.00.01 mksdboot fails

Joe Kreidler
Prodigy 160 points

I have downloaded GLSDK 6.03.00.01 and I am unable to boot the EVM5432 after building the SDcard. The kernel error message is:

Kernel panic - not syncing: No init found. Try passing init= option to kernel.

Inspecting the file system on my Ubuntu 12.04LTS development machine reveals that /sbin/init is a link to the actual init program.

lrwxrwxrwx 1 optimal optimal 19 Dec 20 09:52 init -> /sbin/init.sysvinit
-rwxr-xr-x 1 optimal optimal 29K Dec 20 09:07 init.sysvinit

However, after I create the SDcard with mksdboot.sh, the contents of init in /sbin is a broken link.

Something else that is very odd was observed. I am using a Samsung 64 MByte microSD card XC (so plenty of space per the 4GB requirements in the Software Dev Guide). The first time I tried to create the SDcard, the rootfs only contained these directories:

  • dev
  • lib
  • lost&found
  • media
  • proc
  • sbin

The next time I created the SDcard, the rootfs did not contain all of the directories and the list of directories is different when compared to the first time I created the SDcard.

  • bin
  • boot
  • home
  • lib
  • lost&found
  • usr

The 3rd running mksdboot, the rootfs appear to contain all of the necessary directories, i.e., 

  • bin
  • boot
  • dev
  • etc
  • home
  • lib
  • list&found
  • media
  • mnt
  • proc
  • sbin
  • srv
  • sys
  • tmp
  • usr
  • var

There are no errors from the mksdboot.sh command when the filesystem is untarred.

Anyone else see this phenomenon?

Anyone have any suggestions on how to properly get the SDcard rootfs written? 

Thank you in advance,

Joe

  • 0
    TI__Guru**** 161600 points

    Hello,

    Do you export all variable as described in GLSDK software developers guide? That is, if you have accepted the defaults when executing ./ti-glsdk_omap5-uevm_6_03_00_01_linux-installer.bin,  GLSDK="${HOME}/ti-glsdk_omap5-uevm_6_03_00_01"

    After that the setup.sh script should configure your environment as it is supposed to be.

    Then you should execute sudo ${GLSDK}/bin/mksdboot.sh --device /dev/sdY --sdk ${GLSDK}; this command should extract the arago-glsdk-multimedia-image-omap5-evm.tar.gz (located in ${GLSDK}/filesystem), which contains all necessary directories, on the rootfs partition of your sdcard. 

    Best Regards,

    Yordan

  • 0 in reply to Yordan Kovachev
    Prodigy 160 points

    Thank you for your reply, Yordan.

    The software environment was set up correctly. It looks like an issue with writing to the SDcard and not the software environment. I tried a new SDcard and this time, I was able to bring up the OS on the 5432 EVM.

    Joe