Wed Jul 4 16:02:52 CEST 2007
maybe it's best to reserve some functionality for chip erase, so i
don't need to worry so much about messing up the bootsector. basicly,
just need a single piece that never changes, which has the ability to
influence the booting process to run the interpreter. probably an 'ack
bang' or something?
- keep boot sector free for fast isr
- reserve 2nd block for reset vector?
seems the core of the problem is that boot vector and isr vectors are
in the same block. what if:
- default reset vector = jump to second block
- add an application vector after this
- second block contains some kind of checking code to determine
activation of application or debugger