This has probably happened to many of you more than once. You develop this really cool circuit design for the 08M . . . but you need one more input. Just one. Maybe just an interrupt.
So . . . I wonder if this would be possible. As it is now, the bootloader software is constantly on the look-out, (on pin 2), for a serial input. I assume its done through an interrupt. It checks to see if it was a proper download code, and if so, accepts the download from the host computer. If it isn't, it resumes wherever it was interrupted from.
What if . . . instead of doing nothing if the code was something else, it just sets a special internal variable. Or, better yet, just passes the interrupt along to the current program. It would be a special interrupt. You wouldn't need to check to see what the data was. Just the fact that "something" happened was all you need. Like an external "trigger" of sorts. You could use that input to sense for some external event, and then send your code into action, without needing to use any of your 5 I/O's.
It seems like a simple mod to the bootstrap code could do this. Maybe.
So . . . I wonder if this would be possible. As it is now, the bootloader software is constantly on the look-out, (on pin 2), for a serial input. I assume its done through an interrupt. It checks to see if it was a proper download code, and if so, accepts the download from the host computer. If it isn't, it resumes wherever it was interrupted from.
What if . . . instead of doing nothing if the code was something else, it just sets a special internal variable. Or, better yet, just passes the interrupt along to the current program. It would be a special interrupt. You wouldn't need to check to see what the data was. Just the fact that "something" happened was all you need. Like an external "trigger" of sorts. You could use that input to sense for some external event, and then send your code into action, without needing to use any of your 5 I/O's.
It seems like a simple mod to the bootstrap code could do this. Maybe.