izaya/collapseos
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity
66dacd1816
collapseos/recipes/sms/romasm/glue.asm

167 lines
2.5 KiB
NASM
Raw Normal View History

recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
; 8K of onboard RAM
.equ RAMSTART 0xc000
recipes/sms/romasm: ed and zasm, fully functional!
2019-07-25 14:23:13 -04:00
.equ USER_RAMSTART 0xc200
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
; Memory register at the end of RAM. Must not overwrite
.equ RAMEND 0xddd0
jp init
; *** JUMP TABLE ***
jp strncmp
jp upcase
jp findchar
jp parseHex
jp parseHexPair
jp blkSel
jp blkSet
jp fsFindFN
jp fsOpen
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
jp fsGetB
jp fsPutB
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
jp fsSetSize
jp parseArgs
jp printstr
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
jp _blkGetB
jp _blkPutB
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
jp _blkSeek
jp _blkTell
jp printcrlf
jp stdioPutC
jp stdioReadLine
.fill 0x66-$
retn
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "err.h"
Move ASCII consts to ascii.h And made them shorter in name. The new ascii.h file allow reuse in userspace code.
2019-11-13 20:38:06 -05:00
.inc "ascii.h"
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer.
2019-11-15 15:37:49 -05:00
.inc "blkdev.h"
.inc "fs.h"
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "core.asm"
Extract str.asm from core.asm and make core included by userspace Most of register fiddling routines (which is now the only thing contained in care.asm) are used by almost all userspace apps, often in inner loops. That makes the penalty of using jump tables for those a bit too high. Moreover, it burdens jump tables needlessly. Because this unit is very small (now that string routines are out), it makes sense to always include it in binaries.
2019-11-14 09:55:31 -05:00
.inc "str.asm"
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "sms/kbd.asm"
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
.equ KBD_RAMSTART RAMSTART
.equ KBD_FETCHKC smskbdFetchKCB
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "kbd.asm"
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
.equ VDP_RAMSTART KBD_RAMEND
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "sms/vdp.asm"
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
.equ STDIO_RAMSTART VDP_RAMEND
stdio: remove a layer of indirection in GetC/PutC We use zasm's ability to use labels in .equ directive. We didn't do it before because for a while, we were in between scas and zasm (scas was used in automated tests) so we needed to use the lowest common denominator: zasm doesn't have macros and scas can't use labels in .equ directives. This forced us to add this layer of indirection. But now that we are completely cut from scas' dependency, we can use this nice zasm's ability.
2019-11-04 09:55:12 -05:00
.equ STDIO_GETC kbdGetC
.equ STDIO_PUTC vdpPutC
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "stdio.asm"
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
recipes/sms/romasm: ed and zasm, fully functional!
2019-07-25 14:23:13 -04:00
.equ MMAP_START 0xd700
; 0x180 is to leave some space for the stack
.equ MMAP_LEN RAMEND-MMAP_START-0x180
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "mmap.asm"
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
.equ BLOCKDEV_RAMSTART STDIO_RAMEND
.equ BLOCKDEV_COUNT 3
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "blockdev.asm"
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
; List of devices
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
.dw mmapGetB, mmapPutB
.dw f0GetB, f0PutB
.dw f1GetB, f1PutB
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
.equ FS_RAMSTART BLOCKDEV_RAMEND
.equ FS_HANDLE_COUNT 2
zasm: rename #inc to .inc scas, it's not needed any more.
2019-10-06 14:32:23 -04:00
.inc "fs.asm"
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer.
2019-11-15 15:37:49 -05:00
; *** Shell ***
.inc "lib/util.asm"
.inc "lib/parse.asm"
.inc "lib/args.asm"
.inc "lib/stdio.asm"
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
.equ SHELL_RAMSTART FS_RAMEND
recipes/sms/romasm: ed and zasm, fully functional!
2019-07-25 14:23:13 -04:00
.equ SHELL_EXTRA_CMD_COUNT 10
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer.
2019-11-15 15:37:49 -05:00
.inc "shell/main.asm"
recipes/sms/romasm: ed and zasm, fully functional!
2019-07-25 14:23:13 -04:00
.dw edCmd, zasmCmd, fnewCmd, fdelCmd, fopnCmd, flsCmd, blkBselCmd
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
.dw blkSeekCmd, blkLoadCmd, blkSaveCmd
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer.
2019-11-15 15:37:49 -05:00
.inc "shell/blkdev.asm"
.inc "shell/fs.asm"
recipes/sms/romasm: adjust glue to zasm changes Forward reference of SHELL_MEM_PTR wasn't working (nor should it have been...).
2019-07-23 15:42:52 -04:00
recipes/sms/romasm: ed and zasm, fully functional!
2019-07-25 14:23:13 -04:00
.equ PGM_RAMSTART SHELL_RAMEND
.equ PGM_CODEADDR USER_RAMSTART
Make the shell a userspace app That's my mega-commit you've all been waiting for. The code for the shell share more routines with userspace apps than with kernel units, because, well, its behavior is that of a userspace app, not a device driver. This created a weird situation with libraries and jump tables. Some routine belonging to the `kernel/` directory felt weird there. And then comes `apps/basic`, which will likely share even more code with the shell. I was seeing myself creating huge jump tables to reuse code from the shell. It didn't feel right. Moreover, we'll probably want basic-like apps to optionnally replace the shell. So here I am with this huge change in the project structure. I didn't test all recipes on hardware yet, I will do later. I might have broken some... But now, the structure feels better and the line between what belongs to `kernel` and what belongs to `apps` feels clearer.
2019-11-15 15:37:49 -05:00
.inc "shell/pgm.asm"
recipes/sms/romasm: ed and zasm, fully functional!
2019-07-25 14:23:13 -04:00
.out PGM_RAMEND
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
init:
di
im 1
ld sp, RAMEND
; init a FS in mmap
ld hl, MMAP_START
ld a, 'C'
ld (hl), a
inc hl
ld a, 'F'
ld (hl), a
inc hl
ld a, 'S'
ld (hl), a
recipes/sms/romasm: limit mmap size Otherwise, we overflow into the RAM mirror, which means we overwrite the beginning of the RAM.
2019-07-23 23:01:17 -04:00
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
call fsInit
xor a
recipes/sms/romasm: limit mmap size Otherwise, we overflow into the RAM mirror, which means we overwrite the beginning of the RAM.
2019-07-23 23:01:17 -04:00
ld de, BLOCKDEV_SEL
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
call blkSel
recipes/sms/romasm: limit mmap size Otherwise, we overflow into the RAM mirror, which means we overwrite the beginning of the RAM.
2019-07-23 23:01:17 -04:00
call fsOn
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
call kbdInit
call vdpInit
call shellInit
recipes/sms/romasm: ed and zasm, fully functional!
2019-07-25 14:23:13 -04:00
ld hl, pgmShellHook
ld (SHELL_CMDHOOK), hl
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
jp shellLoop
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
f0GetB:
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
ld ix, FS_HANDLES
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
jp fsGetB
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
f0PutB:
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
ld ix, FS_HANDLES
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
jp fsPutB
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
f1GetB:
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
ld ix, FS_HANDLES+FS_HANDLE_SIZE
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
jp fsGetB
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
f1PutB:
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
ld ix, FS_HANDLES+FS_HANDLE_SIZE
Rename blockdev's API routines to GetB/PutB The goal is to avoid mixing those routines with "character devices" (acia, vpd, kbd) which aren't block devices and have routines that have different expectations. This is a first step to fixing #64.
2019-10-30 16:59:35 -04:00
jp fsPutB
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
edCmd:
shell: allow cmds to be shorter than 4 chars
2019-07-21 15:57:55 -04:00
.db "ed", 0, 0, 0b1001, 0, 0
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
push hl \ pop ix
ld l, (ix)
ld h, (ix+1)
recipes/sms/romasm: adjust ed/zasm offsets
2019-07-22 10:10:42 -04:00
jp 0x1900
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
zasmCmd:
.db "zasm", 0b1001, 0, 0
push hl \ pop ix
ld l, (ix)
ld h, (ix+1)
recipes/sms/romasm: adjust ed/zasm offsets
2019-07-22 10:10:42 -04:00
jp 0x1d00
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
recipes/sms/romasm: adjust ed/zasm offsets
2019-07-22 10:10:42 -04:00
; last time I checked, PC at this point was 0x183c. Let's give us a nice margin
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
; for the start of ed.
recipes/sms/romasm: adjust ed/zasm offsets
2019-07-22 10:10:42 -04:00
.fill 0x1900-$
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
.bin "ed.bin"
recipes/sms/romasm: adjust ed/zasm offsets
2019-07-22 10:10:42 -04:00
; Last check: 0x1c4e
.fill 0x1d00-$
recipes/sms/romasm: first steps
2019-07-21 15:37:03 -04:00
.bin "zasm.bin"
.fill 0x7ff0-$
.db "TMR SEGA", 0x00, 0x00, 0xfb, 0x68, 0x00, 0x00, 0x00, 0x4c
Reference in New Issue Copy Permalink