First boot from SD card

Having downloaded an image from the RISC OS page and put it onto a micro SD card (whole thing from scratch twice) I then put the card in my Pi3 and turn on. I get the multicolour splash screen followed by nothing. While the Pi3’s power LED is on throughout, I see no other signs of life. I know this is a hugely basic level of question but – help! – is this a known problem or can anyone suggest a way ahead? Incidentally, the Pi3 runs fine with Raspbian and Mate – I just want the very different platform RISC OS seems to offer…

You need to download the latest firmware and boot code to allow it to run you can get them here http://www.svrsig.org/software/update4.zip
Use these files to update RC14 image that you wrote to the sdcard then reboot.

Gotcha! Knee deep in grandchildren just now – will try that later…

Prompted by this thread, I spent some time this afternoon getting a Pi 2 to work. I had given up on it some months ago.

It does remind me that finding all the necessary bits of firmware and software is difficult enough to put people off. Maybe I’ll get round to creating a wiki page with all the pointers (that I know) in one place.

I needed:

• new firmware and boot code, as in Rob’s posting above;
• new RISC OS image (I used the nightly build);
• new !Boot (I used the one from the nightly HardDisc4 build);
• new PiSerial modules (because, in my case, I have a thermometer/hygrometer/thermostat connected to it via serial, and I use the Pi to make its results available over the LAN).

Having postponed my effort until tomorrow, that post scares me more than a little. Candidly, I wouldn’t know which RISC OS image would be the right one or what the right !Boot file should be like or, I suspect, other stuff too. Is there some publication around that could help me identify what I do/don’t need? If not a publication, are there websites that can improve my knowledge to a point where I’m not blindly trying options on a suck it and see basis?

new !Boot (I used the one from the nightly HardDisc4 build)

The standard !Boot you download is missing the CPUSetup plugin to allow the Pi to have Alignment Exceptions and Emulated Rotated Loads turned on/off. The latest version is significantly altered by ROOL compared to my original version, so I don’t know how you would get it. Maybe ROOL could make it available to download from the Raspberry PI downloads page, or give me permission to put it on my page?

I posted the easy step for this here https://www.raspberrypi.org/forums/viewtopic.php?f=55&t=140140 read though the posting i made just miss the bits about creating an SDcard on a mac as you already have an image to update.
when I get time later i will do a generic post with pic’s and put up somewhere for everyone.

You need to download the latest firmware and boot code to allow it to run you can get them here
…and the latest RISC OS, as well, surely? The SD card image dates from February 2015…

Prompted by this thread, I spent some time this afternoon getting a Pi 2 to work. I had given up on it some months ago. It does remind me that finding all the necessary bits of firmware and software is difficult enough to put people off.

As far as I’m aware, a Pi 2 “should” work with an unmodified RC14 image. It’s only Zero and 3 that need to be manually tweaked. I don’t own a 2 but it is certainly my impression that it’s supported.

I don’t own a 2 but it is certainly my impression that it’s supported.

Me either but the news article for the release specifically mentions pi2

Having postponed my effort until tomorrow, that post scares me more than a little.

You should therefore wait until ROOL has updated the RC14 SD card image to work with the model 3 Raspberry Pi.

The alternative is to create your SD card (as you have done) using the RC14 SD card image. Find someone with a model 2 or model 1 version of the Raspberry Pi. Ask them to allow you to update your SD card using their machine. Start their card up with your SD card in it. Download the latest firmware and boot code (which includes a recent low vector ROM) under RISC OS from the URL http://www.svrsig.org/software/update4.zip – then run !SparkFS (it is in the ‘Utilities’ directory on your SD card under RISC OS) – then drag the update zip onto its icon bar icon under RISC OS – this will open up the archive and show you what is inside (which includes a directory called !Boot). Make sure Filer/Options are set to Force and Verbose (only) [click MENU over a filer display window and open the sub menu ‘Options’] and simply copy the !Boot directory over the !Boot directory on the SD card. Now remove the SD card (without shutting down the model 1/2 Pi)and it should start OK on your model 3.

The un-updated SD card containing RC14 won’t run on the model 0 or model 3.

that post scares me more than a little.

None of it is difficult in principle. Currently it’s not as easy as I would like it to be, mainly because it appears that we have to get a “kit of parts” of firmware and software that all have to be compatible, and there is no single place to get the parts, or even to get a single complete set of links to where they can be found.

Once you’ve got all the bits, and the set of instructions, all anyone has to do is follow the instructions. The results will work.

It sounds like the new user experience, particularly for a Pi 0 or Pi 3, is a little rough.

I found that the rc14 image worked fine on my Pi 1 (a B+), which you would expect. I chose to update it to the latest Pi firmware, latest RISC OS ROM, and latest HardDisc4. Now that was quite a geeky ride (but easy for those of us who have used RISC OS for years, and read hundreds of posts here!

I wonder if a refreshed image would make things easier? Who was/is responsible for pulling together the current one? What help can they accept from the community?

A good start would be rc14, then the latest Pi firmware, latest RISC OS ROM, and latest HardDisc4. For bonus points, update some of the other bundled apps.

Thinking further ahead, the entire HardDisc4 and the magic in Loader would benefit from being controlled via PackMan…

I wonder if a refreshed image would make things easier?

It is long overdue; and to be honest I’m wondering about a 4GB image. I don’t know about the UK, but it’s getting hard to find 2GB cards here in France, and those that exist are carrying a daft price premium.
[hmm, is there even such a thing as a 2GB microSD card?]

For the Zero, it should be utterly easy – updated firmware, updated RISC OS. After all, it’s basically a Pi Electron (ARM11 with go faster stripes and most of the bells and whistles stripped out – a bit like the Electron).

For the Pi3, it’s a potentially a more complicated proposition as that (ARMv8) processor doesn’t support the SWP instruction. I’d be inclined to update everything on the SD image to the latest versions and hope for the best, as performing a full check is not something that can be done and dusted in a couple of hours.

It is long overdue

Indeed. A few months ago I remember seeing/hearing that RC15 was due “soonish” (may have been said at Wakefield) but I’m not sure what the actual timeframes were. The only forum post I can find is my own, which isn’t too helpful :)

