I am in the early stages of developing a signal processing algorithm
using the BeagleBoard. Angstrom seems to be the predominant
distribution of Linux on the BeagleBoard since the uImage is developed
for the ARM processors. I am still very new to the Linux, Angstrom,
BeagleBoard, and OMAP community/technology so I know I have a lot to
learn ahead of me. The question I have right now concerns just getting
a fully functional version of Angstrom on the board for me to continue
development, the things I need to have access to are the GPIO pins on
the expansion header of the BeagleBoard. I would like to either
serially receive data or implement a software A/D.
I have two sets of boot up software that I have attempted, each with
it's own hang up.
The first attempt's terminal output can be seen at this link, and the
process I followed for the SD card is linked below that. I believe the
issue here is that the boot sequence expects to see the SD partitioned
and locate the root file system on the second partition. For this
attempt it would be nice to know if I can format the MMCSD card as is
described using a windows machine instead of a linux machine.
My other attempt follows the BeagleBoard validation wiki. This one
throws some I/O buffer errors at the end, and I'm not sure what the
root of this one is. I can login to Angstrom on this attempt with the
terminal emulator, however the USB keyboard connected does not
function. Additionally, most of the Linux commands I know of don't
seem to work, but again, I am new to Linux so I may not be using these
commands correctly.
I would appreciate any solutions to either correct one of these
implementations or an alternate implementation of Angstrom or another
Linux distribution that would be well suited to the embedded
environment.
What are your boot arguments, especially the "root=" argument? Here is what is in my boot.scr file. Remember that you must use mkimage to create the boot.scr file.
I am in the early stages of developing a signal processing algorithm
using the BeagleBoard. Angstrom seems to be the predominant
distribution of Linux on the BeagleBoard since the uImage is developed
for the ARM processors. I am still very new to the Linux, Angstrom,
BeagleBoard, and OMAP community/technology so I know I have a lot to
learn ahead of me. The question I have right now concerns just getting
a fully functional version of Angstrom on the board for me to continue
development, the things I need to have access to are the GPIO pins on
the expansion header of the BeagleBoard. I would like to either
serially receive data or implement a software A/D.
I have two sets of boot up software that I have attempted, each with
it's own hang up.
The first attempt's terminal output can be seen at this link, and the
process I followed for the SD card is linked below that. I believe the
issue here is that the boot sequence expects to see the SD partitioned
and locate the root file system on the second partition. For this
attempt it would be nice to know if I can format the MMCSD card as is
described using a windows machine instead of a linux machine.
My other attempt follows the BeagleBoard validation wiki. This one
throws some I/O buffer errors at the end, and I'm not sure what the
root of this one is. I can login to Angstrom on this attempt with the
terminal emulator, however the USB keyboard connected does not
function. Additionally, most of the Linux commands I know of don't
seem to work, but again, I am new to Linux so I may not be using these
commands correctly.
Everything seems correct, may be your ramdisk is corrupted somehow? Bad
download?
I would appreciate any solutions to either correct one of these
implementations or an alternate implementation of Angstrom or another
Linux distribution that would be well suited to the embedded
environment.
I will repeat myself again but have you checked this post [1]? It is a good
place for getting started.
Thanks for your help guys. I finally went back and built my "own"
image files using Narcissus and formatted everything correctly using a
Gentoo live CD, since I don't YET have a machine running Linux full
time. Everything works great now.