Bugs in 5.2x

Sometimes when starting up it takes a long time for the DHCP address to be obtained (so long I eventually interrupt it with Escape) – I then get the error message ‘Message token ErrButtNoFlop not found (error &AC2)’. The long time to get the DHCP address was because the network cable was not firmly in place so that one I solved!

If I click on ‘Boot’ and then the ‘Look at’, ‘Add to apps’ and ‘Run’ items in the boot configuration plug-in (so that all three windows are open) I sometimes get an error ‘SWI &8A60 not known 50’ when clicking either ‘Add to Apps’ or ‘Boot’.

If I open all three options and then click ‘cancel’ in the ‘Boot’ window from whioh I opened them, I always get an error ‘no stack for trap handler AODT at B8C8’ (the address varies sometimes B9C0 is one of the possibilities). All four windows then close with no other untoward effects.

This was using RISC OS 5.2x (10-Jun-2013) on a Beagleboard XM.

If I open all three options and then click ‘cancel’ in the ‘Boot’ window from whioh I opened them, I always get an error ‘no stack for trap handler AODT at B8C8’

I couldn’t recreate that here. Do you still see it with the latest ROM + disc image?

I can confirm Chris problems. Also with the latest disc image. If I use the latest ROM (I try the 1. May one.) I have not the DHCP problem but my USB will not work correct. HD and USB-Stick are not detected.
Note: I only can confirm this with my Rev.C xM, curiously my Rev.B xM works correct.
With older ROMs, also older 5.21, I have no problems with the Rev.C.
If DHCP failed and I interrupt with ESC, in the network settigs no EtherUSB aviable. If I interrupt a “working” DHCP before it is connected, EtherUSB is aviable in the network settings.

Fixed with this… https://www.riscosopen.org/forum/forums/4/topics/2530?page=1#posts-32632

pandaboard with rom dated 2014-06-13 06:40:13 can’t get passed
OMAP4 HAL init
Board config=PandaBoard
HAL_Init
HAL initialised
IICInit
HAL_KbdScanSetup

it hangs there.. Any clues on how to get the latest rom running?

oh.. and when returning to the previous ROM it appeared the RISC OS partition on my SDcard has been rendered unreadable. A little fiddling in Linux and it magically fixed itself..
Which reminds me: always make backups!

Maybe try writing the new ROM again? If the card had become corrupted then maybe it didn’t write properly the first time round.

If that doesn’t work, try disconnecting some of your USB devices – it’s possible that the hang you’re seeing is being caused by some recent changes to USB device initialisation.