Hi Guys,
for me one of the most frustrating things in the early days was waiting for UVEPROM's to erase so i could write the new or modified piece of code onto it to be tested in a system. when bug testing this can be fairly time consuming unless you have a substantial number of UVEPROM to keep circulating through the UV Eraser. i know some people write a new piece of code back into memory via a monitor and RS232, some people write and compile to a COM files for use with CP/M etc. i bring up this topic because for me i dont really use monitor programs and really just write a piece of code todo something specific. so after my last system "melt down" i chose to stry solve this issue for the future, which lead me to develop a bit of a frankenstein board that uses flash memory, cpld's, 7400 series, SRAM & a UVEPROM with a "bios" to load whatever "new piece of code" into a specific memory range on startup, whatever that code my be, a buggy monitor, a new routine, cp/m, application specific routine, load machine code for a bus master to take over etc.. im just curius to know what are other people are using these days to save development time and frustration?
Regards,
Ants