English is currently available.
Other Microcontrollers DISCUSSION
A design needs an alternative MCU because the original part is difficult to obtain. Beyond flash, RAM and clock frequency, which hardware and software differences should be included in the compatibility review?
Reference: Zephyr: board porting guide (https://docs.zephyrproject.org/latest/hardware/porting/board_porting.html).
Compare package and pin functions, supply and I/O limits, analog characteristics, timers, DMA routing and clock sources. Similar marketing specifications do not establish electrical or behavioral compatibility. Identify which requirements are essential and which can tolerate a redesigned interface.
Review compiler and debugger support, peripheral drivers, bootloader behavior and the update process. Check persistent-data layout and externally visible protocol timing. A new controller that passes a simple benchmark can still break an established field-update or calibration workflow.
Prototype the highest-risk interfaces first and build a migration checklist from measured results. Keep the previous implementation as a reference for expected behavior, while validating against the actual product requirements. Document every required PCB, firmware and production-test change before declaring the replacement ready.
Back to Other Microcontrollers community
