EmuTOS - M548x BaS_gcc version

This EmuTOS version runs on ColdFire V4e Evaluation Boards (EVB).
No graphical output, only text mode ColdFire TOS programs through RS-232.

emutos-m548x-bas.s19 - RAM executable (English)

Supported hardware:

- M5485EVB (a.k.a. Zoom ColdFire EVB)
https://www.nxp.com/products/no-longer-manufactured/mcf5485-evaluation-board:M5485EVB

- M5484LITE (a.k.a. Zoom ColdFire LITEKIT)
https://www.nxp.com/products/no-longer-manufactured/mcf5484-lite-evaluation-kit:M5484LITE

Prerequisites:
Your EVB needs to boot to BaS_gcc. It is a pre-OS similar to the one found on
the FireBee. You can download it there, but you will have to build it yourself:
https://github.com/firebee-org/BaS_gcc
Then you can flash the file m5484lite/bas.s19. Beware, after that, your EVB will
boot straight to BaS_gcc, and dBUG will not be available anymore.
Of course, you can always reflash dBUG afterwards.

Requirements:
- An RS-232 connection between the EVB and a controlling computer.
- On the computer, an ANSI terminal emulator connected to the RS-232 port.

Optional supported hardware:
- a CompactFlash card with a FAT16 partition.
- PS/2 keyboard connected through an Eiffel/CAN adapter.

To use the CompactFlash card, you need to have programmed the CPLD
(programmable component) on your board. You need to contact Logic PD
(the board manufacturer) to get the appropriate software package.
https://support.logicpd.com/

How to flash EmuTOS:
You just have to flash emutos-m548x-bas.s19 with your favorite flash tool.
Beware: The start address specified in this file is set regarding to the BaS
address space, which is different than dBUG's one. If you use Freescale's
CF Flasher on Windows, you need to go to the Target Config dialog and set the
Flash Base Address to 0xE0000000 before flashing.

How to run EmuTOS:

1) Switch on the EVB.
You will see a few BaS_gcc debug messages in the terminal.

2) Then you will see the EmuTOS welcome screen.
Press Escape to enter the early console.

3) If you wait too much, the desktop will run in the background.
Press Control+Z to return to EmuCON.

4) Then you can run EmuCON commands, and external text mode programs.

Restrictions:

- No graphical display.
Only text I/O through an RS/232 terminal or PS/2 keyboard

- Support for ColdFire TOS programs only. 680x0 programs will not work.

- No Atari hardware emulated. Clean programs using only the OS will work,
the ones trying direct access to the Atari hardware will not work.

This ROM image has been built using:
make m548x-bas

This release has been built on Linux Mint (a Ubuntu derivative), using
Vincent Rivière's GCC 4.6.4 cross-compiler.  The custom tools used in
the build process were built with native GCC 4.8.4.

The source package and other binary packages are available at:
https://sourceforge.net/projects/emutos/files/emutos/1.0/

The extras directory (if provided) contains:
(1) one or more alternate desktop icon sets, which you can use to replace
    the builtin ones.  You can use a standard resource editor to see what
    the replacement icons look like.
    To use a replacement set, move or rename the existing emuicon.rsc &
    emuicon.def files in the root directory, then copy the files containing
    the desired icons to the root, and rename them to emuicon.rsc/emuicon.def.
(2) a sample mouse cursor set in a resource (emucurs.rsc/emucurs.def).  This
    set is the same as the builtin ones, but you can use it as a basis to
    create your own mouse cursors.
    To use a replacement set, copy the files containing the desired mouse
    cursors to the root, and rename them to emucurs.rsc/emucurs.def.
For further information on the above, see doc/emudesk.txt.

If you want to read more about EmuTOS, please take a look at these files:

doc/announce.txt      - Introduction and general description, including
                        a summary of changes since the previous version
doc/authors.txt       - A list of the authors of EmuTOS
doc/bugs.txt          - Currently known bugs
doc/changelog.txt     - A summarised list of changes after release 0.9.4
doc/emudesk.txt       - A brief guide to the newer features of the desktop
doc/incompatible.txt  - Programs incompatible with EmuTOS due to program bugs
doc/license.txt       - The FSF General Public License for EmuTOS
doc/status.txt        - What is implemented and running (or not yet)
doc/todo.txt          - What should be done in future versions
doc/xhdi.txt          - Current XHDI implementation status

Additional information for developers (just in the source archive):

doc/install.txt       - How to build EmuTOS from sources
doc/coding.txt        - EmuTOS coding standards (never used :-) )
doc/country.txt       - An overview of i18n issues in EmuTOS
doc/fat16.txt         - Notes on the FAT16 filesystem in EmuTOS
doc/memdetect.txt     - Memory bank detection during EmuTOS startup
doc/nls.txt           - How to add a native language or use one
doc/old_changelog.txt - A summarised list of changes up to & including
                        release 0.9.4
doc/osmemory.txt      - All about OS internal memory in EmuTOS
doc/reschange.txt     - How resolution change works in the desktop
doc/resource.txt      - Modifying resources in EmuTOS
doc/startup.txt       - Some notes on the EmuTOS startup sequence
doc/tos14fix.txt      - Lists bugs fixed by TOS 1.04 & their status in EmuTOS

The following documents are principally of historical interest only:

doc/old_code.txt      - A museum of bugs due to old C language
doc/vdibind.txt       - Old information on VDI bindings

-- 
The EmuTOS development team
https://emutos.sourceforge.io/
