Pi hangs at startup?

I should have added I vaguely remember PIs used to have a problem with some powered hubs – don’t know if they still do. It may be worth taking it out of the equation.

The value of the RAM disc section in Configure\Discs wont accept changes and is stuck at 0.1mb. Quiting RAM and sliding the DA size up resolves this particular problem. I guess I need to replace !Configure with the latest from the daily HD image?

Yes … see https://www.riscosopen.org/forum/forums/11/topics/3656

Do you use the same SD card for your tests on both Pi?

It remembers me a problem I did have a few weeks ago. Changes made to the DOS partition visible in !Boot were not applied to the DOS partition visible from a PC (and used to boot the system). So I completely erase partitions on a PC, use HForm, then made a new SD with SystemDisc, with the right ROM and right HardDisc file, and all problems are now solved.

Do you use the same SD card for your tests on both Pi?

No, each Pi (I have five in total, 2xB, 2xB+ and a Pi2) has it’s own card of varying manufacturer.

Whilst rebuilding the Pi2, I tried both the NOOBS route and full SD image, both with the same results. Also updated the firmware to the latest version after the 3rd attempt to see if firmware was at play.

Colin – thanks for the builds, I’ll get testing…now if only I could get the damn thing to break reliable like it was doing yesterday!!

Yes … see https://www.riscosopen.org/forum/forums/11/topics/3656

I did update, which has fixed the Configure problem, however I still get “Corrupt Free Space Map” randomly after boot if I don’t first Quit the RAM drive and then slide the slider up, so I suspect there’s a bug in there somewhere. I’ll work out repro steps and post a Bug report.

I’ve also had it randomly cause an Abort, if you go into Discs, change the RAM drive size, exit and then immediately go back into Discs.

Unfortunately, I’ve not seen this issue once since the nightmare I had during initial setup.

After the London Show is out of the way, I’ll attempt to rebuild the Pi2 again from scratch and see if it reproduces the issue.

I’ve just had an Abort after the Module init process, which is USBDriver related:

FC1E4D60 : 1A000012 : BNE     &FC1E4DB0
FC1E4D64 : E5952004 : LDR     R2,[R5,#4]
FC1E4D68 : E5920000 : LDR     R0,[R2,#0]
FC1E4D6C : E5903030 : LDR     R3,[R0,#48]
FC1E4D70 : E3530000 : CMP     R3,#0
FC1E4D74 : 11A01006 : MOVNE   R1,R6
FC1E4D78 : 11A0E00F : MOVNE   R14,PC
FC1E4D7C : 1593F010 : LDRNE   PC,[R3,#16]
FC1E4D80 : E5D41040 : LDRB    R1,[R4,#64]
FC1E4D84 : E3C12010 : BIC     R2,R1,#&10         
FC1E4D88 : E5C42040 : STRB    R2,[R4,#64]
FC1E4D8C : EA000001 : B       &FC1E4D98
FC1E4D90 : E3590000 : CMP     R9,#0
FC1E4D94 : 1A000005 : BNE     &FC1E4DB0
FC1E4D98 : E5951014 : LDR     R1,[R5,#20]
FC1E4D9C : E5B12044 : LDR     R2,[R1,#68]!
FC1E4DA0 : E3520000 : CMP     R2,#0
FC1E4DA4 > 02851014 : ADDEQ   R1,R5,#&14         
FC1E4DA8 : E5852014 : STR     R2,[R5,#20]
FC1E4DAC : 05851018 : STREQ   R1,[R5,#24]
FC1E4DB0 : E5952004 : LDR     R2,[R5,#4]
FC1E4DB4 : E5951008 : LDR     R1,[R5,#8]
FC1E4DB8 : E5923000 : LDR     R3,[R2,#0]
FC1E4DBC : E5912000 : LDR     R2,[R1,#0]

*where fc1e4d9c
Address &FC1E4D9C is at offset &00005D64 in module 'USBDriver'

No reg info I’m afraid, as the machine locked solid.