3 ms·
A lot of embedded programmers don’t come to it in any formal way. They’ll make it to shipping a product without ever having heard about the idea of blowing the
by Tarragon 6y ago
A lot of embedded programmers don’t come to it in any formal way. They’ll make it to shipping a product without ever having heard about the idea of blowing the security fuses.
For those that do know to do it it’s different. Before you blow the fuses you need to to be damn sure of your bootloader and that you will never want to debug something in the field.
A lot of companies don’t give you the time before putting it into production. Then once it’s in production you work on the next product instead of hardening the last one.
- pantalaimon 6y agoIt's also a big hassle and if you have nothing to hide, why go through the effort?
- acka 6y ago(Supposed) FCC regulations[0]. To prevent users from using non-compliant firmware on their devices, i.e. locked bootloader which will only boot OEM-supplied signed firmware. [0] https://www.wired.com/2016/03/way-go-fcc-now-manufacturers-locking-routers/ https://www.wired.com/2016/03/way-go-fcc-now-manufacturers-l...