Showing changes from revision #4 to #5:
Added | Removed | Changed
Please note these instructions will not work for the Raspberry Pi 4. When a Pi 4 build suitable for beginners is available, this page will be updated accordingly.
For most models of Raspberry Pi, you can use the “RISC OS Pi” SD card image available on the Downloads page.
If you have a Pi 3 model A+, use RISCNOOBS Lite OS will fit on a 2GB card. SD cards up to 32GB capacity can be used, but it may be worth checking the to download the software.known good cards list as there have been problems with a few cards. Be aware that some cards sold as Sandisk are counterfeit: if in doubt, buy from a reputable supplier.
Strictly The speaking, easiest there method is no to preparation use necessary, as the format information is contained in the image file. Any SD card of 2GB or greater capacity should be OK, however, it may be worth checking theknown good cards listNOOBS Lite as there have been problems with some cards. Incidentally, it has been reported recently that many cards sold as Sandisk are counterfeit, so if in doubt, buy from a reputable supplier.
Be sure to download NOOBS Lite – the process will not work if you use full NOOBS.
First, download a suitable SD card image:
Unpack the archive, then use a utility such as Win32DiskImager (Windows) or Etcher (Linux/macOS) to copy the image to the MicroSD card1.
1 RISC OS will only be able to use the space occupied by the .IMG file, so there is no advantage to using large-capacity cards.
Start with a blank formatted SD or SDHC card.
SystemDisc is part of the DiscTools suite, and is a general-purpose tool for managing the system software on modernRISC OS systems. SystemDisc allows you, easily and quickly, to initialise new SD cards for booting your RISC OS system, entirely from within RISC OS. It creates a two-partition SD card which can use all of the available space on your SD card.
Now You you will also need to copy download the ‘firmware’ files into !Boot.Loader where they can be seen by the Pi as it starts up (beforeRISCstable RPi ROM OS and is the started).HardDisc4 image.
Now SystemDisc download will the prompt HardDisc4 you image to and copy that onto the filecore ‘firmware’ partition. files You into will !Boot.Loader now where have they a can ‘cut be down’ seen version by of the recommended Raspberry Pi image as without it all starts the up extra (before software bundled with the “RISC OS Pi” is distribution. started).
Comprehensive instructions can be found here – there is little sense in recreating these directions here as they are not RISC OS specific.
Unpack the HardDisc4 archive and copy !Boot onto the FileCore partition. Do not delete the !Boot application already present on the card: simply copy the new !Boot on top of it. Once this has been done, copy the other directories to the FileCore partition.
Insert Remember to dismount the SD drive card before into unplugging the Raspberry SD Pi, card. and connect the other peripherals necessary. Power up the Pi, and you should see theRISC OS logo during the boot process, before being taken to the desktop.
On the Raspberry Pi, CMOS RAM settings are saved in a file called “CMOS”, but if you have been following the instructions in “Preparing the media manually” above, the file doesn’t exist yet. Press F12 and enter:
*SaveCMOS !Boot.Loader.CMOS
Insert the SD card into the SD slot of the Raspberry Pi and power on. RISC OS should now boot to the desktop.
Press On the Raspberry Pi,CMOS RAM settings are saved in a file called “CMOS”, but the file may not exist yet. From the RISC OS desktop, press F12 and enter:
*SaveCMOS !Boot.Loader.CMOS
Press RETURN twice again to return to the desktop.
The system is now ready for use. It is possible that the screen resolution will need changing to suit your needs, so please see the Beginners FAQ:Look and Feel
If the initial boot-up boot gets stuck at a blank screen (or subsequent a boot) “rainbow” fails, screen with no text) the first likely candidate is the SD card. Check it is seated correctly, check that the contacts in the card slot aren’t damaged in any way, clean it all up, and try again. If The this next fails, thing it may be that the SD card has become corrupt, and needs re-imaging. This is a good time to remind check all is users that of the importance of backups…all of the firmware files are present and correct. If you’re still having problems, it may be that the SD card has become corrupt, and needs re-imaging. This is a good time to remind all users of the importance of backups…
The basic approach is the same – create an SD card with the firmware and the RISC OS boot drive – but there is not yet a pre-built SD card image available so the manual option is the only one.
The basic approach is the same – create an SD card with the firmware and the RISC OS boot drive – but there is not yet a pre-built SD card image available so you will have to use the manual option. If you don’t have another RISC OS system to create the SD card, you can do it on the BeagleBoard/PandaBoard itself by following the instructions at Generic OMAP port setup information.