Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| builderpages:plasmo:tinyz280:final_step [2021/06/19 16:28] – Revision from 2021-06-19 | builderpages:plasmo:tinyz280:final_step [2026/06/15 13:14] (current) – external edit 127.0.0.1 | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| + | /* Imported from Wayback Machine | ||
| + | | ||
| + | | ||
| + | | ||
| + | */ | ||
| + | |||
| + | ====== Final Step, Putting it all together ====== | ||
| + | |||
| + | The [[builderpages: | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | TinyZ280 component side | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | TinyZ280 solder side | ||
| + | |||
| + | ===== Features ===== | ||
| + | |||
| + | Z280 at full bus speed of 12MHz | ||
| + | |||
| + | 4 megbyte of DRAM, can be upgraded to 16 megabyte | ||
| + | |||
| + | RTC based on Dallas DS12887 | ||
| + | |||
| + | Bus connected CF interface | ||
| + | |||
| + | Four 8-meg CF drives (A: to D:) | ||
| + | |||
| + | 3.5-meg RAM drive (E:) | ||
| + | |||
| + | One internal UART at 57600 baud, odd parity, no handshake | ||
| + | |||
| + | bootstrap from CF disk to ZZMon, a simple monitor | ||
| + | |||
| + | CP/M 2.2 | ||
| + | |||
| + | CP/M 3 non-banked | ||
| + | |||
| + | ===== Modes of Operation ===== | ||
| + | |||
| + | TinyZ280 has two modes of operation as determined by the mode jumper at power up (see picture below for location of mode jumper). Jumper removed set the UART bootstrap mode; jumper inserted set the CF bootstrap mode. | ||
| + | |||
| + | ==== UART Bootstrap ==== | ||
| + | |||
| + | At power up the Z280 CPU is held in idle state until 256 bytes of instruction is uploaded to UART (57600 baud, odd parity, and no handshake) which is then copied to memory starting from location 0x0. Afterward the CPU starts execution from 0x0. In UART bootstrap mode, the program “LoadnGo.run” is send to the UART. LoadnGo contains a 256 bytes binary file that loads the following ZZMon in Intel Hex format and then jump to the starting address of ZZMon. This is the mode to initialize a new CF disk. The cold bootstrap code is written to boot sector and ZZMon itself is written to track 0 of CF in this mode. All the functions of ZZMon is accessible in UART bootstrap mode. In fact the TinyZ280 hardware has all the functionalities except it needs to be booted up serially at power up and every reset. | ||
| + | |||
| + | ==== CF Bootstrap ==== | ||
| + | |||
| + | This is normal mode of operation. At powerup, the state machine in CPLD initializes the CF to access cold bootstrap code stored in the boot sector and map the memory from 0x0-0x1FF to the data register of CF. Once the boot sector data is loaded into the 512-byte FIFO of CF data register, the state machine releases the reset of Z280 which then executes a two-stage bootstrapping operations: | ||
| + | |||
| + | 1. Z280 executes the cold bootstrap code which copies a small CF loading program into memory and then jump into the CF loading program. | ||
| + | |||
| + | 2. The CF loading program loads the monitor, ZZMon, from CF disk into memory and jump to ZZMon. ZZMon will display a sign-on message and wait for user inputs. Refer to [[builderpages: | ||
| + | |||
| + | Here is a more detailed description of the [[builderpages: | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | ===== Initialize a New CF disk ===== | ||
| + | |||
| + | The CF disk shipped with the board already has all the necessary software loaded. When a new CF disk is used for the 1st time, the following steps are required: | ||
| + | |||
| + | Insert the new CF disk, remove the mode jumper and power up the board up in UART bootstrap mode. There will be no sign-on message displayed on the console because TinyZ280 is waiting for file upload via the serial port (57600 baud, odd parity, 8 data bits, 1 stop, no handshake). send the program ' | ||
| + | |||
| + | //TinyZZ Monitor v0.8 3/25/18//\\ | ||
| + | //>// | ||
| + | |||
| + | ZZMon is running at this point. Issue the commands: | ||
| + | |||
| + | **c0 (press enter to execute)** to copy the cold bootstrap code to CF's boot sector, | ||
| + | |||
| + | **c1 (press enter to execute)** to copy the ZZMon to CF's LBA sectors 0xF8-0xFF | ||
| + | |||
| + | Power down TinyZ280 and insert the mode jumper and re-apply the power. The ZZMon should sign on with the message: | ||
| + | |||
| + | //TinyZZ Monitor v0.8 3/25/18//\\ | ||
| + | //>// | ||
| + | |||
| + | upload the Intel Hex file cpm22all.hex (the program can be found in the Software section below). Issue the command: | ||
| + | |||
| + | **c2 (press enter to execute)** to copy cpm22 CCP/ | ||
| + | |||
| + | Upload the Intel Hex file cpmldr.hex (the program can be found in the Software section below). Issue the command: | ||
| + | |||
| + | **c3 (press enter to execute)** to copy CPM3 loader into LBA sector 0x1-0xF | ||
| + | |||
| + | Issue the commands: | ||
| + | |||
| + | **xA (press enter to execute)** to erase drive A directory | ||
| + | |||
| + | **xB (press enter to execute)** to erase drive B directory | ||
| + | |||
| + | **xC (press enter to execute)** to erase drive C directory | ||
| + | |||
| + | **xD (press enter to execute)** to erase drive D directory | ||
| + | |||
| + | upload cpm22dri.hex (the program can be found in the Software section below). This is cpm22 distribution files image that' | ||
| + | |||
| + | **b2 (press enter to execute)** to boot CP/M 2.2. At the CP/M prompt type: | ||
| + | |||
| + | **e:pip b: | ||
| + | |||
| + | Press the reset button to exit CP/M 2.2 to ZZMon and upload cpm3dstr.hex (this program can be found int the Software section below). This is the CPM3 distribution files image that' | ||
| + | |||
| + | **b2 (press enter to execute)** to boot CP/M 2.2. At the CP/M prompt type: | ||
| + | |||
| + | **b:pip a: | ||
| + | |||
| + | Press the reset button to exit CP/M 2.2 to ZZMon and type | ||
| + | |||
| + | **b3 (press enter to execute)** to boot CP/M 3. At the CP/M prompt type: | ||
| + | |||
| + | **pip c: | ||
| + | |||
| + | This completes the initialization of a new CF disk. | ||
| + | |||
| + | ===== Design Files ===== | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | [[builderpages: | ||
| + | |||
| + | CPLD design file. | ||
| + | |||
| + | CPLD design file for [[https:// | ||
| + | |||
| + | CPLD design file for [[https:// | ||
| + | |||
| + | [[software: | ||
| + | |||
| + | ZZMon – [[https:// | ||
| + | |||
| + | LoadnGo – [[https:// | ||
| + | |||
| + | CP/M2.2, [[https:// | ||
| + | |||
| + | CP/M2.2 [[https:// | ||
| + | |||
| + | CP/M3 [[https:// | ||
| + | |||
| + | CP/M3 [[https:// | ||
| + | |||
| + | CP/M3 CPMLDR.COM linked to 0x1100. This is an [[https:// | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | [[https:// | ||
| + | |||
| + | Manual | ||
| + | |||
| + | [[builderpages: | ||
| + | |||
| + | ZZMon [[builderpages: | ||
| + | |||
| + | TinyZ280 [[builderpages: | ||
| + | |||
| + | Creating a [[builderpages: | ||
