izaya/collapseos
1
0
Fork 0
mirror of https://github.com/hsoft/collapseos.git synced 2024-11-23 22:48:05 +11:00
Code Issues Releases Wiki Activity
4720714bd4
collapseos/blk/160

17 lines
636 B
Plaintext
Raw Normal View History

avrpgm: add EEPROM support also, verify all 3 first bytes of SPI commands. I'm not sure why I wasn't doing that, probably because I was getting a lot of AVR err and thought that only 2 bytes of the cmd were echoed. But now, with a reliable SPI setup, verifying 3 bytes seems to work.
2020-10-06 10:32:42 +11:00
( AVR Programmer, load range 160-163. doc/avr.txt )
avr: allow writing to flash
2020-09-06 04:07:13 +10:00
( page size in words, 64 is default on atmega328P )
CREATE aspfpgsz 64 ,
VARIABLE aspprevx
: _x ( a -- b ) DUP aspprevx ! (spix) ;
: _xc ( a -- b ) DUP (spix) ( a b )
DUP aspprevx @ = NOT IF ABORT" AVR err" THEN ( a b )
SWAP aspprevx ! ( b ) ;
avrpgm: add EEPROM support also, verify all 3 first bytes of SPI commands. I'm not sure why I wasn't doing that, probably because I was getting a lot of AVR err and thought that only 2 bytes of the cmd were echoed. But now, with a reliable SPI setup, verifying 3 bytes seems to work.
2020-10-06 10:32:42 +11:00
: _cmd ( b4 b3 b2 b1 -- r4 ) _xc DROP _xc DROP _xc DROP _x ;
avr: allow writing to flash
2020-09-06 04:07:13 +10:00
: asprdy ( -- ) BEGIN 0 0 0 0xf0 _cmd 1 AND NOT UNTIL ;
Make the SPI Relay protocol support multiple devices Working on programming AVR chips exposes a glaring omission in my first design of the SPI Relay: not allowing multiple devices make this task hard. I constantly have to unplug my SD card before, plug the AVR chip holder, then play a bit, then unplug the AVR holder, then replug the SD card... My prototype for a SPI relay design is built, but I haven't tested it yet. I need to adapt the code first, which is what I do here. When the prototype is tested, I'll update the SDC recipe with a new schema.
2020-09-17 23:36:16 +10:00
: asp$ ( spidevid -- )
( RESET pulse ) DUP (spie) 0 (spie) (spie)
Add word TICKS Adding a delay such as the 20ms one we have in AVR programmer's initialization routine is tricky without a word like TICKS. This implementation is highly inaccurate, but more accurate and reliable than a "ballpark" DO..LOOP...
2020-09-26 07:31:06 +10:00
( wait >20ms ) 220 TICKS
avr: allow writing to flash
2020-09-06 04:07:13 +10:00
( enable prog ) 0xac (spix) DROP
0x53 _x DROP 0 _xc DROP 0 _x DROP ;
: asperase 0 0 0x80 0xac _cmd asprdy ;
Reference in New Issue Copy Permalink