izaya/collapseos
1
1
Fork 0
Code Issues Pull Requests Releases Wiki Activity

tools/upload: use A! instead of C! to write

Browse Source 
By default, it changes nothing, but it allows interesting
setups, such as using AT28! for directly uploading to EEPROM.

I've also updated the EEPROM recipe to upload directly to 0x2000.
I'm not sure what has changed, but it's working fine now.
This commit is contained in:
Virgil Dupras 2020-09-17 13:27:12 -04:00
parent a19c814b0d
commit 7dc00179f7
2 changed files with 5 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

17
recipes/rc2014/eeprom.md
View File

@ -44,18 +44,9 @@ can use `/tools/exec` to send `blk/593` to the RC2014.
## Writing contents to the AT28 ## Writing contents to the AT28
The driver provides `AT28!` which can be plugged in adev's `A!*`. The driver provides `AT28!` which can be plugged in adev's `A!*`. You can do so
with `' AT28! A!* !`.
First, upload your binary to some place in memory, for example `a000`. To do so, Then, upload your binary to EEPROM with:
run this from your modern computer:
./upload <tty device> a000 <filename> ./upload <tty device> 2000 <filename>
Then, activate `AT28!` with `' AT28! A!* !` and then run
`0xa000 0x2000 <size-of-bin> AMOVE`. `AT28!` checks every byte for integrity,
so it there's no error, you should be fine. Your content is now on the EEPROM!
Why not upload content directly to `0x2000` after having activated `AT28!`?
Technically, you could. It was my first idea too. However, at the time of this
writing, I always get weird mismatch errors about halfway through. Maybe that
the ACIA interrupt does something wrong...

2
tools/upload.c
View File

@ -42,7 +42,7 @@ int main(int argc, char **argv)
} }
char s[0x40]; char s[0x40];
sprintf(s, sprintf(s,
": _ 0x%04x 0x%04x DO KEY DUP .x I C! LOOP ; _", ": _ 0x%04x 0x%04x DO KEY DUP .x I A! LOOP ; _",
memptr+bytecount, memptr); memptr+bytecount, memptr);
sendcmd(fd, s); sendcmd(fd, s);