Explore >> Select a destination
|
You are here 
|
blog.fahhem.com | ||
| | | | |
ciesie.com
|
|
| | | | | You programmed STM32 microcontroller using Nucleo or Discovery boards. That means you used Serial Wire Debug (SWD) for programming/debugging. Now, you are designing a PCB with a STM32 microcontroller on it, which means you have to be able to program it. One solution is uploading the code through a bootloader - a small piece of software, made by ST that has been saved in the protected (read-only) memory of the microcontroller. | |
| | | | |
cybergibbons.com
|
|
| | | | | Last time we looked at using the SWD interface of an STM32 ARM chip. This isn't the only way we can interact with this device though. It also contains a serial interface on the bootloader tha... | |
| | | | |
8051enthusiast.github.io
|
|
| | | | | [AI summary] The blog post delves into the intricacies of an embedded controller (EC) firmware, exploring its architecture, memory management, and communication protocols. Key points include the use of SHA-1 for battery authentication, the EC's ability to reprogram itself via SRAM mapping, and the challenges of writing to flash due to checksum constraints. The author also discusses the discovery of a silicon bug in the memory mapping and the development of a tool to facilitate custom code execution on the EC. | |
| | | | |
www.abubalay.com
|
|
| | | |||
