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

A few changes to make deciphering what's what easier.

For ROMs we essentially have IOMDHAL[Dev]; Tungsten[Dev]; OMAP3[Dev]; OMAP4Dev and for these it only makes sense to autobuild the Dev ones and offer them as softloads where there's an actual ROM chip to softload over. OMAP4Dev remains development status, IOMDHAL doesn't exist in stable form.
So:
 * IOMDHALDev - only make a softload ZIP file
 * IOMDHAL - do not use at this time
 * OMAP3Dev - updated text docs to reflect CMOS use
 * OMAP3 - do not use at this time
 * TungstenDev - only make a softload ZIP file
 * Tungsten - do not use at this time
 * OMAP4Dev - untouched
Removed references to !SCSIForm from InstallHD4 script.
Don't turn off alignment exceptions by default in InstallHD4 script.
Update RMEnsures to 5.19 for development.
Make readme's be non specific about the version to save updating them again.

Version 0.21. Tagged as 'ABRelease-0_21'
parent 8fcebe2f
......@@ -13,9 +13,8 @@
| limitations under the License.
|
| Set up and/or override some system variables
Set ab_local$zip rom-iomd/5/xx/zip
Set ab_local$soft soft-iomd/5/xx/zip
Set ab_soft$dir <ab_res$dir>.soft.!Boot.Choices.Boot.PreDesk.!!SoftLoad
Set ab_local$zip soft-iomd/5/xx/zip
Set ab_soft$dir <ab_res$dir>.zip.soft.!Boot.Choices.Boot.PreDesk.!!SoftLoad
| Remove any old crud from our resources directory
x Wipe <ab_res$dir>.zip ~cfr~v
......
......@@ -27,8 +27,9 @@ Copy ab_res:Licence_v1/pdf <ab_res$dir>.zip.Licence_v1/pdf ~cf~r~v
| Copy the ReadMe for this build into the zip directory
Copy ab_res:ReadMe/txt <ab_res$dir>.zip.ReadMe/txt ~cf~r~v
| Copy the ROM image into the zip directory
Copy <Build$Dir>.Images.<Build$ImageName> <ab_res$dir>.zip.riscos ~cf~r~v
| Copy the ROM image into the softload directory
Copy ab_res:soft <ab_res$dir>.zip.soft ~cfr~v
Copy <Build$Dir>.Images.<Build$ImageName> <ab_soft$dir>.riscos ~cf~r~v
| Set the zip directory as the current directory
Dir <ab_res$dir>.zip
......@@ -39,14 +40,6 @@ Do zip -9qr ^.<ab_local$zip> *
| Return the CSD to its original state
Back
| Create the softload zipfile
Copy ab_res:Licence_v1/pdf <ab_res$dir>.soft.Licence_v1/pdf ~cf~r~v
Copy <ab_res$dir>.zip.riscos <ab_soft$dir>.riscos ~cf~r~v
Dir <ab_res$dir>.soft
Do zip -9qr <ab_res$dir>.<ab_local$soft> *
SetType <ab_res$dir>.<ab_local$soft> &A91
Back
| Delete any pre-existing ROM build zip archive on the autobuild server
Remove <ab_zip$file>
......
......@@ -22,4 +22,4 @@
Set SoftLoad$Dir <Obey$Dir>
| Check OS version and run user prompt...
RMEnsure UtilityModule 5.17 Run <SoftLoad$Dir>.Prompt
\ No newline at end of file
RMEnsure UtilityModule 5.19 Run <SoftLoad$Dir>.Prompt
\ No newline at end of file
This is a ROM softloader patch for RiscPC and A7000 machines. It includes a
development release of the RISC OS 5.17 ROM image which can be installed into
development release of the RISC OS ROM image which can be installed into
your boot sequence as follows:
* Open your main hard disc (left click on the hard disc iconbar icon)
......
......@@ -77,10 +77,19 @@ That's it! If it all went well, you should now have a working SD card/image for
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.
......@@ -196,6 +205,8 @@ The U-Boot environment file (uenv.txt) is a file that new versions of U-Boot use
History
-------
V1.16 - 2012/1/7
* Scripts adjusted to load the CMOS file with 'fatload'
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
......
fatload mmc 0:1 0x4020F000 cmos
fatload mmc 0:1 0x81000000 riscos
go 0x81000000
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 0x4020F000 cmos
fatload mmc 0:1 0x81000000 riscos
go 0x8100000c
uenvcmd=fatload mmc ${mmcdev} ${loadaddr} riscos;go ${loadaddr}
uenvcmd=fatload mmc ${mmcdev} 4020F000 cmos;fatload mmc ${mmcdev} ${loadaddr} riscos;go ${loadaddr}
......@@ -12,7 +12,6 @@ basic
100MOV PC,R14
110]
120CALL code%
RUN
*changedynamicarea -ramfssize 32m
*ram
SAVE"RAM::RamDisc0.$.AOff"
......@@ -43,7 +42,7 @@ NEW
1040DATA" note its drive number on the icon bar."
1050DATA"2. Unplug the FAT formatted device you used to get"
1060DATA" to this point, if you wish."
1070DATA"3. To reformat this new device, run SCSIForm from"
1070DATA"3. To reformat this new device, run HForm from"
1080DATA" its shortcut placed on the Pinboard."
1090DATA"4. In the RAM::RamDisc0.$.HardDisc4 directory"
1100DATA" display, click Menu -> Select all."
......@@ -60,14 +59,14 @@ RUN
NEW
10REM Run self-extracting HardDisc4 image
20REM which provides the !Boot sequence and
30REM SCSI ADFS formatter
30REM FileCore formatter
40:
50REM Assumes a RAM disc of minimum size 32MB is present
60:
70*copy SCSI::0.HardDisc4/util RAM::RamDisc0.$.HD4 ~c
80*dismount :0
90*settype RAM::RamDisc0.$.HD4 &ffc
100*key0|m*delete RAM::RamDisc0.$.HD4|m*pin RAM::RamDisc0.$.HardDisc4.Utilities.USB-Mass.!SCSIForm 32 152|m*filer_opendir RAM::RamDisc0.$|m*filer_opendir RAM::RamDisc0.$.HardDisc4|m*filer_run RAM::RamDisc0.$.HD4instruct|m
100*key0|m*delete RAM::RamDisc0.$.HD4|m*pin RAM::RamDisc0.$.HardDisc4.Utilities.!HForm 32 152|m*filer_opendir RAM::RamDisc0.$|m*filer_opendir RAM::RamDisc0.$.HardDisc4|m*filer_run RAM::RamDisc0.$.HD4instruct|m
110*key1|m|m|m|m|m|mREM **********************|mREM * Finished. *|mREM * You may safely *|mREM * CLOSE this window. *|mREM **********************|m|mQUIT|mshellcli_taskquit|m
120*fx15,0
130*fx138,0,128
......
......@@ -46,14 +46,18 @@ 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.
The OMAP port of RISC OS now supports saving configuration settings in a CMOS memory chip so that they are kept when the power is turned off. This requires a small carrier board to be plugged in, which you can obtain for a few pounds from your favourite supplier.
If this carrier board is not detected it is possible to have 'read only' settings in one of two ways
* Add a CMOS file to the SD card
Make any configuration settings changes desired than use the *SaveCMOS
command to capture them in a file, put this file on the SD card alongside
the RISC OS ROM image.
For more information about how the CMOS file is handled, please see
the !SDCreate help file.
* Do nothing
If the hardware is not present, and you haven't put a CMOS file on the
SD card, you'll get the built in defaults.
-- RISC OS Open
......@@ -13,7 +13,6 @@
| limitations under the License.
|
| Set up and/or override some system variables
Set ab_local$zip rom-iyo-beta/5/xx/zip
Set ab_local$soft soft-iyo-beta/5/xx/zip
Set ab_soft$dir <ab_res$dir>.soft.!Boot.Choices.Boot.PreDesk.!!SoftLoad
......
......@@ -22,4 +22,4 @@
Set SoftLoad$Dir <Obey$Dir>
| Check OS version and run user prompt...
RMEnsure UtilityModule 5.17 Run <SoftLoad$Dir>.Prompt
\ No newline at end of file
RMEnsure UtilityModule 5.19 Run <SoftLoad$Dir>.Prompt
\ No newline at end of file
/* (0.20)
/* (0.21)
*
* This file is automatically maintained by srccommit, do not edit manually.
* Last processed by srccommit version: 1.1.
*
*/
#define Module_MajorVersion_CMHG 0.20
#define Module_MajorVersion_CMHG 0.21
#define Module_MinorVersion_CMHG
#define Module_Date_CMHG 20 Oct 2011
#define Module_Date_CMHG 07 Jan 2012
#define Module_MajorVersion "0.20"
#define Module_Version 20
#define Module_MajorVersion "0.21"
#define Module_Version 21
#define Module_MinorVersion ""
#define Module_Date "20 Oct 2011"
#define Module_Date "07 Jan 2012"
#define Module_ApplicationDate "20-Oct-11"
#define Module_ApplicationDate "07-Jan-12"
#define Module_ComponentName "ABRelease"
#define Module_ComponentPath "castle/RiscOS/Utilities/Autobuild/ABRelease"
#define Module_FullVersion "0.20"
#define Module_HelpVersion "0.20 (20 Oct 2011)"
#define Module_LibraryVersionInfo "0:20"
#define Module_FullVersion "0.21"
#define Module_HelpVersion "0.21 (07 Jan 2012)"
#define Module_LibraryVersionInfo "0:21"
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