Showing changes from revision #43 to #44:
Added | Removed | Changed
Firstly, you’ll need to buy something with the OMAP processor on it, and some supporting peripherals.
The first thing to do is obviously to get a ROM image. If you want to build one yourself, view the instructions on this page. If you want to use a prebuilt ROM image, you can download one for the BeagleBoard from this page or PandaBoard from this page.
You may also want to download the HardDisc4 archive which contains the RISC OS 5 !Boot sequence and other utilities. Note that there are two versions available – a self-extracting version and a ZIP version. Only choose the ZIP version if you have a working RISC OS machine which you can use to extract the archive onto a USB device!
( Attempting to prepare an SD card manually can often result in failure, either due to user error or operating system quirks. The easiest way to solve this problem is to use the SDCreate utility, a copy of which is supplied with everyNote:OMAP To prepare a Linux/ROM image distributed by ROOL. Even if you don’t have a RISC OS dual OS boot, machine follow on which to run SDCreate, you’ll still want a copy of the app, as it contains a description of how SD cards are prepared, and copies of the required U-Boot scripts.these instructions.)
Attempting to prepare an SD card manually can often result in failure, either due to user error or operating system quirks. The easiest way to solve this problem is to use the SDCreate utility, a copy of which is supplied with every OMAP3 ROM image distributed by ROOL. Even if you don’t have a RISC OS machine on which to run SDCreate, you’ll still want a copy of the app, as it contains a description of how SD cards are prepared, and copies of the required U-Boot scripts.
Before preparing your SD card, you may need to track down some extra files/software:
If this is all a bit daunting, you can skip all these steps by buying a pre-prepared card instead.
The SDCreate main window is split into two sections – ‘Create image’ and ‘Write image’. Depending on which options are selected the ‘Run’ button at the bottom may or may not be greyed out.
WARNING
The code SDCreate which will writes overwrite images any to existing SD content. cards hasn’t received thorough testing, and doesn’t ask for confirmation before beginning the write operation. So if you’ve selected the wrong drive you will lose all your data on that drive, and if you try interacting with the drive while the write is occuring occurring then it will likely result in a corrupt image.
WARNING
If you want to create an image, and save it as a file:
If you want to create an image, and write it straight out to a card:
If you want to write an existing SD image to an SD card:
That’s it! If it all went well, you should now have a working SD card/image for use with your OMAP3 machine.OMAP machine.
If you’re able to use SDCreate to create an image file, but are unable to use it to actually write the image to a card, then you can use any number of Windows/Linux/Mac utilities to do the job for you:
If you’re unable or unwilling to use SDCreate to create an image for you, then you can always create one manually. See the SDCreate !Help file for information about the SD card structure and how booting works, or alternatively this archived copy of an earlier version of this page, which contains information about a variety of different boot methods.
The Here’s OMAP3 a port brief guide of how to set up your RISC OMAP OS board doesn’t yet contain a suitable driver to allow boot from aRISC OS to interact with the SD card slot. So your !Boot sequence must be placed on a USB drive instead. instead: Here’s a brief guide of how to set up the drive:
At the moment the only way to get around this problem is to get your OMAP3 machine (runningOMAP machine (running RISC OS) to set up the boot sequence itself. Unfortunately This is somewhat a couple case of bugs pulling and yourself limitations up in by your own bootstraps, but the following should save you some time!RISC OS mean that this is currently slightly trickier than it could be, but the following should save you some time!
desktop
fd6
or taskexec
and press EnterHardDisc4/util
)