Beagleboard XM - no video out

Well I’ve just got my hands on a Beagleboard XM (says rev B on the box and on the board…but the x loader on RS232 output reports it as Beagle XM rev A)

reading riscos

4194304 bytes read
## Starting application at 0x81000000 ...
OMAP3 HAL init
Board config=BeagleBoard
HAL_Init
HAL initialised
InitCMOSCache entry
InitCMOSCache done
IMB_Full done
Keyboard scan complete
FIQ enabled
IRQ enabled
VduInit
ExecuteInit
Machine ID duff,zero substituted
KeyInit
MouseInit
OscliInit
Enabling IRQs
IRQs on
HAL_InitDevices
HAL RTC detected!
Leaving LookForHALRTC
InitVariables
AMBControl_Init
ModuleInit
OMAPVideo:
OMAPVideo: ***** Debug Session Started **************************************
OMAPVideo: DebugLib is (c) Pace Micro Technology plc. 1997-2001
OMAPVideo: System: DebugLib 0.65
OMAPVideo:         remotedb 0.10
OMAPVideo:         PDebug 0.07
OMAPVideo: Task:   OMAPVideo
OMAPVideo: Time:   Fri Jan  2 00:00:00 1970
OMAPVideo: Levels: Not specified.
                             OMAPVideo: ******************************************************************
OMAPVideo: Using DMA channel at f9e56c20
OMAPVideo: dss_reset
OMAPVideo: Finished module initialisation, DSS regs=f9e50000
OMAPVideo: dispc_set_lcdmode: rate=25175000 syncpol=3
OMAPVideo: hsw=96 hfp=18 hbp=46 width=640
OMAPVideo: vsw=2 vfp=11 vbp=32 height=480
OMAPVideo: dsi_pll_program_for_dispc: Changing pixel rate from 0 to 25175000
OMAPVideo: REGM=122 REGN=6 REGM3=8 REGM4=8
OMAPVideo: Fint=1857142
OMAPVideo: dsi_pll_program_for_dispc: Done
OMAPVideo: dispc_set_lcdmode: Done (0)

Sounds like you have one of the new boards mentioned in this thread. There’s a mention there about the DVI power GPIO being changed, but at first glance it looks like RISC OS is already doing the right thing. When I get home tomorrow I’ll have a proper look to see if there’s anything wrong.

In the meantime, are you sure it’s not something silly like the signal being out of range for your monitor? :)

My monitor is going into powersave mode when switched to DVI input – its not showing any error such as out of range or anything like that.

I have also tried blind typing wimpmode 27, wimpmode 28, wimpmode 32 etc, various combinations, F12 then trying them wimpmode commands. Nothing appears on screen and the output on serial never changes beyond what I posted above.

Chances are I have one of the latest revision boards – it only came into stock at Digikey USA last week and arrived Friday last week. Hearing that some Ubuntu users have had similar issues is reassuring thats its not just RISC OS having trouble initialising DVI. If theres any tests I can do, please let me know and I’ll give it a whirl.

Edit Just found this bug report on the Ubuntu bugtracker

Edit Just found this bug report on the Ubuntu bugtracker

Yup, it looks like the RISC OS equivalent of this fix will do the trick. There’s a ROM image here that should work.

Well Ive tried that rom image you’ve just uploaded and alas, no video output. Monitor remains blank, goes into power save mode as if there is no signal there. Output from RS232 shown below:

reading riscos

4194304 bytes read
## Starting application at 0x81000000 ...
OMAP3 HAL init
Board config=BeagleBoard
HAL_Init
HAL initialised
InitCMOSCache entry
InitCMOSCache done
IMB_Full done
Keyboard scan complete
FIQ enabled
IRQ enabled
VduInit
ExecuteInit
Machine ID duff,zero substituted
KeyInit
MouseInit
OscliInit
Enabling IRQs
IRQs on
HAL_InitDevices
HAL RTC detected!
Leaving LookForHALRTC
InitVariables
AMBControl_Init
ModuleInit
OMAPVideo:
OMAPVideo: ***** Debug Session Started **************************************
OMAPVideo: DebugLib is (c) Pace Micro Technology plc. 1997-2001
OMAPVideo: System: DebugLib 0.65
OMAPVideo:         remotedb 0.10
OMAPVideo:         PDebug 0.07
OMAPVideo: Task:   OMAPVideo
OMAPVideo: Time:   Fri Jan  2 00:00:00 1970
OMAPVideo: Levels: Not specified.
OMAPVideo: ******************************************************************
OMAPVideo: Using DMA channel at f9e56c20
OMAPVideo: dss_reset
OMAPVideo: Finished module initialisation, DSS regs=f9e50000
OMAPVideo: dispc_set_lcdmode: rate=25175000 syncpol=3
OMAPVideo: hsw=96 hfp=18 hbp=46 width=640
OMAPVideo: vsw=2 vfp=11 vbp=32 height=480
OMAPVideo: dsi_pll_program_for_dispc: Changing pixel rate from 0 to 25175000
OMAPVideo: REGM=122 REGN=6 REGM3=8 REGM4=8
OMAPVideo: Fint=1857142
OMAPVideo: dsi_pll_program_for_dispc: Done
OMAPVideo: dispc_set_lcdmode: Done (0)

Ctrl G still gives a beep. Incidentally ive also now hooked up a TV to the S Video socket as well as a HDMI connection. When the machine boots it shows NTSC colourbars then blanks the TV when RISC OS takes over.

