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

rc2014/eeprom: adjust instructions

Browse Source 
Now that adev is directly in core, things are easier.
This commit is contained in:
Virgil Dupras 2020-05-22 20:35:01 -04:00
parent 6bff03a48b
commit a2136e604d
1 changed files with 7 additions and 13 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
recipes/rc2014/eeprom/README.md
View File

@ -34,19 +34,13 @@ I don't think you need a schematic. It's really simple.
### Building the binary ### Building the binary
You build the binary by modifying the base recipe's `xcomp` unit. This binary The binary from the base recipe has almost all it needs to write to EEPROM. The
is missing 2 things: Addressed devices and the AT28 Driver. only thing it needs is the AT28 driver from B590. You could add it to the
`xcomp` unit and rebuild, but the driver is so tiny, you're probably better off
loading it at runtime.
Addressed devices are at B140. If you read that block, you'll see that it tells If your system has mass storage, it's as easy as a LOAD. If it doesn't, you
you to load block 142. Open the `xcomp` unit and locate the ACIA driver loading can use `/tools/exec` to send `blk/591` to the RC2014.
line. Insert your new load line after that one.
Do the same thing with the AT28 driver (B590)
You also have to modify the initialization sequence at the end of the `xcomp`
unit to include `ADEV$`.
Build again, write `os.com` to EEPROM.
## Writing contents to the AT28 ## Writing contents to the AT28
@ -58,7 +52,7 @@ run this from your modern computer:
./upload <tty device> a000 <filename> ./upload <tty device> a000 <filename>
Then, activate `AT28!` with `' AT28! A!* !` and then run Then, activate `AT28!` with `' AT28! A!* !` and then run
`0xa000 0x2000 <size-of-bin> AMOVE`. `AT28!` checks every myte for integrity, `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! 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!`? Why not upload content directly to `0x2000` after having activated `AT28!`?