| PM | Quote | Reply | Full Topic |
| Joined: | Wednesday Sep 22nd, 2010 |
| Location: | United Kingdom |
| Posts: | 22 |
| Status: |
Offline
|
Oh my mistake. I understand the eeprom I mentioned is 256K bits not bytes.
That said couldn't you save part of the firmware to U3 (ie the download/upload code part), then if you had similar in future you could get the customer to set memory address xxxx as 1 and restart and it would at least allow a new firmware to be uploaded.
A neater solution for the general UCM would be to have just enough code inside a protected bootloader that never gets reflashed to accept a UCM firmware over the USB/Ethernet/RS232 port. The PC interface is just serial from the point of view of the UCM uC so the actual module attached doesn't affect anything.
The bootloader would only be capable of loading a new firmware and running whatever is in flash. You'd trigger recovery mode by doing something unusual like plugging in the UCM whilst some odd combination of jumpers is shorted or holding down a button. As the bootloader always runs first then you should be able to recover from a bad flash assuming it hasn't affected the bootloader itself.
| Close Window |