Beagleboard Xm

Yes, it says ‘Click!’ and then ‘Beep’.

That sounds about right. Although I’ll hopefully get round to fixing the click one day ;)

[Edit: Whether it’s of any direct use in connection with castle/RiscOS/Sources/HAL/OMAP3/s/Audio is another matter, of course!]

I just tried following Chris’s instructions above (Sep 8, 10:44 am) for creating a u-boot boot script which would prompt the user to pres the USER button for RISC OS:

echo Press USER button to enter RISC OS
sleep 10
mmc init
if userbutton; then fatload mmc 0 0x80100000 riscos; go 0x80100000; fi
echo Entering Angstrom GUI
setenv bootargs 'console=ttyS2,115200n8 console=tty0 root=/dev/mmcblk0p2 rw roofstype=ext3 rootwait omapfb.mode=dvi:1280x1024MR-16@60'
setenv bootcmd 'fatload mmc 0 0x80300000 uImage; bootm 0x80300000'
boot

The script works to some extent (i.e. if I don’t press the button, we go through to Linux) but I don’t see the prompt anywhere. Should it be appearing on the monitor? Or would it have appeared only on the serial port output? I’ve never had to connect the serial cable, thankfully! If it’s meant to appear on the monitor perhaps there are simply issues with the signal being out of range for our monitor.

I think I am going to revert to my previous dual boot method, which was to replace the user.scr with one to boot RISC OS, and have the boot.scr go into Ubuntu. It doesn’t allow for three different options as Chris’s method appears to, but that’s OK.

but I don’t see the prompt anywhere

Guys,

Is there a summary for getting RiscOS to boot on the xM?

This wiki page should sort you out:

http://www.riscosopen.org/wiki/documentation/pages/Using+the+Cortex-A8+port

Thanks Jeffrey,

I’ve decided to sell my bb-xM as i’m not very happy with it. Anyone interested before i stick it on fleabay?

Thanks Jeffrey,

I’ve decided to sell my bb-xM as i’m not very happy with it. Anyone interested before i stick it on fleabay?

I’m interested, but would like to know why you’re not happy with it. Oh, yes, and how much please ?

Dave,

I just don’t like how everything is serial attached on the xM. I prefer a proper CPU bus and I’m planning on doing some FPGA work. Looking for 80 quid for the board (+ min postage or can collect). Its boxed (and comes in a sealable anti static bag) and has been turned on 4 times comes with the linux demo sd card. I didn’t get a PSU with it so I’m not including one.

Stephen, Yes, I’ll have it please, where are you located ?

I’m located between Glasgow and Edinburgh.

Bit too far for me to drop in :)

Do you want me to send a cheque ?

Best if we take this off list.

t e c h @ e t c s y s t e m s . c o . u k

Hi everyone just got a bbxm rev c when i try to start 5.17 with the mlo & u-boot on the sd card that came with it all i get is a blank screen card created using sdcreate. so i used an older version of u-boot from the validation image in the troubleshooting guide now i get a boot screen that will go to the supervisor but with no usb so no keyboard input and idea’s

Have you tried this image? (Cf. "Problems…" thread but not sure how successful it’ll be.) I’ll upload some images some time when I can.

Tried the iamage wrote it to the sd card no luck card would not boot at all looked at it on my iyo and changed the mlo file the card get seen by the bbxm board will see the card lights on board still no luck changed the u-boot boot the rob image to the start.
512 mb, cortex 8 waiting for boot drive ect, sits at aflashing cursor for 30 mins then message memory cannot be moved (error Number &1C1) then supervisor promt but still no keyboard access. any more ideas???

Does the image on the SD card supplied with the board boot up OK? If so, then I guess the board’s alright.

bbxm rev c

Hmmm, perhaps you’re the first to try RISC OS on a rev C xM. There seem to have been some issues with Ubuntu.

• Above beagleboard.org mailing list thread 28 Apr
• Current pre-built ROM image 16 Apr
• Apparently no recent source changes since then which may address the xM rev.C

Rob, have you got your Beagleboard-xm rev c working since your post on the 15th?

As the rev c has been available since April, I wonder if Andrew Rawnsley of RCOMP has had this problem on the latest ARMminis.

No Not yet but looking at the problem there seem to be soom hardware changes i will let you know how we go

Good. I did mention this last week, BTW ;-)

It does look like there might have been a couple of relevant hardware changes between the xM rev A/B and rev C. But trying to tell the difference between bits which have actually changed and bits which people simply say have changed is a bit tricky. I’ve got a couple of things noted down which I’ll investigate tonight; I’ll report back once I know what’s going on.

This ROM image should work: http://www.phlamethrower.co.uk/misc2/riscos.zip

well done jeffrey it works now, some times the usb is a bit flakey the mlo andu-boot seem to be the inportant bits, the colours are a bit washed out this benq led.
Now got to get networking sorted so that i can tranfer some software over. i will keep you informed on progress.
Thanks by the way what where the changes???

Brilliant!

what where the changes???

If you can’t wait to get it from the horse’s mouth, check the changelog.

Next update something is wrong not sure if it me selecting the wrong MLO & U_boot files but have to boot linux (or no usb or Vid) then switch the cards pressed the reset button to get Riscos to boot but the video is shifted into the red so everything has a pink tint. what mlo & u-boot file did you use to get it to boot on it’s own versions date stamp???
Is the pink tint because i booted from the sd card that came with the xM this was beta 4.25, downloaded 3.3 video is fine with the xM test images, but still the same problem if you try to boot without first booting linux to set up usb.
too many qustions no answers yet

Thanks by the way what where the changes???

The only functional change was to invert the pin that’s used to control the EHCI (USB) power.

what mlo & u-boot file did you use to get it to boot on it’s own versions date stamp???

So far I’ve been using the mlo & u-boot that came with the board. But I’ve only got a rev A board, so I don’t think trying to use the same mlo & u-boot as me will solve your problems.

Is the pink tint because i booted from the sd card that came with the xM this was beta 4.25, downloaded 3.3 video is fine with the xM test images, but still the same problem if you try to boot without first booting linux to set up usb.

I’m not sure what could be causing the pink tint problem; it’s not something I’ve ever heard of before. The only thing I can think of is that the hardware which does the red/blue swapping isn’t working, or something’s wrong with the gamma tables. Would it be possible for you to take a photo of the screen? It’d probably be easier than trying to describe the problem.

I do know that they changed to a newer DM3730 revision recently (either for the rev B or C boards), so I’ll have a good look at the docs tonight to see if there have been any changes to the video hardware. I’ll also try the 4.25 & 3.3 images with my xM to check that they work fine, and try using their mlo & u-boot in place of the ones I’m currently using.

Done a screen grab in paint on xM looked at it on iyo and it looked perfect so i can only guess it could be the htmi to dvi converter that i have any thoughts will try a different type over the next couple of days and report back strange because it works fine in linux