•  Back 
  •  Firmware Updates 
  •  Index 
  •  Cross references 
  •  Help Page 
  •  Show info about hypertext 
  •  View a new file 
Topic       : CTPCI Documentation
Author      : Sascha Uhlig (Editor)
Version     : CTPCI.hyp (5/12/2010)
Subject     : Expansion Card
Nodes       : 135
Index Size  : 3892
HCP-Version : 5
Compiled on : Atari
@charset    : atarist
@lang       : 
@default    : Title Page
@help       : Help Page
@options    : -i +zz
@width      : 70
View Ref-File5.1  Updating CT60/63 Flash Memory                               CTPCI

On Atari computers, the whole operating system (TOS) including the 
GEM desktop [⇨9]The TOS consists of the following:
 - Desktop
 - GEM    (Graphical Environment Manager)
    ⇨ AES (Application Environment Services)
    ⇨ VDI (Virtual Device Interface, screen drivers only,
           other drivers loaded using the separately loaded
           GDOS, Graphics Device Operation System)
 - GEMDOS (GEM Disk Operating System)
 - BIOS   (Basic Input Output System)
 - XBIOS  (eXtended BIOS)
 - Line-A (low-level high-speed graphics calls, obsolete)
 is stored in the ROM and is immediately ready after 
power up. On a CT60/63 Falcon, the whole system is in a flash chip on 
the CT60/63 board that can be rewritten so allowing the system to be 
updated very easily.

A CT60/63 Falcon uses a patched TOS 4.04 for the CT60/63. Of course, 
the TOS can be replaced by an alternative and modern operating system 
like a patched MagiC, or (a not too old) MiNT ('just' a GEMDOS and a 
partly BIOS and XBIOS replacement [⇨9]The TOS consists of the following:
 - Desktop
 - GEM    (Graphical Environment Manager)
    ⇨ AES (Application Environment Services)
    ⇨ VDI (Virtual Device Interface, screen drivers only,
           other drivers loaded using the separately loaded
           GDOS, Graphics Device Operation System)
 - GEMDOS (GEM Disk Operating System)
 - BIOS   (Basic Input Output System)
 - XBIOS  (eXtended BIOS)
 - Line-A (low-level high-speed graphics calls, obsolete)
) with a window manager like 
XaAES. Nevertheless the patched TOS is still needed to boot your 
Falcon and for accessing some low-level routines. If you like, you 
can imagine the CT60/63's flash memory contents, like in PCs, as the 
basic input/output system (BIOS) of your computer.


Updating the flash memory is very easy. Download the latest CT60 
software archive and the TOS PCI drivers package from Didier 
Méquignon's website. There you will find two files:

CT60TOS.bin

   Normal CT60 TOS including the boot part and the Atari Diagnostics 
   (Falcon diagnostic tool).

   The boot part for loading the PCI drivers also contains the PCI 
   BIOS which has automatic PCI space configuration (with/without 
   EtherNat/SuperVidel) for getting the maximum space (1 GB) for the 
   PCI zones.

Drivers.hex

   The compressed PCI drivers contains two drivers, a graphics card 
   driver that consists of
    - a VDI/fVDI remix (TOS compatible),
    - a Radeon driver,
    - an x86 emulator (for initialising the Radeon board) and
    - updated XBIOS screen functions,
   and a USB mouse/keyboard/storage driver.

   If the PCI drivers are installed, they will replace the Atari 
   Diagnostics. They cannot be used together since there is not 
   enough space.



index=109
Figure. Flash060 after loading a flash file Start the tool Flash060 from the CT60 software package, load the binary or hexadecimal file (*.bin, *.hex) you want to use, by clicking on the load icon or on the source info line, and press [PROGRAM]. If the last status light flashes up and you get no alert, everything is fine. Reflashing the firmware can take up to 20 seconds. Please note the following: ∙ In order to avoid problems, do not use older versions of Flash060. For example, versions earlier than 1.9 do not work with newer CT63 boards (which have a new flash chip). ∙ You can even flash the memory in 060 mode. You may get the alert: 'TOS in flash may currently be in use. Are you sure you want to update the flash?' However, it is only relevant if TOS does not run in RAM (check the option 'TOS in RAM' inside 'Boot' of the CT60 Configuration CPX). And, since version 2.00 of CT60 TOS, this problem does not exist because TOS runs always in RAM.