STARTUP & FIRMWARE UPDATES
Boot, updates & recovery
CAN-based bootloader software covering programming, integrity validation, recovery and application handover.
Implemented softwareImage integrity and cryptographic authenticity are distinct.
Separate responsibilities, explicit decisions
Boot control, update-protocol handling, hardware abstraction and peripheral access are separate responsibilities. Firmware transfer over CAN feeds flash programming; integrity and entry checks determine whether control can pass to the application.
Failure and recovery
Error and recovery paths remain explicit in the design. The public flow summarises the documented responsibilities without exposing private memory layouts or protocol details.
Integrity is not authenticity
The evidenced checks concern image integrity. Cryptographic authentication, signing and key management are separate requirements and are not claimed for this implementation.
This is an anonymised example of our founder’s engineering experience across client programmes, including previous employment. It describes the stated software contribution, not ownership of the whole programme. Experience and attribution
LET’S GET SPECIFIC
Have a similar engineering challenge?
Share the target hardware, the software baseline, the current blocker and the release date. We establish access and dependencies, then propose a review or implementation package.