From 9344c4b961fef0ad73dce842a70e3c122a27fd08 Mon Sep 17 00:00:00 2001 From: Virgil Dupras Date: Mon, 4 Nov 2019 14:45:10 -0500 Subject: [PATCH] doc: minor improvements --- recipes/rc2014/README.md | 4 +++- recipes/rc2014/eeprom/README.md | 2 +- 2 files changed, 4 insertions(+), 2 deletions(-) diff --git a/recipes/rc2014/README.md b/recipes/rc2014/README.md index 871e78e..6041d9b 100644 --- a/recipes/rc2014/README.md +++ b/recipes/rc2014/README.md @@ -75,7 +75,9 @@ is decoupled from the ACIA and can get its IO from anything. See We only have the shell to build, so it's rather straightforward: - zasm < glue.asm > rom.bin + ../../tools/zasm.sh ../../kernel < glue.asm > os.bin + +Running `make` will also work. ### Write to the ROM diff --git a/recipes/rc2014/eeprom/README.md b/recipes/rc2014/eeprom/README.md index cc9c047..fed51ae 100644 --- a/recipes/rc2014/eeprom/README.md +++ b/recipes/rc2014/eeprom/README.md @@ -27,7 +27,7 @@ If you're tempted by the idea of hacking your existing RC2014 ROM module by wiring `WR` and write directly to the range `0x0000-0x1fff` while running it, be aware that it's not that easy. I was also tempted by this idea, tried it, but on bootup, it seems that some random `WR` triggers happen and it corrupts -the EEPROM contents. Theoretically, we could go around that my putting the AT28 +the EEPROM contents. Theoretically, we could go around that by putting the AT28 in write protection mode, but I preferred building my own module. I don't think you need a schematic. It's really simple.