I found some situations where deleting the .bin file used to program the uC will be useful for several reasons, one of them is, simply, to save disk space. In my application, the user will not connect the mbed through the USB link provided by the kit, but through the USB connection provided by the uC, and firmware updates will be done using this connection too; after that, the .bin file could be removed, as it has no further utility. Obviously, I understand that if the uC has no program loaded, releasing the reset when no binary is found by the interface could lead to imprevisible behaviour. However, I think this is not harmful, so why don't release reset even if no binary is found? What do you think guys?
I found some situations where deleting the .bin file used to program the uC will be useful for several reasons, one of them is, simply, to save disk space. In my application, the user will not connect the mbed through the USB link provided by the kit, but through the USB connection provided by the uC, and firmware updates will be done using this connection too; after that, the .bin file could be removed, as it has no further utility. Obviously, I understand that if the uC has no program loaded, releasing the reset when no binary is found by the interface could lead to imprevisible behaviour. However, I think this is not harmful, so why don't release reset even if no binary is found? What do you think guys?