collapseos/emul/z80/xcomp.fs

0xff00 CONSTANT RS_ADDR
0xfffa CONSTANT PS_ADDR
RS_ADDR 0x80 - CONSTANT SYSVARS
0 CONSTANT HERESTART
5 LOAD  ( z80 assembler )
262 LOAD  ( xcomp )
282 LOAD  ( boot.z80.decl )
270 LOAD  ( xcomp overrides )
283 335 LOADR ( boot.z80 )
353 LOAD  ( xcomp core low )
: (emit) 0 PC! ;
: (key?) 0 PC@ 1 ;
: EFS@
    1 3 PC! ( read )
    256 /MOD 3 PC! 3 PC! ( blkid )
    BLK( 256 /MOD 3 PC! 3 PC! ( dest )
;
: EFS!
    2 3 PC! ( write )
    256 /MOD 3 PC! 3 PC! ( blkid )
    BLK( 256 /MOD 3 PC! 3 PC! ( dest )
;
: COLS 80 ; : LINES 32 ;
: AT-XY 6 PC! ( y ) 5 PC! ( x ) ;

390 LOAD  ( xcomp core high )
(entry) _
( Update LATEST )
PC ORG @ 8 + !
," BLK$ "
," ' EFS@ BLK@* ! "
," ' EFS! BLK!* ! "
EOT,
ORG @ 256 /MOD 2 PC! 2 PC!
H@ 256 /MOD 2 PC! 2 PC!
By default, allocate about 0x100 bytes for PSP+RSP During "make updatebootstrap", we use less than 0x20 bytes on the PSP side and less than 0x40 bytes on the RSP one. 0x100 bytes ought to be enough for anybody. 2020-05-15 08:41:09 +10:00			`0xff00 CONSTANT RS_ADDR`
Replace INITIAL_SP with PS_ADDR conf Now I struggle to remember why I ever did things they way I did. There must have been a reason... 2020-05-12 11:08:24 +10:00			`0xfffa CONSTANT PS_ADDR`
Add HERESTART xcomp config 2020-06-29 09:45:28 +10:00			`RS_ADDR 0x80 - CONSTANT SYSVARS`
			`0 CONSTANT HERESTART`
Move z80a from B200 to B5 The idea is to consider assemblers as "runtime" apps instead of placing them in the "bootstrap" section of the blocks. These apps will be used for much more than bootstrapping. Moved its documentation to doc/asm.txt and made its code blocks more compact. 2020-09-22 07:51:08 +10:00			`5 LOAD ( z80 assembler )`
Use blk's boot.z80 2020-04-23 11:49:44 +10:00			`262 LOAD ( xcomp )`
z80: make boot binary a 2-part process Previously, recipes that began spitting binary contents before loading block 282 would end up with VARIABLE code in their binary, thus breaking them. We fix this by making this loading process 2-part. 2020-06-27 11:41:17 +10:00			`282 LOAD ( boot.z80.decl )`
xcomp: add overrides into a loadable block Makes xcomp.fs units shorter. 2020-05-14 03:33:24 +10:00			`270 LOAD ( xcomp overrides )`
z80: make boot binary a 2-part process Previously, recipes that began spitting binary contents before loading block 282 would end up with VARIABLE code in their binary, thus breaking them. We fix this by making this loading process 2-part. 2020-06-27 11:41:17 +10:00			`283 335 LOADR ( boot.z80 )`
Move Cross-compiled core from B390 to B350 and renamed it "Core words". Also, reworded the presentation. 2020-05-16 12:44:49 +10:00			`353 LOAD ( xcomp core low )`
Split icore in 2 parts The goal is to insert device drivers in between. 2020-05-09 11:47:03 +10:00			`: (emit) 0 PC! ;`
Make KEY non-blocking ... and rename it to KEY?. Then, add KEY from KEY? for its blocking version. I need this for an upcoming Remote Shell feature. If a Collapse OS system remotely controls another shell, it needs to be able to poll both the remote system and the local keyboard at the same time. A blocking KEY is incompatible with this. In some places, the polling mechanism doesn't make sense, so this new KEY? always returns a character. In some places, I just haven't implemented the mechanism yet, so I kept the old blocking code and added a "always 1" flag as a temporary shim. I have probably broken something, but in emulators, Collapse OS runs fine. It's an important reminder of what will be lost with the new "dogfooding" approach (see recent mailing list message): without emulators, it's much harder to to sweeping changes like this without breaking stuff. It's fine, I don't expect many more of these core changes to the system. It's nearly feature-complete. 2021-01-02 00:05:29 +11:00			`: (key?) 0 PC@ 1 ;`
emul: remove stage1 2020-05-15 00:49:24 +10:00			`: EFS@`
emul: make blk operations much faster It helps a bit with staging times. 2020-06-22 20:29:00 +10:00			`1 3 PC! ( read )`
			`256 /MOD 3 PC! 3 PC! ( blkid )`
			`BLK( 256 /MOD 3 PC! 3 PC! ( dest )`
emul: remove stage1 2020-05-15 00:49:24 +10:00			`;`
			`: EFS!`
emul: make blk operations much faster It helps a bit with staging times. 2020-06-22 20:29:00 +10:00			`2 3 PC! ( write )`
			`256 /MOD 3 PC! 3 PC! ( blkid )`
			`BLK( 256 /MOD 3 PC! 3 PC! ( dest )`
emul: remove stage1 2020-05-15 00:49:24 +10:00			`;`
emul: implement AT-XY VI, here we come! 2020-05-24 10:15:28 +10:00			`: COLS 80 ; : LINES 32 ;`
			`: AT-XY 6 PC! ( y ) 5 PC! ( x ) ;`
emul: remove stage1 2020-05-15 00:49:24 +10:00
Move most of the high layer of comp core into the low one With KEY and EMIT being switch words, most of the high layer can be defined before drivers. In addition to this change, I've compacted core blocks which were becoming quite sparse. 2020-10-29 09:06:58 +11:00			`390 LOAD ( xcomp core high )`
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-24 05:14:14 +10:00			`(entry) _`
Update z80c.bin's LATEST during xcomp instead of using slatest 2020-04-26 12:02:44 +10:00			`( Update LATEST )`
xcomp: remove XOFF and use ORG and BIN( instead 2020-04-28 23:15:17 +10:00			`PC ORG @ 8 + !`
emul: remove stage1 2020-05-15 00:49:24 +10:00			`," BLK$ "`
Streamline initialization process Instead of letting each configuration taking care of RDLN$ and "CollapseOS" prompt, move this to BOOT to simplify xcomp units. Initialization source code is now only for driver initialization. 2020-05-16 01:34:35 +10:00			`," ' EFS@ BLK@* ! "`
			`," ' EFS! BLK!* ! "`
			`EOT,`
xcomp: move all offset spitting to the end of the unit I'd like to move this code, along with all recipe contents, to blk/. It's easier if "emul-related" code is gathered at the same place. 2020-05-06 10:10:04 +10:00			`ORG @ 256 /MOD 2 PC! 2 PC!`
Move icore to blkfs The way is clear for complete stage1 bootstrapping on the RC2014 target! 2020-04-24 05:14:14 +10:00			`H@ 256 /MOD 2 PC! 2 PC!`