It is long overdue; and to be honest I’m wondering about a 4GB image.

The 2GB image will work on a larger card with no problems. You could even add another partition above to use the rest of the card – but not a filecore one – perhaps a linux type. If you want a larger image then you just need to buy SystemDisc from Ben.

For me, the new user experience is more than a little rough! I have two Pi3s – one running Raspbian and the other Ubuntu Mate – no problem with either. I also have a Pi Zero that I’ve done nothing with as yet. But, the more I read here, the more I’m left thinking that to get RISC OS running I need to have a Pi that’s already running RISC OS. I’ve tried all I can by downloading stuff on my desktop PC – and have got nowhere. This evening, I tried running a MicroSD I bought ready loaded – same result. Not encouraging! Might a Pi2 help me get further? or should I just give up…

If you open the update4.zip under Windows and look in the !Boot.Loader directory you will see the firmware and RISC OS ROM files. Look in the FAT partition on the un-updated RC14 SD card, again under Windows, and you will see the same set of files but older. Copy the newer files to replace the older files. Now the updated SD card should just work on the Pi 3 or Pi 0.

For me, the new user experience is more than a little rough!

Fair comment: the Pi3* RISC OS port is unfortunately much less developed than those for the earlier machines, where you can get an RC14 SD image that will run ‘out of the box’. Your best plan might be to attend one of the regular user-group sessions [see: http://www.riscository.com/category/user-groups/
] and bring your Pi3 and/or a blank SD card with you. Or wait for the next RISC OS Show which is in Feltham near London on 29 Oct: either way you’ll find people who are expert /and/ friendly. But do persevere, RISC OS can be addictive (I should know: I started in 1994)!
[*which I don’t have, otherwise I could run you up a discimage]

Thanks both, I’ll try again tomorrow (in a consciously fully organised mode) and see if I can’t get it right this time. Otherwise, as you suggest George, I’ll play a longer game. I do know what I want… I wrote a full OS for an Army ICL1903S back in the seventies and loved every moment. If I could manage that, RISC OS can’t be impossible, can it?

It sounds like Chris has had a go at simplifying things. What is in update4? New firmware, ROM and HD4? And it can be unzipped on Windows or Mac OS X so you don’t need a working RISC OS Pi to start? If so, great!

I guess another option is for one of us with a working image to write it to a file and host it somewhere temporarily? I would do that happily if my spare SD card hadn’t just failed!

Oh, and I wasn’t aiming to complain about any of this. I actually asked what we (the community) could do to help, as I would not dream of pointing the finger at ROOL.

I have just tried RetroPie. It must have had zillions of developer man hours compared to RISC OS Pi. But guess what? I got stick with two very simple issues. Another rough experience!

The 2GB image will work on a larger card with no problems.

I know that. I just don’t fancy being the one who has to explain to newbies that RISC OS is only going to use a portion of their SD card and that’s that.

It sounds like Chris has had a go at simplifying things. What is in update4? New firmware, ROM and HD4? And it can be unzipped on Windows or Mac OS X so you don’t need a working RISC OS Pi to start? If so, great!

No change is required to HD4 (as provided with the RC14 SD card image) to run a low vector rom on the Pi3. One or two bits of software in RC14 will not run on the Pi3 (some of which are part of the standard HardDisc4 image and have thus since been fixed) but RISC OS itself is OK. Otherwise it is all as stated.

In update4.zip is the following:

The update contains a low vector build of the latest ROM (29-Mar-2016) so that it will automatically switch speeds from idling to the nominal rated speed of the particular Pi model concerned (note: the model 1 does not switch speed).

It will work on the Raspberry Pi Zero, Compute Module, model 1, 2 and 3 A, A+, B and B+. It will support AX8872B-based USB to Ethernet adapters [such adapters are required on the Pi Zero to make an internet connection], which are not supported by the current RC14 download. Explicit clock settings in the file CONFIG/TXT are no longer required although an example is given to set the faster clock speed to 1000MHz vice 900MHz for the model 2.

It will update your ROM image to RISC OS 5.23 as at 29-Mar-2016 and the firmware to 29-Mar-2016. This build of RISC OS is a low processor vector build and so does not need the ZeroPain module.

Don’tcha just love it when something clicks and goes right – and you’re not sure what you did different? Well, one difference is that I’ve loaded RISC OS Pico rather than the whole nine yards. Whatever, at least it’s there and giving me a start screen. One more word of advice would be welcome though. Can I build on Pico until I have the full system? Or would I be better starting from scratch on a new MicroSD and hoping to repeat my success and get it that way? Thanks for the encouragement so far guys!