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

Update ReadMe's

Clarify CMOS use with OMAP3/4, copy notes to BCM2835.
Update FlashQSPI to latest for Titanium.

Version 0.77. Tagged as 'ABRelease-0_77'
parent 7a779719
......@@ -29,4 +29,23 @@ readme file in the ZeroPain folder for more information. It is recommended that
you install the module before you install this new ROM image, otherwise you may
have difficulty booting your system.
CMOS RAM
========
The Raspberry Pi doesn't include any CMOS memory on the circuit board which
RISC OS expects to find to hold its essential configuration options needed
before the main !Boot application is run.
It is possible to seed the CMOS 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. The SDCMOS module included in the operating system
will update this file whenever a configuration change is made.
* 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 every time you turn on.
-- RISC OS Open
......@@ -58,25 +58,28 @@ 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
================================
CMOS RAM
========
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.
a few pounds from
If this carrier board is not detected it is possible to have 'read only'
settings in one of two ways
http://www.riscosopen.org/content/sales/cmos-widgets
or your RISC OS dealer.
If this carrier board is not detected it is possible to seed the CMOS 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.
the RISC OS ROM image. The SDCMOS module included in the operating system
will update this file whenever a configuration change is made.
* 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.
SD card, you'll get the built in defaults every time you turn on.
-- RISC OS Open
......@@ -58,25 +58,28 @@ 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
================================
CMOS RAM
========
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.
a few pounds from
If this carrier board is not detected it is possible to have 'read only'
settings in one of two ways
http://www.riscosopen.org/content/sales/cmos-widgets
or your RISC OS dealer.
If this carrier board is not detected it is possible to seed the CMOS 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.
the RISC OS ROM image. The SDCMOS module included in the operating system
will update this file whenever a configuration change is made.
* 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.
SD card, you'll get the built in defaults every time you turn on.
-- RISC OS Open
/* (0.76)
/* (0.77)
*
* This file is automatically maintained by srccommit, do not edit manually.
* Last processed by srccommit version: 1.1.
*
*/
#define Module_MajorVersion_CMHG 0.76
#define Module_MajorVersion_CMHG 0.77
#define Module_MinorVersion_CMHG
#define Module_Date_CMHG 03 Jun 2016
#define Module_Date_CMHG 16 Oct 2016
#define Module_MajorVersion "0.76"
#define Module_Version 76
#define Module_MajorVersion "0.77"
#define Module_Version 77
#define Module_MinorVersion ""
#define Module_Date "03 Jun 2016"
#define Module_Date "16 Oct 2016"
#define Module_ApplicationDate "03-Jun-16"
#define Module_ApplicationDate "16-Oct-16"
#define Module_ComponentName "ABRelease"
#define Module_ComponentPath "castle/RiscOS/Utilities/Autobuild/ABRelease"
#define Module_FullVersion "0.76"
#define Module_HelpVersion "0.76 (03 Jun 2016)"
#define Module_LibraryVersionInfo "0:76"
#define Module_FullVersion "0.77"
#define Module_HelpVersion "0.77 (16 Oct 2016)"
#define Module_LibraryVersionInfo "0:77"
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