RISC OS Pi card on 3B+

Can someone confirm for me whether the current (2022-02-10) RISC OS Pi disc image works on a Pi 3B+?

My SD card went kaput :-( I put the above image on a new card, but it didn’t work.
I don’t have a monitor on it so I can’t say much about what happens; but the
keyboard lights work for a few seconds, and then freeze. I don’t get a beep. The
green ACT light flashes twice, is off for about 6 seconds, and then is on continuously;
I don’t see any of the usual flickering you get. I tried burning the card with both
Raspberry Pi Imager, which verified ok, and dd as well. Raspberry Pi OS works fine.

@ Julie

I did just the RISC OS img replacement on mine and it worked. Did not re-flash the SD, just replaced files in the FAT32 “partition”.

Downloading your linked image now and will give it a try if it gets flashed quickly and let you know.

Can someone confirm for me whether the current (2022-02-10) RISC OS Pi disc image works on a Pi 3B+?

Worked just fine here. Using Raspberry Pi OS bullseye 64bit on the RPi3B+ the Imager written RISC OS booted perfectly. A monitor was connected.

IIRC it is possible to get into a catch 22 thing in that the Pi may not startup at all without a monitor connected. This has been discussed before and also as I recall my work around did not work for other.

memory refresh The Pi does start up without a monitor connected, the catch 22 was that there is no HDMI output so connecting the monitor later is no good.

https://www.riscosopen.org/forum/forums/4/topics/16391

https://www.riscosopen.org/forum/forums/11/topics/16732

I did have some HDMI lines in my old config.txt, but putting those back in didn’t make it boot.

It seems to be at a command line, and unable to find SDFS::RISCOSPi, because if I type *a the ACT light comes on, which I take to be it saying ‘Please insert disc’ and if I press Escape the light goes off again. It doesn’t go on if I type *help

But usually at the command line I’d get a beep pressing Ctrl-G, and it doesn’t now.

Right, I’ve got a lot further … but I’m not there yet.

I burnt RISC OS Pi to a USB stick and if I remove the SD card then the Pi boots fine from USB.

But if I have the SD card in with Loader on (which is how I want to do things), it won’t boot.

The reason is SDFS thinks the drive is empty. If I take the card out and put it back in, it then sees the card there. But it’s too late, it hasn’t loaded CMOS (which is why I didn’t hear any beep), and you have to type !Boot to carry on.

So for some reason RISC OS doesn’t see the card if it is inserted when you turn
the power on. I use to be able to boot fine. The Pi firmware I was using before was
dated June 12 2020. Did something change after that?

It sounds the same as the problem Thomas was having.

I had a similar issue with several SD cards and a Pi 1B. After buying a Pi 4B, the problem was the same. Tried NOOBS, Risc OS Direct and plain Risc OS downloads and no combination of them worked.

It was stuck at the command line, thinking there was no drive present. *Desktop got me to the desktop but with an error saying boot had not run. Of course, you can’t even use configure without boot running first!

The solution was a different SD card. The cards I was using were all the same size by the same manufacturer. A different size card by the same manufacturer and it worked without me doing anything different.

All the cards that did not work were tried again but this time with Linux installed and they worked no problem. So one of those cards went into a Pi Zero running Linux.

The problem is not SDFS. When the SD card is read to look for CMOS, START.ELF, RISCOS, CONFIG.TXT and BOOTCODE.BIN it is being examined by the Pi boot firmware, using a filing system looking for a FAT partition, not RISC OS. Newer firmware then tries for a USB drive and boots from that.