Should also mention, tried blind typing the usual wimpmode commands to try and force a display. Still no joy. Tried booting without any USB devices attached. Still no video.

Just noticed you’ve uploaded a new image…. the ROM is called kui800-00. I’ve renamed it riscos, stuck it on my microsd card. Booted the beagle and hey presto, I have a supervisor prompt! :) USB keyboard on beagle doesnt respond, but I can access the command line via putty → RS232 link. Typing desktop via the RS232 link got me into the RISC OS desktop :) Mouse works too :)

OK; are you sure you copied the earlier iu8i00-00 ROM image properly? The only thing that should have changed between ‘i’ and ‘k’ is that I enabled the debug terminal (and there was an intermediate ‘j’ image which I ran on my beagle just to make sure the GPIOs were being set properly). I was going to upload another new image in a minute (and tell you about it this time!) – after uploading the ‘k’ image I had a closer look and realised that there were some extra registers to control the pull up/down resistors, which so far I’d been ignoring, so I was just quickly adding some code to set those to the same values Linux uses (although the defaults should be fine – which, judging by your success, looks to be correct).

But now that everything seems to be working, I’ll upload another image in a minute with the debug terminal turned off so your keyboard will work properly (in fact the image should be identical to the ‘i’ one, except I’ve already deleted that to tidy up my output folder!)

New ROM image uploaded. It might be best to keep a copy of the one that you’re using now, just in case something very strange is happening. Also if it ever boots up with no video output and lots of debug output over the serial port, then that’s a known bug (the rarity makes it a bit of a bitch to try and fix). Reset the board once or twice and everything should go back to normal.

The latest ROM (uploaded at 00:44AM 26/10/10) gets me to a Supervisor prompt on the DVI output but neither my USB keyboard on Beagle or the RS232 keyboard link works now. Did you remember to enable local USB keyboard support on that ROM release?

Did you remember to enable local USB keyboard support on that ROM release?

Yes – it’s either one or the other. In fact, even with the debug terminal enabled, your keyboard should still work in the desktop, and when at the command line caps lock/num lock/etc. should still toggle the LEDs.

I say USB keyboard – its actually a PS/2 to USB converter (which was working fine earlier making RISC OS beep with Ctrl G with the version of the ROM with no video out) The same converter works fine on the Iyonix too. The latest ROM doesnt allow RS232 keyboard input or input from my PS/2 to USB converter. Ctrl G does not make the sound beep any more, but the Caps lock, numlock and scroll lock lights respond.

Well if the caps lock/etc. LEDs are toggling on and off properly then USB is working. And after redownloading the archive, extracting the ROM image, and trying it on my beagle, I know that the debug terminal is definitely off and USB keyboards definitely work from the command line & desktop.

Are you sure you’re dismounting the SD card properly after copying the ROM image to it? (Iconbar dismount option under RISC OS, or the ‘safely remove hardware’ option from the notification area of the taskbar under Windows XP. I’m not sure offhand where the equivalent option is hidden under Vista/7).

Well I don’t know what happened there, but I have re-downloaded that ROM image, did a fresh copy to the memory card, dismounted correctly, booted from it and hey presto. It works as it should. Just sorting out a Boot sequence for it now :) Thanks for getting it working!

Thanks for getting it working!

No problem. The fix is now in CVS, so future downloads from the ROOL site should work without problem.

Been trying to get my hands on one of these… nobody seems to have them.. whats the deal?

With hindsight, perhaps we should’ve all clubbed together and placed a bulk order!

ISTR reading on the BB mailing list that Digikey are best placed in terms of pre-orders with beagleboard.org. They’re currently estimating a shipping date of 7 Nov on their order page… but such info has been incorrect before. (As a previous customer of theirs, I could investigate whether it’s possible for me to place a multi-unit order with different shipping addresses if that may help you and a few others. Otherwise, just place your order and hang tight!)

Another update from the Ubuntu Developer Conference is that it’s the PandaBoard which is now the exiting stuff.

http://pandaboard.org/

Obviously there are substantial differences from the BeagleBoard.

You’re right but as Jeffrey and others have pointed out, it’ll require a huge development effort. However, I thought it’d be a good idea to get a RISC OS project listed anyway, with the intention of attracting early developer interest before the platform becomes too swamped with projects to choose from. (Apologies for simplicities in my wording – I’m sure they can be corrected if the pandaboard.org people are contacted.)

I do fancy the panda board too..

My problems seems to be that i’ve always been waiting for someone to have the beagle in stock before ordering. Been waiting since July now though.

S

I’m up for a development drive on the panda if a few other people are in with me.

If Jeffrey can get the video up i’ll start on the NICs and other gadgets.

S

Surely we could get it up and going single processor relatively easily though?

I’m up for a development drive on the panda if a few other people are in with me.

I wish were skilled and knowledgeable enough to consider myself a developer!

If Jeffrey can get the video up i’ll start on the NICs and other gadgets.

Jeffrey will be in danger of repeating his todo list explanation

Surely we could get it up and going single processor relatively easily though?

If there’s a considerable delivery delay then perhaps the OMAP3 port will be finished in order to move on to this!

Farnell still haven’t shipped my -xM :( At this rate I think I’ve got more chance of receiving my Pandora first!

Farnell still haven’t shipped my -xM :(

Might be quicker to demand a refund (assuming they’ve already taken your money) and re-order from either Digikey or Mouser