Ubuntu on BeagleBoard XM
Rob
I am trying to get Ubuntu running on XM, but can't get it to work. I
ran the following commands (on Ubuntu running on x86_32) as per the
instructions for the pre-build demo image at (http://elinux.org/
BeagleBoardUbuntu):
wget http://rcn-ee.net/deb/rootfs/lucid/ubuntu-10.04.1-r1-minimal-armel.tar.7z
7za x ubuntu-10.04.1-r1-minimal-armel.tar.7z
tar xf ubuntu-10.04.1-r1-minimal-armel.tar
cd ubuntu-10.04.1-r1-minimal-armel
./setup_sdcard.sh --mmc /dev/sdi --uboot beagle --swap_file 50
The microSD card has 16 GB capacity, and looks like it is creating all
the required files on it. But when I try to boot the BeagleBoard with
it, the USR0 LED near the microSD keeps flashing and nothing comes up
on the LCD screen (connected via HDMI). Am I missing anything here?
The Angstrom dist. that came with the board is working fine.
Thanks,
Rob.
Robert Nelson
Hi Rob,
On first boot, it'll take a good 2-3 minutes before the console loads
"oem-config" to help you create the first user.. Which will explain
the USR0 LED flashing..
If that isn't happening... Is there anything on your serial log? Can
you pastebin it anyways so i can take a look at it...
Can i have you rerun the "setup_sdcard.sh" script with:
"--use-default-user" , this will bypass the oem-config, does it load
to a login prompt?
user: ubuntu pass: temppwd
Regards,
--
Robert Nelson
http://www.rcn-ee.com/
Rob
I tried with --use-default-user option, still no luck. Don't see
anything on the screen even after an hour. I don't have a serial cable
around to check the log... is there anything else I can try?
Thanks,
Rob
On Oct 14, 12:00 pm, Robert Nelson <robertcnel...@gmail.com> wrote:
> > Hi all,
>
> > I am trying to get Ubuntu running on XM, but can't get it to work. I
> > ran the following commands (on Ubuntu running on x86_32) as per the
> > instructions for the pre-build demo image at (http://elinux.org/
> > BeagleBoardUbuntu):
>
Robert Nelson
> Hi Robert,
>
> I tried with --use-default-user option, still no luck. Don't see
> anything on the screen even after an hour. I don't have a serial cable
> around to check the log... is there anything else I can try?
An hour is way to much... (anything more then 5mins is usually a
failure of some kind)
With out a serial cable, it's pretty hard to see what's going on in your board..
Do you have any smaller sd cards? 4/8G? I've had some issues with
large/oversize cards..
Trey Weaver
Here is the output, after this output it just sits there (waited 15
minutes):
=========================================
Texas Instruments X-Loader 1.4.4ss (Sep 22 2010 - 16:12:19)
Beagle xM Rev A
Reading boot sector
Loading u-boot.bin from mmc
U-Boot 2010.03-dirty (Sep 01 2010 - 16:53:27)
OMAP3630/3730-GP ES1.0, CPU-OPP2, L3-165MHz,
OMAP3 Beagle board + LPDDR/NAND
I2C: ready
DRAM: 512 MB
NAND: 0 MiB
*** Warning - bad CRC or NAND, using default environment
In: serial
Out: serial
Err: serial
Probing for expansion boards, if none are connected you'll see a
harmless I2C error.
No EEPROM on expansion board
Beagle xM Rev A
Die ID #7baa0000061000000156166b0a018002
Hit any key to stop autoboot: 0
mmc1 is available
The user button is currently NOT pressed.
reading boot.scr
532 bytes read
Running bootscript from mmc ...
## Executing script at 80200000
Kernel is not ready for 1Ghz limiting to 800Mhz
mmc1 is available
reading uImage
4431040 bytes read
reading uInitrd
3943106 bytes read
## Booting kernel from Legacy Image at 80300000 ...
Image Name: Linux
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4430976 Bytes = 4.2 MB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 81600000 ...
Image Name: initramfs
Image Type: ARM Linux RAMDisk Image (uncompressed)
Data Size: 3943042 Bytes = 3.8 MB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
Robert Nelson
On Fri, Oct 15, 2010 at 9:56 AM, Trey Weaver <treyw...@gmail.com> wrote:
> I am having the same issue and I do have a serial port connected.
>
> Here is the output, after this output it just sits there (waited 15
> minutes):
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
That's definitely not good...
Which of the various install methods was this install? Which command
line options did you give it? and can i see your dump of your
"boot.scr" "cat boot.scr | pastebinit" would work fine..
Ricardo Salveti
This would be normal if he used the official pre-installed image for
Maverick (as console is disabled by default).
But it seems he's using a different x-loader/u-boot combination than
the official release.
Cheers,
--
Ricardo Salveti de Araujo
Trey Weaver
Since it would not load the kernel, I thought I would try a different
kernel. So I took the kernel from the original angstrom build that
came with the beagleboard-xm and put it on the ubuntu sd (uImage on
boot). The kernel then booted and got me to the prompt.
So is something wrong with the uImage that is supplied?
Trey
from the http://elinux.org/BeagleBoardUbuntu site.
I am using the following commands:
wget http://rcn-ee.net/deb/rootfs/maverick/ubuntu-10.10-minimal-armel.tar.7z
md5sum ubuntu-10.10-minimal-armel.tar.7z
7za x ubuntu-10.10-minimal-armel.tar.7z
tar xf ubuntu-10.10-minimal-armel.tar
cd ubuntu-10.10-minimal-armel
sudo ./setup_sdcard.sh --mmc /dev/sdb --uboot beagle
Here is the pastebin of the boot.scr.
http://pastebin.com/XUYgNVRN
Robert Nelson
Hey Trey,
There shouldn't be...
After your first message, i double checked it and posted this..
http://pastebin.com/fXwm4cJx
Which xM revision do you have?
Robert Nelson
> I am using the http://rcn-ee.net/deb/rootfs/maverick/ubuntu-10.10-minimal-armel.tar.7z
> from the http://elinux.org/BeagleBoardUbuntu site.
>
> I am using the following commands:
>
> wget http://rcn-ee.net/deb/rootfs/maverick/ubuntu-10.10-minimal-armel.tar.7z
> md5sum ubuntu-10.10-minimal-armel.tar.7z
> 7za x ubuntu-10.10-minimal-armel.tar.7z
> tar xf ubuntu-10.10-minimal-armel.tar
> cd ubuntu-10.10-minimal-armel
>
> sudo ./setup_sdcard.sh --mmc /dev/sdb --uboot beagle
I don't think it causes any harm, but you don't actually need 'sudo'
as the parts in the script that need it will call sudo itself.. (sudo
sudo xyz effect)
> Here is the pastebin of the boot.scr.
>
> http://pastebin.com/XUYgNVRN
That looks fine..
Ricardo Salveti
You can also try the pre-installed image released for Maverick at
https://wiki.ubuntu.com/ARM/OMAPMaverickInstall , it should work fine.
Trey
Trey
Trey
I noticed that your setenv is this: Kernel command line:
console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait ro
vram=12MB omapfb.mode=dvi:1280x720MR-16@60 fixrtc buddy=none
mpurate=800
I am not sure my monitor would show that resolution, how do I go about
changing it?
I have a Rev A2 board.
Thanks for your help, what should I try now?
On Oct 15, 3:12 pm, Robert Nelson <robertcnel...@gmail.com> wrote:
> On Fri, Oct 15, 2010 at 1:53 PM, Trey <weav...@myfastmail.com> wrote:
> > I am using thehttp://rcn-ee.net/deb/rootfs/maverick/ubuntu-10.10-minimal-armel.tar.7z
> > from thehttp://elinux.org/BeagleBoardUbuntusite.
> > I am using the following commands:
>
Robert Nelson
>
> I noticed that your setenv is this: Kernel command line:
> console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait ro
> vram=12MB omapfb.mode=dvi:1280x720MR-16@60 fixrtc buddy=none
> mpurate=800
>
> I am not sure my monitor would show that resolution, how do I go about
> changing it?
That one is usually the most compatible, but to change it is pretty easy..
First on the 'boot' partition, there is a boot.scr and boot.cmd
Open the boot.cmd file and change the 2/3 line "setenv dvi
1280x720MR-16@60" to 800x600MR-16@60 or something else.. save and
close..
Then:
mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Some Text" -d
./boot.cmd ./boot.scr
> I have a Rev A2 board.
Okay, same as mine..
Weird, it should as setup dump over the serial console..
> Thanks for your help, what should I try now?
Give this a test... ( i modified the 'setup_sdcard.sh' script to show
more information..)
first remove the existing setup_sdcard.sh file
download this new one:
wget http://rcn-ee.homeip.net:81/dl/updates/omap-image-builder/tools/setup_sdcard.sh
change permissions:
chmod a+x setup_sdcard.sh
then run it on your sd card again...
./setup_sdcard.sh --mmc /dev/sdb --uboot beagle
Regards,
Trey
port 81, and our company's it dept tries to get in the way any way it
can.
On Oct 15, 3:52 pm, Robert Nelson <robertcnel...@gmail.com> wrote:
>
> > I noticed that your setenv is this: Kernel command line:
> > console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait ro
> > vram=12MB omapfb.mode=dvi:1280x720MR-16@60 fixrtc buddy=none
> > mpurate=800
>
> > I am not sure my monitor would show that resolution, how do I go about
> > changing it?
>
> That one is usually the most compatible, but to change it is pretty easy..
>
> First on the 'boot' partition, there is a boot.scr and boot.cmd
>
> Open the boot.cmd file and change the 2/3 line "setenv dvi
> 1280x720MR-16@60" to 800x600MR-16@60 or something else.. save and
> close..
>
> Then:
>
> mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Some Text" -d
> ./boot.cmd ./boot.scr
>
> > I have a Rev A2 board.
>
> Okay, same as mine..
>
> Weird, it should as setup dump over the serial console..
>
> > Thanks for your help, what should I try now?
>
> Give this a test... ( i modified the 'setup_sdcard.sh' script to show
> more information..)
>
> first remove the existing setup_sdcard.sh file
>
> download this new one:
>
Trey Weaver
Changing monitor resolution did not help.
On Oct 15, 3:52 pm, Robert Nelson <robertcnel...@gmail.com> wrote:
>
> > I noticed that your setenv is this: Kernel command line:
> > console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rootwait ro
> > vram=12MB omapfb.mode=dvi:1280x720MR-16@60 fixrtc buddy=none
> > mpurate=800
>
> > I am not sure my monitor would show that resolution, how do I go about
> > changing it?
>
> That one is usually the most compatible, but to change it is pretty easy..
>
> First on the 'boot' partition, there is a boot.scr and boot.cmd
>
> Open the boot.cmd file and change the 2/3 line "setenv dvi
> 1280x720MR-16@60" to 800x600MR-16@60 or something else.. save and
> close..
>
> Then:
>
> mkimage -A arm -O linux -T script -C none -a 0 -e 0 -n "Some Text" -d
> ./boot.cmd ./boot.scr
>
> > I have a Rev A2 board.
>
> Okay, same as mine..
>
> Weird, it should as setup dump over the serial console..
>
> > Thanks for your help, what should I try now?
>
> Give this a test... ( i modified the 'setup_sdcard.sh' script to show
> more information..)
>
> first remove the existing setup_sdcard.sh file
>
> download this new one:
>
Trey Weaver
This did not work either, same problem.
On Oct 15, 3:22 pm, Ricardo Salveti <rsalv...@rsalveti.net> wrote:
> > OK, this will really confuse you Robert.
>
> > Since it would not load the kernel, I thought I would try a different
> > kernel. So I took the kernel from the original angstrom build that
> > came with the beagleboard-xm and put it on the ubuntu sd (uImage on
> > boot). The kernel then booted and got me to the prompt.
>
> > So is something wrong with the uImage that is supplied?
>
Ricardo Salveti
> Ricardo,
>
> This did not work either, same problem.
Can you try the following?
Edit boot.scr from the first partition and add proper console arguments:
1. Mount your SD card after flashing the image on it;
2. # cd /media/6B57-ED78/
3. # dd if=boot.scr of=boot.script bs=1 skip=72
4. Edit boot.script and add "console=ttyS2,115200n8" at the setenv line, like:
setenv bootargs vram=12M omapfb.mode=dvi:1280x720MR-16@60
root=/dev/mmcblk0p2 fixrtc console=ttyS2,115200n8 earlyprintk=ttyS2
loglevel=8
5. # mkimage -A arm -T script -C none -n "Ubuntu boot script" -d
boot.script boot.scr
6. Unmount the sd card and boot it on your board
See if changing the bootargs get you at least something at uart.
Trey
Do you know why if I replace the uImage file that you provided with
the one that came with Angstom Linux on my Beagle board that it will
boot?
On Oct 15, 7:17 pm, Ricardo Salveti <rsalv...@rsalveti.net> wrote:
Ricardo Salveti
> I will try that Monday.
>
> Do you know why if I replace the uImage file that you provided with
> the one that came with Angstom Linux on my Beagle board that it will
> boot?
Angstrom one is a quite different kernel.
Probably with earlyprintk you should be able to at least see something at uart.
James Pogge
I'm experiencing the exact same problem, my XM was received this
week, micron chip, A2 Everything includng video checked out with the
angstrom distribution.
I read all the wiki and threads I coukld find and followed the
instructions, beyond that the serial boot dump and the entire
experience above is as if wrote it.
The image hangs on whne booting the kernel
..
Uncompressing Linux... done, booting the kernel.
disk imager to create the SD card, it fails on 4G, 8G and 16 G sd
cards.
There is no signal at all on the video. I dont have the experience
with linux ti set a trace on the u-boot, a skill I will learn soon,
but I did place a bridge on the dvi as I have access to digital video
enabled O scope.. the DVI is dead.. As Ricardo mentioned, the console
may not be enabled during boot, so I can describe the action (limited)
of the XM
with a new SD card all 3 leds light up after 4-5 sec the xloader
progresses into uboot, and checksums. the serial stops at the booting
the kernel message and a series of user LED and the further left let
blink and sequence, (loading the rfs and ext , this continues for 20
seconds or so and the user led (middle?) blinks twicw every 2
seconds..
If after 5 min. I press reset or cycle power, the x loader and u-boot
is identical it reaches the user double blink faster subsequently from
a fresh load of the sd,
I have looked at the sd ram n my unix box and although I dont have a
file list, first glance tells me it is an intact image relative to my
x86 desktop version ,
After reading the above, the boot,scr ect are all correct and appera
to be functional, in my limited experience, the kernel is not at the
correct location expected to launch, address maybe,
or the HDMI/LCD display isnt initializing correctly (this is most
likely)
Could it be a difference in the latest delivered BBXM mine is 1
week old, most claims of a suceesful boot are from boards delivered
this summer or before sept. just a wag, they should be identical,
mine definitely has a micron ram, their logo is hard to miss. My
board is part of the Oct build. I will search for any info on the
hardware, Sorry that Im new to embedded linux, or I would be of more
use in helping identify the problem, I do however have extensive
hardware / driver experience, with smaller RTOS and FPGA embedded
esign ect so I expect I will improve as I learn..
Jim
On Oct 16, 1:08 am, Ricardo Salveti <rsalv...@rsalveti.net> wrote:
Ricardo Salveti
On Sun, Oct 17, 2010 at 12:30 AM, James Pogge <jpog...@gmail.com> wrote:
> Hi,
>
> I'm experiencing the exact same problem, my XM was received this
> week, micron chip, A2 Everything includng video checked out with the
> angstrom distribution.
>
> I read all the wiki and threads I coukld find and followed the
> instructions, beyond that the serial boot dump and the entire
> experience above is as if wrote it.
Please just follow what is described at
https://wiki.ubuntu.com/ARM/OMAPMaverickInstall
It's normal to stop at "Uncompressing Linux... done, booting the
kernel." because the console is not enabled by default.
If you can, after writing the image at the SD card, do the following
steps and then you'll be able to see at least something:
Edit boot.scr from the first partition and add proper console arguments:
1. Mount your SD card after flashing the image on it;
2. # cd /media/6B57-ED78/
3. # dd if=boot.scr of=boot.script bs=1 skip=72
4. Edit boot.script and add "console=ttyS2,115200n8" at the setenv line, like:
setenv bootargs vram=12M omapfb.mode=dvi:1280x720MR-16@60
root=/dev/mmcblk0p2 fixrtc console=ttyS2,115200n8 earlyprintk=ttyS2
loglevel=8
5. # mkimage -A arm -T script -C none -n "Ubuntu boot script" -d
boot.script boot.scr
6. Unmount the sd card and boot it on your board
If you get something at your serial then you can at least check what's
wrong with your kernel.
I'd suspect that this can probably be related with the x-loader/u-boot
and the latest xM revision. If the default ubuntu image doesn't work
for you, try grabbing just MLO and u-boot.bin from Angstrom image and
put at the first sd card partition.
Let me know if you're able to boot your kernel.
James Pogge
I was able to boot Ubuntu, its on the other thread, the power down
oin wasnt being enabled on the TSP410 HDMI device,
Ive been testing everything, USB sticks, bkluetooth USB, Web Camera
all work, The microphone input is recording and providing an
indicatrion on the bar graph, but the audo out is completely quiet,
The apps all show it as on and initialized but I get no sound not even
the nominal hiss.. I checked on a scope and both sides of the DC
blocking caps on the R and L output channels are flat (ground) it
would seem that the sound card is not properly initialized on the A3
either, or its no good, I havent seen anyone else report this.. It may
be early.
Jim
> > Hi,
>
> > I'm experiencing the exact same problem, my XM was received this
> > week, micron chip, A2 Everything includng video checked out with the
> > angstrom distribution.
>
> > I read all the wiki and threads I coukld find and followed the
> > instructions, beyond that the serial boot dump and the entire
> > experience above is as if wrote it.
>
Ricardo Salveti
> Ricardo, Hi
>
> I was able to boot Ubuntu, its on the other thread, the power down
> oin wasnt being enabled on the TSP410 HDMI device,
True, didn't expect to have xM A3 around already, and too bad we need
an extra kernel patch for it.
Opened bug https://bugs.launchpad.net/bugs/663642 for it, pointing the
new uImage. Also updated
https://wiki.ubuntu.com/ARM/OMAPMaverickInstall.
Please, if anyone with an xM A3 could test bug 663642 and report the
result it'd be very helpful (I only have a xM rev A board around, so
can't test).
> Ive been testing everything, USB sticks, bkluetooth USB, Web Camera
> all work, The microphone input is recording and providing an
> indicatrion on the bar graph, but the audo out is completely quiet,
> The apps all show it as on and initialized but I get no sound not even
> the nominal hiss.. I checked on a scope and both sides of the DC
> blocking caps on the R and L output channels are flat (ground) it
> would seem that the sound card is not properly initialized on the A3
> either, or its no good, I havent seen anyone else report this.. It may
> be early.
Yeah, there's a bug for this already, please check
https://bugs.launchpad.net/ubuntu/+source/linux/+bug/651302. And
thanks for reporting back the results of your testing :-)
Rob
Thanks,
Rob
Ricardo Salveti
> Verified the bug fix for DVI output on xM A3, it is working now!
Cool, thanks for testing, will forward the fix to the kernel team and
hopefully will be applied soon.