Another possibility to handle current hardware version is to use the bootloader + OTP area to save the hardware version when it is produced. When updating the firmware of the device through the bootloader, the version number of the hardware for which this software is provided is transmitted along with the firmware. In case of a mismatch, the bootloader simply will not accept the downloaded firmware.
Yes, that's definitely a possibility to consider if you got a dedicated bootloader. Reading this OTP area could also serve as a runtime check in your application code. Burning the hardware version into read-only memory is generally something to consider instead of encoding it with GPIOs/ADC-pin. I don't think my msp430 has any write-protected area for this purpose, but I could perhaps have demonstrated the principle by setting aside a byte in my flash memory, i.e. by modifying my linker script.
![Learning C - Build Your Own Lisp [1]](http://i.ytimg.com/vi/HaLpOku7u_E/mqdefault.jpg)
Another possibility to handle current hardware version is to use the bootloader + OTP area to save the hardware version when it is produced. When updating the firmware of the device through the bootloader, the version number of the hardware for which this software is provided is transmitted along with the firmware. In case of a mismatch, the bootloader simply will not accept the downloaded firmware.
Yes, that's definitely a possibility to consider if you got a dedicated bootloader. Reading this OTP area could also serve as a runtime check in your application code.
Burning the hardware version into read-only memory is generally something to consider instead of encoding it with GPIOs/ADC-pin. I don't think my msp430 has any write-protected area for this purpose, but I could perhaps have demonstrated the principle by setting aside a byte in my flash memory, i.e. by modifying my linker script.
♥
❤
Bra !
🤗
Can you please use comic sans on when you are writing code? Is so much easier to read.
😡