| ??? 02/09/07 13:47 Read: times |
#132361 - development Responding to: ???'s previous message |
As I have said on this site about 5 times, I do NOT want to make a separate programmer, because then I have to remove the rom everytime I change the code, and the chances of me changing code are high. If chances of changing code are high, that means you are still developping code... I would hence say you need a development system. If you code changes frequently, use a SRAM to store your code. You would not even need a battery backup, as you will have your SRAM-loader (carefully ommiting "bootloader" as you don't seem to like them) handy anyway, allowing you to quickly load your code into SRAM after power on. What I want happening under the worst case scenario is for the system to allow programming, even if all the eeproms were not programmed or even not inserted. I do not want to depend on an EEPROM for programming operations. Then use SRAM with a "monitor system" in EPROM/FLASH... or any other ROM-type... See http://www.pjrc.com/tech/8051...dware.html for a minimal low cost system... or any other 8052 development system... Once your software is stable, program your eprom or eeprom or earom or flash, and go on to the next challenge.. again: When software needs to be changed often, it's due to development.. and what's better to use than a development system when developping software... When devlopping QBasic or php you would not save your qbasic sources or php programs on a (rewritable) CD at each step, you would use a hard disk wouldn't you? Once it is fairly stable, then you save your sources on CD... regards Patrick |
