Forums » Software Development »
SATA on MityDSP-L138F dev board
Added by Mike Costa over 12 years ago
Hi,
I am looking to get some relatively quick proof of concept & testing of the SATA functionality with the MityDSP-L138F module and dev board.
Could you possibly point me to some resources on how to get a SATA drive running with embedded Linux? I have the Linux system running on the board with the default uImage and root file system, but I am unclear if there is SATA capability in the default build. If not, is there source code to build into a driver and to build a new kernel etc?
Thanks,
Mike
Replies (3)
RE: SATA on MityDSP-L138F dev board - Added by Michael Williamson over 12 years ago
Well Mike,
I think all you need to do is get a powered SATA drive and plug it in. If you are using our provided filesystem (well, really just udev) and the default kernel you should have SATA support. The config option should be:
Device Drivers-> Serial ATA and Parallel ATA drivers -> AHCI SATA SUPPORT
If you have a drive connected and boot the kernel, you should see some messages on the console about a SATA drive (/dev/sda device should be vreated). You'll need to make a filesystem and mount it (or if it's pre-formatted you'll need to ensure that the filesystem drivers are included in the kernel image for that filesystem type, likely FAT32).
Any good "howto" linux reference wiki or book should give you the commands/info for formatting the disk and mounting the drive. E.G., something along the lines of
mke2fs -j /dev/sda1
mkdir /mnt/sata
mount /dev/sda1 /mnt/stat
We have tested SATA access on the industrial I/O board as well as during our SOM factory testing.
We have also tested having the kernel use a SATA mounted filesystem as the root partition (works fine).
Hope this helps.
-Mike
RE: SATA on MityDSP-L138F dev board - Added by Mike Costa over 12 years ago
Hi Mike,
Wow that was easy ;-) It worked right out of the box.
I am curious, who is in charge of the Linux distro that CriticalLink provides?
RE: SATA on MityDSP-L138F dev board - Added by Michael Williamson over 12 years ago
Glad to hear it!
As for "who is in charge", the filesystem images (our "base" vs. our "full") are basically openembedded images (the "base" console image and an image that includes qt4-embedded libraries with a handful of utilities). You can add or tailor them using "opkg" to your liking or build your own if you are comfortable with the openembedded build framework. This is generally what we do here on a project to project basis (using NFS until the filesystem is at a point to burn into NAND or MMC, if necessary).
At the moment, I am responsible for kicking the release and adding packages (with contributions coming from internal engineering here at Critical Link) to the filesystems. However, those filesystems are really intended to be examples. You can use the TI DVSDK filesystem images (recommended if you are considering using gstreamer for video playback, etc.) or cook up your own based on your needs. There is no way for Critical Link to cover the needs for all end users, and unless someone wants to put us on contract for supporting a specific filesystem image it's unlikely that we'll do a whole lot of tailoring of the images released in the MDK board support packages.
As far as packages go, we have considered providing a package server (as an alternate to the openemebedded/angstrom package servers), but it's not clear if that would be of any value to our customers. Would appreciate any feedback on that....
-Mike
