Commit 09389363 authored by Jeffrey Lee's avatar Jeffrey Lee
Browse files

Use SDCreate component instead of local copies of the tool

Detail:
  Resources/OMAP3Dev/release_autobuild,feb, Resources/OMAP4Dev/release_autobuild,feb - Take SDCreate from the <Install$Dir>.ABRelease folder instead of using local copies of the tool
  Resources/OMAP3Dev/!SDCreate, Resources/OMAP4Dev/!SDCreate - Deleted local copies of SDCreate
Admin:
  Tested with building and packaging OMAP3 ROM


Version 0.31. Tagged as 'ABRelease-0_31'
parent b70654fa
Set SDCreate$Dir <Obey$Dir>
IconSprites <SDCreate$Dir>.!Sprites
\ No newline at end of file
SDCreate
========
Introduction
------------
SDCreate is a utility designed to help people with the task of installing RISC OS ROM images onto SD cards, for use with the OMAP3 and OMAP4 ports of RISC OS. If you attempt to create an SD card manually then there are many places where things can go wrong, either due to user error or operating system quirks. But if you use SDCreate to create the image for you then you can (almost) guarantee that it will boot without any trouble.
Requirements
------------
Images can be created on almost any RISC OS computer with >32MB of spare disc space. You will need at least version 1.28 of the FrontEnd module and version 1.52 of DDEUtils. RISC OS 5 users can find up-to-date versions of these modules in the HardDisc4 image available in the downloads section of the RISC OS Open website. Users of 26bit machines can find the modules in the "System resources" download.
http://www.riscosopen.org/content/downloads/other-zipfiles
If you want to use SDCreate to write the image to an SD card, then you'll need to be using a RISC OS 5 machine with a USB card reader and the USB mass storage drivers (SCSISoftUSB).
Alternatively, you can copy the SD card image to a Windows/Linux/Mac/etc. PC and write the image to an SD card using any number of the free utilities that are available for those platforms (see the 'Utilities for other platforms' section, below)
Before you use SDCreate to create an SD card image, 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 extract them from the demo images available to download from the CircuitCo website:
http://circuitco.com/support/index.php?title=Circuitco_Support_Wiki
* TouchBook users will need suitable copies of x-loader 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.
* TouchBook users will also need to install the RISC OS port of mkimage, available from riscos.info:
http://www.riscos.info/packages/CommandDetails.html#Mkimage
Usage
-----
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 which writes images to SD 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 then it will likely result in a corrupt image.
******** WARNING *******
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.
CMOS files
----------
RISC OS stores a number of non volatile settings in what is often referred to as CMOS memory. Most notably, these are all the configuration settings such as the keyboard repeat rate and the drive to boot from.
From RISC OS 5.18 onwards the OMAP3 HAL will try to find CMOS memory mounted on a carrier board plugged into the otherwise unused 14 pin JTAG connector.
If that is not found to be present then an attempt will be made to find a valid CMOS image loaded into volatile memory by the boot process, though any settings will be forgotten when powered down - it is recommended to obtain a CMOS carrier board from your supplier for full read/write capability.
If that is also not found to be present (or is corrupt) the defaults in the kernel will be used instead, so the machine will still boot whether the hardware is present or not and whether a CMOS file is present or not.
The default filename is simply 'cmos' but can be changed to anything you desire as long as the corresponding boot script is ammended (see 'The Techie Bit'
later).
The behaviour of SDCreate with regards to CMOS files is as follows:
* When creating an image (i.e. the 'Create image' box is ticked), you can place a copy of a specific CMOS file into the image by entering the filename in the 'CMOS file' box.
* If you don't specify a file, a blank CMOS file will be placed in the image.
* If you're writing an existing image to a card (i.e. 'Create image' isn't ticked), then by default the CMOS file held in the image will be used.
* However you can override this behaviour by entering a filename in the 'CMOS file' box. This CMOS file will then be used instead of the one held in the image.
The format of CMOS file used is compatible with that used by the *LoadCMOS/*SaveCMOS commands, or the load/save CMOS option available within Configure. Note that you should obviously only use CMOS files that have been saved by an OMAP3 machine; a file from a RiscPC, Iyonix, etc. isn't guaranteed to work correctly.
Additional usage notes
----------------------
Owners of old BeagleBoards, with version of U-Boot before 2009.01, may find that the 'BeagleBoard' option produces an SD card that won't boot on their machine. This can be solved in one of three ways:
* Edit the !SDCreate.Desc file so that the boot script is named 'RESET/SCR' instead of 'BOOT/SCR'. You need to change the "icn 8 maps_to ..." line (line 31)
* Reflash your NAND with the latest x-loader & U-Boot. See the beagleboard.org website for details.
* Use the BeagleBoard-xM machine type (with either the BeagleBoard or BeagleBoard-xM x-loader & U-Boot; both should be compatible with the non-xM boards).
* Note however that this may introduce an additional problem, where the machine hangs on boot, due to an old, incompatible version of x-loader in NAND being used with the new version of U-Boot on the SD card. To fix this you can find an older version of U-Boot that works, or reflash your board, or always boot while holding down the User button.
Utilities for other platforms
-----------------------------
If you don't own a working RISC OS machine and therefore can't use SDCreate to create an SD card image, then 'The techie bit' section below has information as to what files SDCreate places into the images. This should allow you to create a working card manually.
If you've created an image file using SDCreate, but can't use SDCreate itself to write the image to a card, then you can use one of the following Windows/Linux/Mac utilities to write the image for you:
* Windows - Win32DiskImager - https://wiki.ubuntu.com/Win32DiskImager
- Just 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 - http://meego.com/devices/netbook/installing-meego-your-netbook
- I'm not aware of any user-friendly utilities to do this on a Mac OS X machine, but the above instructions for writing a MeeGo Linux disc image onto a USB drive can easily be adapted for writing the SD card images created by SDCreate.
The techie bit
--------------
SDCreate creates SD card images in the following manner:
* The file !SDCreate.blank is a blank, 32MB FAT16 disc image created under Windows and then copied off of the SD card using 'dd' under Linux
* This file was then squashed using !Squash to cut down the size of the program.
* So one of the first things SDCreate does is to unsquash the image. If the image is being written straight out to the SD card then it will be unsquashed directly to the card using the SCSIFS_DiscOp SWIs. Otherwise, it will be unsquashed to a file. This file will then have its filetype set to 'DOSDisc', allowing the FAT image to be used as an image file with DOSFS.
* SDCreate then copies a series of files into the image. The exact files copied will depend upon which machine type you are using:
BeagleBoard (non-xM):
BOOT/SCR <- The BeagleBoard boot script from !SDCreate.scripts
UENV/TXT <- U-Boot environment file from !SDCreate.scripts
RISCOS <- Your RISC OS ROM image
CMOS <- Your CMOS settings
BeagleBoard-xM:
MLO <- The x-loader binary
U-BOOT/BIN <- The U-Boot binary
BOOT/SCR <- The BeagleBoard boot script from !SDCreate.scripts
UENV/TXT <- U-Boot environment file from !SDCreate.scripts
RISCOS <- Your RISC OS ROM image
CMOS <- Your CMOS settings
DevKit8000:
BOOT/SCR <- The DevKit8000 boot script from !SDCreate.scripts
RISCOS <- Your RISC OS ROM image
CMOS <- Your CMOS settings
IGEPv2:
BOOT/INI <- The IGEPv2 boot script from !SDCreate.scripts
RISCOS <- Your RISC OS ROM image
CMOS <- Your CMOS settings
Touch Book:
MLO <- The x-loader binary
U-BOOT/BIN <- The U-Boot binary
UIMAGE <- Your RISC OS ROM image, packaged as a U-Boot uImage
CMOS <- Your CMOS settings
Pandora:
BOOT/SCR <- The Pandora boot script from !SDCreate.scripts
RISCOS <- Your RISC OS ROM image
CMOS <- Your CMOS settings
PandaBoard:
MLO <- The x-loader binary
U-BOOT/BIN <- The U-Boot binary
BOOT/SCR <- The PandaBoard boot script from !SDCreate.scripts
RISCOS <- Your RISC OS ROM image
CMOS <- Your CMOS settings
* The rules for which files get used on which machine type are in the FrontEnd description file (!SDCreate.Desc). I wouldn't advise trying to decipher it, though!
* If you want to examine the contents of an image file, just set its filetype to 'DOSDisc' and double-click. (The files get typed to Data since the FrontEnd module doesn't consider image files to be valid tool output!)
* The Touch Book uImage file is created using the following command:
mkimage -A arm -O linux -T kernel -C none -a 0x81000000 -e 0x81000064 -n "RISC OS" -d <infile> <outfile>
The even more techie bit
------------------------
The human-readable source to the boot scripts is available in !SDCreate.scripts.source. You will also find there the 'convert' script script, which uses mkimage to convert the scripts to the binary format used by U-Boot.
Each boot script will enter the ROM image at a different address; this is how RISC OS works out what machine type it's running on. The full list of (current) ROM image entry points is given below:
BeagleBoard ROM start + &00000000
DevKit8000 ROM start + &00000004
IGEPv2 ROM start + &00000008
Pandora ROM start + &0000000C
Touch Book ROM start + &00000010
PandaBoard ROM start + &00000000
There is also an extra entry point at offset &00000064, which should be used when the ROM image is packed as a uImage. This entry point allows RISC OS to detect the machine type automatically, via the machine ID number that is passed to it by U-Boot. The uImage format also has a few other advantages (checksums, argument strings), so in the future it may be adopted for all machine types instead of just the Touch Book (and the only reason it's used on the Touch Book is because the default Touch Book version of U-Boot doesn't seem to look for boot scripts).
The U-Boot environment file (uenv.txt) is a file that new versions of U-Boot use to get their environment variables. Although it's supposedly an optional thing, the BeagleBoard-xM demo images have had their default environments changed such that the regular boot.scr is no longer used, and uenv.txt is the only (easy) method to boot RISC OS.
History
-------
V1.20 - 2012/2/12
* Added PandaBoard support [Willi Theiss]
* Fix interactive help text
* Relaxed ROM size constraints and changed to using a 32MB FAT16 partition, to allow for both bigger ROMs and compressed ROMs
* Change 'x-loader' to 'x-loader/MLO' in the templates file to help make it clear what's required
V1.16 - 2012/1/7
* Scripts adjusted to load the CMOS file with 'fatload' [Rob Sprowson]
V1.15 - 2011/5/25
* Added a uenv.txt file to provide compatability with the latest BeagleBoard/BeagleBoard-xM versions of U-Boot
V1.10 - 2011/1/22
* Added support for adding CMOS files to images
V1.02b - 2010/11/14
* Changed !Run file to RMEnsure FrontEnd 1.28 after receiving reports of 1.16 not working
V1.02 - 2010/10/17
* Fixed a bug with the step that checks for successful uImage creation
* Corrected all filenames to be in caps, so TouchBook/xM cards actually boot!
V1.01 - 2010/10/12
* Tweaked a couple of bits and added Chris Wraight's icon
V1.00 - 2010/10/7
* First release of the GUI version
Other
-----
SDCreate is public domain.
SDCreate was written by Jeffrey Lee, me@phlamethrower.co.uk. SDCreate icon created by Chris Wraight.
http://www.phlamethrower.co.uk/riscos/sdcreate.php
Run <Obey$Dir>.!Boot
RMEnsure FrontEnd 0.00 Run System:Modules.Frontend
RMEnsure FrontEnd 1.28 Error You need version 1.28 of the FrontEnd module to run !SDCreate
RMEnsure DDEUtils 0.00 Run System:Modules.DDEUtils
RMEnsure DDEUtils 1.52 Error You need version 1.52 of the DDEUtils module to run !SDCreate
WimpSlot -Min 128k -Max 128k
FrontEnd_Start -app SDCreate -desc <SDCreate$Dir>.Desc
# This is a description of the WIMP interface for SDCreate
tool_details_start
name "SDCreate";
command_is "<SDCreate$Dir>.SDCreate";
version "1.20";
wimpslot 256k;
has_extended_cmdline;
tool_details_end
metaoptions_start
has_auto_save "SDImage" from icn 4;
has_text_window;
metaoptions_end
fileoutput_start
output_option_is "file";
output_dft_string "SDImage";
output_dft_is produces_output;
fileoutput_end
dbox_start
icons_start
icn 4 maps_to string;
icn 5 maps_to "MLO " string;
icn 6 maps_to "U-BOOT/BIN " string;
icn 8 maps_to "BOOT/SCR <SDCreate$Dir>.scripts.beagleboard/scr UENV/TXT <SDCreate$Dir>.scripts.uenv/txt RISCOS";
icn 9 maps_to "BOOT/SCR <SDCreate$Dir>.scripts.beagleboard/scr UENV/TXT <SDCreate$Dir>.scripts.uenv/txt RISCOS";
icn 10 maps_to "BOOT/SCR <SDCreate$Dir>.scripts.devkit8000/scr RISCOS";
icn 11 maps_to "BOOT/INI <SDCreate$Dir>.scripts.igepv2/ini RISCOS";
icn 12 maps_to "UIMAGE";
icn 13 maps_to "BOOT/SCR <SDCreate$Dir>.scripts.pandora/scr RISCOS";
icn 28 maps_to "BOOT/SCR <SDCreate$Dir>.scripts.pandaboard/scr RISCOS";
icn 0 maps_to "";
icn 14 maps_to "";
icn 15 maps_to "";
icn 16 on maps_to "disc " followed_by icn 17 produces_no_output;
icn 17 on maps_to "";
icn 18 decreases icn 17 min 0;
icn 19 increases icn 17 max 7;
icn 21 on maps_to "" produces_output;
icn 21 off maps_to "" produces_no_output;
icn 22 maps_to "";
icn 23 maps_to "";
icn 24 maps_to "image " string;
icn 25 maps_to "";
icn 20 maps_to "";
icn 27 maps_to "CMOS " string;
icons_end
defaults
icn 21 on,
icn 8 on,
icn 16 on;
imports_start
drag_to icn 4 inserts icn 4;
drag_to icn 5 inserts icn 5;
drag_to icn 6 inserts icn 6;
drag_to icn 24 inserts icn 24;
drag_to icn 27 inserts icn 27;
imports_end
dbox_end
rules_start
# Enable/disable top-level 'create image' icons
icn 21 off deselects icn 8, icn 9, icn 10, icn 11, icn 12, icn 13, icn 28;
icn 21 off excludes icn 8, icn 9, icn 10, icn 11, icn 12, icn 13, icn 28, icn 4, icn 22, icn 20;
icn 21 on includes icn 8, icn 9, icn 10, icn 11, icn 12, icn 13, icn 28, icn 4, icn 22, icn 20;
# Enable/disable 'SD image' icons
icn 16 on includes icn 23, icn 24;
icn 16 off excludes icn 23, icn 24;
icn 21 on excludes icn 23, icn 24;
icn 21 off includes icn 23, icn 24;
# Machine type ESG
icn 8 deselects icn 9, icn 10, icn 11, icn 12, icn 13, icn 28;
icn 9 deselects icn 8, icn 10, icn 11, icn 12, icn 13, icn 28;
icn 10 deselects icn 8, icn 9, icn 11, icn 12, icn 13, icn 28;
icn 11 deselects icn 8, icn 9, icn 10, icn 12, icn 13, icn 28;
icn 12 deselects icn 8, icn 9, icn 10, icn 11, icn 13, icn 28;
icn 13 deselects icn 8, icn 9, icn 10, icn 11, icn 12, icn 28;
icn 28 deselects icn 8, icn 9, icn 10, icn 11, icn 12, icn 13;
# Machine type -> ROM/x-loader/U-Boot mapping (disable stuff)
icn 9 off excludes icn 5, icn 6, icn 14, icn 15;
icn 12 off excludes icn 5, icn 6, icn 14, icn 15;
icn 8 on excludes icn 5, icn 6, icn 14, icn 15;
icn 10 on excludes icn 5, icn 6, icn 14, icn 15;
icn 11 on excludes icn 5, icn 6, icn 14, icn 15;
icn 13 on excludes icn 5, icn 6, icn 14, icn 15;
icn 8 off excludes icn 5, icn 6, icn 14, icn 15;
icn 10 off excludes icn 5, icn 6, icn 14, icn 15;
icn 11 off excludes icn 5, icn 6, icn 14, icn 15;
icn 13 off excludes icn 5, icn 6, icn 14, icn 15;
icn 28 off excludes icn 5, icn 6, icn 14, icn 15;
icn 28 on excludes icn 5, icn 6, icn 14, icn 15;
# Machine type -> ROM/x-loader/U-Boot mapping (enable stuff)
icn 9 on includes icn 5, icn 6, icn 14, icn 15;
icn 12 on includes icn 5, icn 6, icn 14, icn 15;
icn 28 on includes icn 5, icn 6, icn 14, icn 15;
# Enable/disable SCSI drive icons
icn 16 off excludes icn 17, icn 18, icn 19, icn 25;
icn 16 on includes icn 17, icn 18, icn 19, icn 25;
# Enable/disable Run button
# I have no idea how this works
icn 21 on excludes icn 0;
icn 21 off includes icn 0;
icn 16 on includes icn 0;
icn 16 off excludes icn 0;
icn 8 off excludes icn 0, icn 0;
icn 9 off excludes icn 0, icn 0;
icn 10 off excludes icn 0, icn 0;
icn 11 off excludes icn 0, icn 0;
icn 12 off excludes icn 0, icn 0;
icn 13 off excludes icn 0, icn 0;
icn 28 off excludes icn 0, icn 0;
icn 8 on includes icn 0, icn 0;
icn 9 on includes icn 0, icn 0;
icn 10 on includes icn 0, icn 0;
icn 11 on includes icn 0, icn 0;
icn 12 on includes icn 0, icn 0;
icn 13 on includes icn 0, icn 0;
icn 28 on includes icn 0, icn 0;
rules_end
# This boils down to one of two formats:
# [CMOS <name>] (disc <id> | file <name>) [MLO <name>] [U-BOOT/BIN <name>] ([BOOT/SCR|BOOT/INI] <name> RISCOS <name> | UIMAGE <name>)
# [CMOS <name>] disc <id> image <name>
order_is
icn 27, icn 16, icn 24, output, icn 5, icn 6, icn 8, icn 9, icn 10, icn 11, icn 12, icn 13, icn 28, icn 4;
# First section of messages file is general to all applications
# Third parties can change FEinterr1 to their company name so that
# internal error messages will come up "Please report to <your name>"
FECmd1:String too long (limit %d current %d addition %d)
FECmd2:You cannot change the command used to run this tool
FECmd3:Output
FECmd4:ReRun
FECmd5:OK
FECmd6:Run
FEdbox1:Can't import from other applications when invoked from !Make
FEdbox2:Unable to start up -- not enough space (or too many windows)
FEinterr1:Jeffrey Lee <me@phlamethrower.co.uk>
FEinterr2:%s: internal error: %s (%s/%d)
FEinterr3:Please report this error to %s
FEmem1:Out of memory, on request for %d bytes
FEmenu1:>Info,Save options,Options,Help,Quit
FEmenu2:Options
FEmenu3:Auto Run,Auto Save,Display
FEmenu4:Display
FEmenu5:Text,Summary
FEmenu6:>Command line
FEmenu7:>Info,>Cmd Line,>Save,Abort,Pause,Continue
FEmenu8:>Info,>Cmd Line,>Save
FEmenus9:Task(s) active: are you sure you want to quit?
FEmsg1:Wimp$Scrap must be set to do this transfer
FEmsg2:Invalid DataSave (filename != Wimp$Scrap)
FEoutput1:No more memory for output display - requesting %d bytes
FEoutput2:Running
FEoutput3:Aborted
FEoutput4:Paused
FEoutput5:Completed
FEoutput6:Task active: abort and close?
FEoutput7:Output file produced but not saved and will be lost. OK to continue?
FEoutput8:Continue
FEoutput9:Pause
FEsaveas1:Directories can only be saved to a filer viewer
FEsaveas2:To save, drag the icon to a directory viewer.
FEtask1:Task window not active
FEtask2:Application needs at least %dK to start up
FEtask3:Command line too long for task window module
utils1:Field is too long
utils2:Save failed %s -> %s
FEOpts1:Unable to write choices file %s
# General help messages
CMDLINE:This dialogue box displays the command line equivalent|Mof dialogue box and menu settings.|M
CMDLINE1:This is the command line equivalent of dialogue box and menu settings.
CMDLINE0:Click here to Run/ReRun the tool or to send options back to !Make.
SETUP:This dialogue box sets commonly used options.
SETUP0:Click here to run the application with the current options.
SETUP1:Click here to return to the previous set of options for this application.
SUMMARY:This dialogue box gives a summary of the command which has been run|Mor is running.
SUMMARY1:This is the icon for this application.
SUMMARY2:Click here to abort a running task.
SUMMARY3:Click here to continue a paused task.
SUMMARY4:This gives the number of lines produced by this task.
SUMMARY5:This gives the time at which a task was run.
SAVE:This dialogue box is used to save the file output of a command.
SAVE0:Click here to save the file output.
SAVE2:Filename for output appears here.
SAVE3:Drag this icon to save file output.
# Tool-specific messages follow here
#
# a = 10
# b = 11
# c = 12
# d = 13
# e = 14
# f = 15
# g = 16
# h = 17
# i = 18
# j = 19
# k = 20
# l = 21
# m = 22
#
SETUP4:Enter the name of the RISC OS ROM image, or drag it to this icon.
SETUP5:Enter the name of the version of x-loader for your machine, or drag it to this icon.
SETUP6:Enter the name of the version of U-Boot for your machine, or drag it to this icon.
SETUP8:Select this option to create an SD card image for non-xM BeagleBoards.
SETUP9:Select this option to create an SD card image for the BeagleBoard-xM.
SETUPa:Select this option to create an SD card image for the DevKit8000.
SETUPb:Select this option to create an SD card image for the IGEPv2.
SETUPc:Select this option to create an SD card image for the Touch Book.
SETUPd:Select this option to create an SD card image for the Pandora.
SETUPg:Select this option to write an image to an SD card.
SETUPh:Enter the target SCSI drive number here.
SETUPl:Select this option to create an image.
SETUPo:Enter the name of the SD image to load, or drag it to this icon.
SETUPs:Select this option to create an SD card image for the PandaBoard
fatload mmc 0:1 0x4020F000 cmos
fatload mmc 0:1 0x81000000 riscos
go 0x81000000
mkimage -A arm -O u-boot -T script -C none -n "RISC OS BeagleBoard boot script" -d <Obey$Dir>.beagle <Obey$Dir>.^.BeagleBoard/scr
mkimage -A arm -O u-boot -T script -C none -n "RISC OS DevKit8000 boot script" -d <Obey$Dir>.devkit <Obey$Dir>.^.DevKit8000/scr
mkimage -A arm -O u-boot -T script -C none -n "RISC OS IGEPv2 boot script" -d <Obey$Dir>.igep <Obey$Dir>.^.IGEPv2/ini
mkimage -A arm -O u-boot -T script -C none -n "RISC OS Pandora boot script" -d <Obey$Dir>.pandora <Obey$Dir>.^.Pandora/scr
mkimage -A arm -O u-boot -T script -C none -n "RISC OS PandaBoard boot script" -d <Obey$Dir>.panda <Obey$Dir>.^.PandaBoard/scr
fatload mmc 0:1 0x4020F000 cmos
fatload mmc 0:1 0x81000000 riscos
go 0x81000004
fatload mmc 0:1 0x4020F000 cmos
fatload mmc 0:1 0x81000000 riscos
go 0x81000008
fatload mmc 0:1 0x81000000 riscos
go 0x81000000
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment