Commit b70654fa authored by Robert Sprowson's avatar Robert Sprowson
Browse files

Import of !SDCreate 1.20 from Jeffrey Lee.

Version 0.30. Tagged as 'ABRelease-0_30'
parent b5b491c0
......@@ -5,14 +5,14 @@ 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 port 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.
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 >8MB of spare disc space. You will need at least version 1.28 of the FrontEnd module and version 1.52 of DDEUtils. Up-to-date versions of these modules can be found in the !System archive available for download from the RISC OS Open website:
http://www.riscosopen.org/content/downloads/boot-zipfiles
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).
......@@ -71,7 +71,7 @@ If you want to write an existing SD image to an SD card:
* Click 'Run'
That's it! If it all went well, you should now have a working SD card/image for use with your OMAP3 machine.
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
......@@ -104,7 +104,7 @@ Owners of old BeagleBoards, with version of U-Boot before 2009.01, may find that
* 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. The only way to avoid this is to find an older version of U-Boot that works, or reflash your board, or always boot while holding down the User button.
* 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
......@@ -127,17 +127,7 @@ The techie bit
SDCreate creates SD card images in the following manner:
* The file !SDCreate.blank is a blank, 8MB FAT12 disc image created under Linux using the following script:
#!/bin/bash
dd if=/dev/zero of=BlankImg bs=8225280 count=1
sfdisk -C 1 -H 255 -S 63 -D BlankImg <<EOF
,,0x01,*
EOF
sudo losetup -v -o 32256 /dev/loop0 BlankImg
sudo mkfs.vfat /dev/loop0 -n "RISC OS" -F 12
sudo losetup -d /dev/loop0
* 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:
......@@ -177,6 +167,13 @@ SDCreate creates SD card images in the following manner:
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:
......@@ -197,6 +194,8 @@ 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.
......@@ -205,8 +204,13 @@ The U-Boot environment file (uenv.txt) is a file that new versions of U-Boot use
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'
* 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
......
......@@ -3,7 +3,7 @@
tool_details_start
name "SDCreate";
command_is "<SDCreate$Dir>.SDCreate";
version "1.16";
version "1.20";
wimpslot 256k;
has_extended_cmdline;
tool_details_end
......@@ -34,6 +34,7 @@ dbox_start
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 "";
......@@ -71,9 +72,9 @@ 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 21 off excludes icn 8, icn 9, icn 10, icn 11, icn 12, icn 13, icn 4, icn 22, icn 20;
icn 21 on includes icn 8, icn 9, icn 10, icn 11, icn 12, icn 13, icn 4, icn 22, icn 20;
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;
......@@ -82,12 +83,13 @@ rules_start
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 9 deselects icn 8, icn 10, icn 11, icn 12, icn 13;
icn 10 deselects icn 8, icn 9, icn 11, icn 12, icn 13;
icn 11 deselects icn 8, icn 9, icn 10, icn 12, icn 13;
icn 12 deselects icn 8, icn 9, icn 10, icn 11, icn 13;
icn 13 deselects icn 8, icn 9, icn 10, icn 11, icn 12;
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;
......@@ -100,10 +102,13 @@ rules_start
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;
......@@ -116,19 +121,21 @@ rules_start
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
......@@ -136,4 +143,4 @@ rules_end
# [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 4;
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;
......@@ -86,11 +86,12 @@ SETUP5:Enter the name of the version of x-loader for your machine, or drag it to
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.
SETUP10:Select this option to create an SD card image for the DevKit8000.
SETUP11:Select this option to create an SD card image for the IGEPv2.
SETUP12:Select this option to create an SD card image for the Touch Book.
SETUP13:Select this option to create an SD card image for the Pandora.
SETUP16:Select this option to write an image to an SD card.
SETUP17:Enter the target SCSI drive number here.
SETUP21:Select this option to create an image.
SETUP24:Enter the name of the SD image to load, or drag it to this icon.
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
......@@ -2,3 +2,4 @@ mkimage -A arm -O u-boot -T script -C none -n "RISC OS BeagleBoard boot script"
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 0x81000000 riscos
go 0x81000000
......@@ -5,14 +5,14 @@ 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 port 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.
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 >8MB of spare disc space. You will need at least version 1.28 of the FrontEnd module and version 1.52 of DDEUtils. Up-to-date versions of these modules can be found in the !System archive available for download from the RISC OS Open website:
http://www.riscosopen.org/content/downloads/boot-zipfiles
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).
......@@ -71,16 +71,25 @@ If you want to write an existing SD image to an SD card:
* Click 'Run'
That's it! If it all went well, you should now have a working SD card/image for use with your OMAP3 machine.
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
----------
Since OMAP3 machines lack any real CMOS RAM, the OMAP3 port of RISC OS uses a file stored on the SD card to emulate CMOS RAM. Therefore when you use SDCreate to install a new ROM image you must be careful not to overwrite the CMOS file, otherwise the settings held in CMOS will be restored to default. The behaviour of SDCreate with regards to CMOS files is as follows:
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. This file acts as a placeholder to ensure that CMOS settings can be saved back to the card once the SD/MMC driver gains write support.
* 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.
......@@ -95,7 +104,7 @@ Owners of old BeagleBoards, with version of U-Boot before 2009.01, may find that
* 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. The only way to avoid this is to find an older version of U-Boot that works, or reflash your board, or always boot while holding down the User button.
* 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
......@@ -118,17 +127,7 @@ The techie bit
SDCreate creates SD card images in the following manner:
* The file !SDCreate.blank is a blank, 8MB FAT12 disc image created under Linux using the following script:
#!/bin/bash
dd if=/dev/zero of=BlankImg bs=8225280 count=1
sfdisk -C 1 -H 255 -S 63 -D BlankImg <<EOF
,,0x01,*
EOF
sudo losetup -v -o 32256 /dev/loop0 BlankImg
sudo mkfs.vfat /dev/loop0 -n "RISC OS" -F 12
sudo losetup -d /dev/loop0
* 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:
......@@ -168,6 +167,13 @@ SDCreate creates SD card images in the following manner:
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:
......@@ -188,6 +194,8 @@ 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.
......@@ -196,6 +204,13 @@ The U-Boot environment file (uenv.txt) is a file that new versions of U-Boot use
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
......
......@@ -3,7 +3,7 @@
tool_details_start
name "SDCreate";
command_is "<SDCreate$Dir>.SDCreate";
version "1.15";
version "1.20";
wimpslot 256k;
has_extended_cmdline;
tool_details_end
......@@ -34,6 +34,7 @@ dbox_start
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 "";
......@@ -71,9 +72,9 @@ 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 21 off excludes icn 8, icn 9, icn 10, icn 11, icn 12, icn 13, icn 4, icn 22, icn 20;
icn 21 on includes icn 8, icn 9, icn 10, icn 11, icn 12, icn 13, icn 4, icn 22, icn 20;
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;
......@@ -82,12 +83,13 @@ rules_start
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 9 deselects icn 8, icn 10, icn 11, icn 12, icn 13;
icn 10 deselects icn 8, icn 9, icn 11, icn 12, icn 13;
icn 11 deselects icn 8, icn 9, icn 10, icn 12, icn 13;
icn 12 deselects icn 8, icn 9, icn 10, icn 11, icn 13;
icn 13 deselects icn 8, icn 9, icn 10, icn 11, icn 12;
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;
......@@ -100,10 +102,13 @@ rules_start
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;
......@@ -116,19 +121,21 @@ rules_start
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
......@@ -136,4 +143,4 @@ rules_end
# [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 4;
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;
......@@ -86,11 +86,12 @@ SETUP5:Enter the name of the version of x-loader for your machine, or drag it to
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.
SETUP10:Select this option to create an SD card image for the DevKit8000.
SETUP11:Select this option to create an SD card image for the IGEPv2.
SETUP12:Select this option to create an SD card image for the Touch Book.
SETUP13:Select this option to create an SD card image for the Pandora.
SETUP16:Select this option to write an image to an SD card.
SETUP17:Enter the target SCSI drive number here.
SETUP21:Select this option to create an image.
SETUP24:Enter the name of the SD image to load, or drag it to this icon.
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
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