Commit 01df2f71 authored by Jeffrey Lee's avatar Jeffrey Lee
Browse files

Update SDCreate to V1.10. Add note about CMOS RAM.

Detail:
  Resources/OMAP3Dev/ReadMe.txt - Added a note about how the OMAP port handles CMOS RAM
  Resources/OMAP3Dev/!SDCreate/!Help, Desc, SDCreate,ffb, Templates,fec - Updated SDCreate to V1.10, which supports placing CMOS files into the SD images
Admin:
  New version of SDCreate tested on Iyonix; resulting images tested on BeagleBoard.


Version 0.17. Tagged as 'ABRelease-0_17'
parent 38639076
......@@ -47,6 +47,7 @@ If you want to create an image, and save it as a file:
* 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:
......@@ -56,6 +57,7 @@ If you want to create an image, and write it straight out to a card:
* 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:
......@@ -64,12 +66,26 @@ If you want to write an existing SD image to an SD card:
* 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 OMAP3 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:
* 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'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
----------------------
......@@ -119,29 +135,35 @@ SDCreate creates SD card images in the following manner:
BeagleBoard (non-xM):
BOOT/SCR <- The BeagleBoard boot script 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
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
* 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!)
......@@ -169,6 +191,8 @@ There is also an extra entry point at offset &00000064, which should be used whe
History
-------
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
......
......@@ -3,7 +3,7 @@
tool_details_start
name "SDCreate";
command_is "<SDCreate$Dir>.SDCreate";
version "1.02b";
version "1.10";
wimpslot 256k;
has_extended_cmdline;
tool_details_end
......@@ -50,6 +50,8 @@ dbox_start
icn 24 maps_to "image " string;
icn 25 maps_to "";
icn 20 maps_to "";
icn 27 maps_to "CMOS " string;
icons_end
defaults
......@@ -62,6 +64,7 @@ dbox_start
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
......@@ -130,7 +133,7 @@ rules_end
# This boils down to one of two formats:
# (disc <id> | file <name>) [MLO <name>] [U-BOOT/BIN <name>] ([BOOT/SCR|BOOT/INI] <name> RISCOS <name> | UIMAGE <name>)
# disc <id> image <name>
# [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 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 4;
......@@ -43,4 +43,10 @@ The 'InstallHD4' script supplied with this archive is intended to be used in
conjunction with the installation steps given on the above page.
An important note about CMOS RAM
================================
The OMAP port of RISC OS now has the ability to use CMOS settings that are saved to the SD card alongside the ROM image. However, RISC OS currently lacks the ability to write updated settings back to the card. Therefore if you make any configuration changes that will affect CMOS RAM (e.g. switching to boot from drive 4 instead of 0) then you must make sure you manually save the settings using *SaveCMOS and copy the new file onto the SD card. For more information about how the CMOS file is handled, please see the !SDCreate help file.
-- RISC OS Open
/* (0.16)
/* (0.17)
*
* This file is automatically maintained by srccommit, do not edit manually.
* Last processed by srccommit version: 1.1.
*
*/
#define Module_MajorVersion_CMHG 0.16
#define Module_MajorVersion_CMHG 0.17
#define Module_MinorVersion_CMHG
#define Module_Date_CMHG 24 Nov 2010
#define Module_Date_CMHG 23 Jan 2011
#define Module_MajorVersion "0.16"
#define Module_Version 16
#define Module_MajorVersion "0.17"
#define Module_Version 17
#define Module_MinorVersion ""
#define Module_Date "24 Nov 2010"
#define Module_Date "23 Jan 2011"
#define Module_ApplicationDate "24-Nov-10"
#define Module_ApplicationDate "23-Jan-11"
#define Module_ComponentName "ABRelease"
#define Module_ComponentPath "castle/RiscOS/Utilities/Autobuild/ABRelease"
#define Module_FullVersion "0.16"
#define Module_HelpVersion "0.16 (24 Nov 2010)"
#define Module_LibraryVersionInfo "0:16"
#define Module_FullVersion "0.17"
#define Module_HelpVersion "0.17 (23 Jan 2011)"
#define Module_LibraryVersionInfo "0:17"
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