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

which arago root file system is available for omapl137

CalvinTai
Intellectual 850 points
Other Parts Discussed in Thread: OMAP-L137

Dear all:

I have boot the Linux kernel based on "Davinci-PSP-SDK-03.20.00.14" for my omapl137 custom board.

The Linux kernel is: "version 2.6.33-rc4" based on Sourcery G++ Lite 2009q1-203.

From the forum, it seems there is arago root file system can be used for linux. However I find there is no omapl137/da830 related image directory after 2009.11. And it seems there are some problems when using the image inside 2009.11 directory. Which image I can use for the Linux mentioned above?

 

  • 0
    Guru 26430 points

    Looks likes the TI guys are not talking. I'd like to know too. I have a feeling they won't release a new version of a OMAP-L137 specific file system.

    I have been using the "arago-base-image-arago" image here:
    2009.11/images/arago/arago-base-image-arago
    No apparent problems yet but I am only basic kernel commands. No LCD or demos. I haven't tried "demo" images as they are too large for my SD card.

    I've tried later "base" images like this:
    davinci-psp_03.01.01.39/images/arago/arago-base-image-arago
    I get a few more warnings but it still works.

    I'm tried DVSDK 03.20/linux-2.6.32-?? and DVSDK 03.21/linux-2.6.37 so far.

    As far as I can tell, the OMAP-L137 specific file system differs from the base only in cosmetic things like the command prompt. The kernel modules on the prebuilt filesystem will generally never match whatever version you are currently using. I usually delete the prebuilt modules and install my own built modules.

     

  • 0 in reply to Norman Wong
    Intellectual 850 points

    Dear Norman:

     

    Thanks for help.

    I tried the Arago but it reports some messages during booting Linux:

    root: mount: mounting rootfs on / failed: No such file or directory
    root: mount: mounting usbfs on /proc/bus/usb failed: No such file or directory

    The file system (busybox v1.13.2) works for basic commands, but I think it missing some device nodes. For example fbset will report 

    open /dev/fb0: No such file or directory

    I just wondering why the wiki and Linux Software Development Kit (SDK) mentioned the arago file system, though it can be used for demo purpose, It can't be used in a product without revise.

     

  • 0 in reply to CalvinTai
    Guru 26430 points

    I get the mount errors as well. I traced them a generic /etc/fstab file the referenced devices that might not exist. They certainly don't exist on my EVM.

    Not sure about the "/dev/fb0" file. I was under the impression that udev overrides the ones on the actual file system. Enabling frame buffer in the kernel build should cause udev to automatically create "/dev/fb0".