h2. Purchasing a board Firstly, you'll need to buy something with the OMAP processor on it, and [[How to get started with a BeagleBoard|some supporting peripherals]]. h2. Getting a ROM image and Boot application The first thing to do is obviously to get a ROM image. If you want to build one yourself, view the instructions on [[Cortex-A8 port source code|this page]]. If you want to use a prebuilt ROM image, you can download one for the BeagleBoard from "this page":/content/downloads/beagleboard or PandaBoard from "this page":/content/downloads/pandaboard. You may also want to download the "HardDisc4":/content/downloads/common 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! h2. Putting the ROM image onto an SD card 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 OMAP 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: * BeagleBoard-xM users will need suitable copies of x-loader and U-Boot. You will find suitable versions on the Linux SD card that came with your board; the 'mlo' file is x-loader, and the 'u-boot/bin' file is u-boot. Alternatively, you can download the latest copies of those files from following advice/links via the beagleboard.org website. ** On the "Beagle Board Diagnostic Tools and Procedure":http://code.google.com/p/beagleboard/wiki/BeagleBoardDiagnosticsNext page, under 'Preparing the flash on your BeagleBoard' there is a link stating where to acquire the individual MLO and u-boot.bin files. ** This page is "an XML page":http://beagleboard-validation.s3.amazonaws.com/deploy/201008201549/sd/list.html and therefore poses difficulties for current RISC OS browsers. ** However, the specific links can be used for the downloads and are (as at 4 November 2011): *** "MLO":http://beagleboard-validation.s3.amazonaws.com/deploy/201008201549/sd/MLO *** "u-boot.bin":http://beagleboard-validation.s3.amazonaws.com/deploy/201008201549/sd/u-boot.bin * TouchBook users will need suitable copies of "x-loader and U-Boot":http://www.alwaysinnovating.com/wiki/index.php/Booting#x-load_and_u-boot as well. You can either copy these off of the Linux SD card that came with the machine, or download new versions from the "Always Innovating website":http://www.alwaysinnovating.com/wiki/index.php/List_release_folder * TouchBook users will also need a copy of the 'mkimage' tool that is supplied with the "U-Boot":http://www.denx.de/wiki/U-Boot sources. RISC OS users can install the RISC OS port of mkimage that is "available from riscos.info":http://www.riscos.info/packages/CommandDetails.html#mkimage. Linux users may have to build the tool from source. * Pandora users may find it helpful to refer to "Running Linux from an SD card":http://pandorawiki.org/Running_Linux_from_an_SD_card If this is all a bit daunting, you can skip *all* these steps by "buying a pre-prepared":/content/sales/risc-os-panda-beagle card instead. h3(#create_riscos). Using SDCreate 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 SDCreate will overwrite any existing content. 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 occurring then it will likely result in a corrupt image. If you want to create an image, and save it as a file: * Select 'Create image' * Deselect 'Write image' * Select the right machine type * Drag the RISC OS ROM image to the 'ROM image' box * Drag the x-loader and U-Boot binaries into the x-loader and U-Boot boxes, if necessary * Drag your desired CMOS file into the 'CMOS file' box, if necessary * Click 'Run' If you want to create an image, and write it straight out to a card: * Select both 'Create image' and 'Write image' * Select the right machine type * Drag the RISC OS ROM image to the 'ROM image' box * Drag the x-loader and U-Boot binaries into the x-loader and U-Boot boxes, if necessary * Select the SCSI drive number which your SD card reader has appeared under * Drag your desired CMOS file into the 'CMOS file' box, if necessary * Click 'Run' If you want to write an existing SD image to an SD card: * Select 'Write image' * Deselect 'Create image' * Drag the image file to the 'SD image' box * Select the SCSI drive number which your SD card reader has appeared under * Drag your desired CMOS file into the 'CMOS file' box, if necessary * Click 'Run' That's it! If it all went well, you should now have a working SD card/image for use with your OMAP machine. h3(#create_nonriscos). Using Windows/Linux/Mac utilities for writing SD card images 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: * Windows - "Win32DiskImager":https://wiki.ubuntu.com/Win32DiskImager ** Make sure the file has a .img extension for Win32DiskImager to find it * Linux - "UNetbootin":http://unetbootin.sourceforge.net/ ** Or if you're feeling adventurous, just use 'dd' * Mac - "Etcher":https://www.balena.io/etcher/ ** Or if you're feeling adventurous, just use 'dd' h2(#usbdrive_setup). Putting the HardDisc4 image onto a USB drive Here's a brief guide of how to set up your OMAP board to boot from a USB drive instead: h3. If you have an existing RISC OS device with USB support # Format the USB device for use with RISC OS (e.g. RISC OS 5 users would use !HForm) # Extract the HardDisc4 components (e.g. by copying them from the ZIP download, or running the self extracting copy) h3. If you don't have an existing RISC OS device with USB support At the moment the only way to get around this problem is to get your OMAP machine (running RISC OS) to set up the boot sequence itself. This is somewhat a case of pulling yourself up by your own bootstraps, but the following should save you some time! # First off, make sure you have a FAT formatted USB device which is formatted to under 2GB in size. If you want, this can be the same device that you'll extract the boot sequence to, but it doesn't have to be. If you're using two different USB devices, ensure that they *don't* have the *same name*, e.g. name the one with the self-extracting archive on it 'INSTALLHD4'. # Copy the self-extracting "HardDisc4":https://www.riscosopen.org/content/downloads/other-zipfiles archive (under *Ancillary downloads*) onto the device # Also copy the InstallHD4 script onto the device. The InstallHD4 script should have been supplied with the OMAP ROM zipfile, or you can download the latest version from "here":https://www.riscosopen.org/viewer/view/~checkout~/apache/RiscOS/Utilities/Autobuild/ABRelease/Resources/OMAP3Dev/InstallHD4%2Cfd6?content-type=text%2Fplain # Plug the USB device into the OMAP machine and boot the machine into RISC OS (Making sure that the SD card you created earlier is inserted in the SD/microSD card slot!) #* If you _don't_ have the USB device connected, you'll be prompted to press Escape. This will take a while to be detected, so be patient. # At the RISC OS Supervisor *** prompt type @desktop@<br /><br />[[Riscosinstallation-tb-v1-01.png|Supervisor prompt:pic]]<br /><small>_Supervisor prompt_</small><br /><br /> # After a short wait, the splash screen is displayed<br /><br />[[Riscosinstallation-tb-v1-02.png|Splash screen:pic]]<br /><small>_Splash screen_</small><br /><br /> # This is followed by the desktop<br /><br />[[Riscosinstallation-tb-v1-03.png|Desktop:pic]]<br /><small>_Desktop_</small><br /><br /> # If you get a "Message from Desktop" stating "Machine startup has not completed successfully:" this can be ignored so click _Cancel_ # If help is not required for familiarisation with RISC OS, this can be disabled by <em>Select</em>ing the Help icon (_*i*_ to the right of the icon bar) to make it grey (_Select_ is the left mouse button, _Menu_ the middle button/scrollwheel, _Adjust_ the right button) # Click _Select_ on the SCSI disc icon to open its directory viewer<br /><br />[[Riscosinstallation-tb-v1-04.png|Directory viewer:pic]]<br /><small>_Directory viewer_</small><br /><br /> # Click Menu over the InstallHD4 script, navigate to *File 'InstallHD4'->Set type* and (in place of whatever is shown) type @fd6@ or @taskexec@ and press Enter<br /><br />[[Riscosinstallation-tb-v1-05.png|Changing the filetype:pic]]<br /><small>_Changing the filetype_</small><br /><br /> # If the HardDisc4 archive isn't named 'HardDisc4/util' then you'll need to rename it (Click Menu over the file, navigate to *File '...'->Rename* and enter @HardDisc4/util@) # Run the InstallHD4 script by double-clicking on it. # If you get an Error message stating "No Boot application has been run on startup. Some facilities may not be available or set up correctly." this can be ignored so click _Cancel_ # If everything went OK, you should be left with a window containing some instructions to follow, and a shortcut to !HForm on the pinboard in the bottom-left corner of the screen.<br /><br />[[Riscosinstallation-tb-v1-06.png|Results of executing the InstallHD4 script:pic]]<br /><small>_Results of executing the InstallHD4 script_</small><br /><br /> # Connecting the new USB boot device to format reveals its drive number on the icon bar #* *Note:* the same device can be reused if wished. If a *different* device is being used, the FAT formatted device used to get to this point can be safely disconnected, if desired # (Re)formatting of the device is undertaken by the single-tasking !HForm, executed by double-clicking on it with <em>Select</em><br /><br />[[Riscosinstallation-tb-v1-07.png|HForm:pic]]<br /><small>_HForm_</small><br /> #* When prompted about adding entries to the defect list, _'*A*' (no more changes)_ is required. Otherwise, the default settings should work just fine.<br /><br /> # When formatting is complete (or aborted by pressing _Escape_), the system will return to the desktop # Selecting all files in the RAM::RamDisc0.$.HardDisc4 directory viewer is done by clicking _Menu_ *Select all* within the viewer<br /><br />[[Riscosinstallation-tb-v1-08.png|Select all:pic]]<br /><small>_Select all_</small><br /><br /> # The extracted contents are copied to the USB boot device by <em>Select</em>ing one of the highlighted files and dragging the selection onto the iconbar drive icon for the newly formatted device<br /><br />[[Riscosinstallation-tb-v1-09.png|Commencing drag:pic]]<br /><small>_Commencing drag_</small><br /><br />[[Riscosinstallation-tb-v1-10.png|Dropping onto destination USB boot device icon:pic]]<br /><small><em>Dropping onto destination USB boot device icon</em></small><br /><br /> # File copying commences # This is accelerated by <em>Select</em>ing *Faster*<br /><br />[[Riscosinstallation-tb-v1-11.png|Commencing copying:pic]]<br /><small>_Commencing copying_</small><br /><br />[[Riscosinstallation-tb-v1-12.png|Selecting Faster:pic]]<br /><small><em>Selecting Faster</em></small><br /><br /> # When copying is complete (i.e. Copying files window disappears), the device is dismounted by clicking _Menu_ *Dismount* on its iconbar drive icon<br /><br />[[Riscosinstallation-tb-v1-13.png|Dismounting the USB boot device:pic]]<br /><small><em>Dismounting the USB boot device</em></small><br /><br /> # The device may be restarted by clicking _Menu_ *Shutdown* over the Task Manager "switcher" icon, followed by <em>Select</em>ing *Restart*<br /><br />[[Riscosinstallation-tb-v1-14.png|System shutdown:pic]]<br /><small>_System shutdown_</small><br /><br /> # The device will now boot from the newly installed boot sequence on the USB boot device<br /><br />[[Riscosinstallation-tb-v1-15.png|1024 x 600 desktop (example shown on the TouchBook after setting correct screen display):pic]]<br /><small>_1024 x 600 desktop (example shown on the TouchBook after setting correct screen display)_</small><br /><br />[[Riscosinstallation-tb-v1-15a.png|1024 x 600 desktop running NetSurf browser:pic]]<br /><small><em>1024 x 600 desktop running "NetSurf browser":ARMv7%20software%20compatibility%20list#networking</em></small>