Reset bug 09/04/12 ROM

we should only need to wait 122ms for each device), but that’s likely to be a far riskier game

Wouldn’t setting this be an obvious candidate for a CMOS entry?

Hmm upgraded my BB-xM to the ARMini OS4 yesterday and apart from !territory not working seemed fine. Today however the monitor remained black. The board itself seems to boot, at least all the lights come on as does the keyboard. Hard to tell though with no video output. Had some success with pulling my boot drive. After a few minutes got to the supervisor. Booting off a flash drive via powered hub, HD4 connected to second powered hub. Never had this sort of behavior before. My BB-xM is equipped with Sprow’s CMOS widget btw.

Swapping µSD cards, returning to a previous ROM cured this. Monitor came on in the usual way. Nothing obviously wrong with the SD card itself, had a look under windows and as I once managed booting successfully with the new ROM I’d doubt this to be down to file corruption.

Todays ROM (26/04/12) seems to have fixed the reset issue. Is the module initialisation stuff being displayed before the RISC OS start up screen left over from debugging or a feature of a quicker display init?

or a feature of a quicker display init?

That’s the one, I think.

Yeah, the display is turned on quicker now, so you’ll get to see the debug stuff which would normally have been hidden.

patric: Did you try rebooting the board to see if it was just a one-off? And did you see the orange screen at all? (Assuming you usually see it – I think some of the earlier u-boot versions didn’t show it properly on the BB-xM)

What you’re describing could be the rare crash/hang I was seeing while trying to recreate Frederick’s problem. I still need to try and track down what it is, and whether it’s something that’s been caused by the SmartReflex driver or whether it’s always been there.