Silicon Labs maintains different SDK lines, and the newest package name is not enough to choose a migration target. What should an existing wireless project check before moving its board and protocol stack to another SDK?
Silicon Labs MCUs DISCUSSION
Simplicity SDK or Gecko SDK: which branch belongs in an existing Silicon Labs project?
3 replies
248 views
4 participants
Latest activity · 27 Sep 2026Simplicity SDK or Gecko SDK: which branch belongs in an existing Silicon Labs project?
Re: Simplicity SDK or Gecko SDK: which branch belongs in an existing Silicon Labs project?
#2Identify the exact device series and read the supported-device list. The current vendor information distinguishes Simplicity SDK from the Gecko SDK line used for older Series 0 and Series 1 devices. Do not assume that a tool installation's newest SDK supports every earlier chip.
Re: Simplicity SDK or Gecko SDK: which branch belongs in an existing Silicon Labs project?
#3Review protocol-stack changes, generated configuration, bootloader compatibility and persistent data formats. Preserve a reproducible build of the working release. Upgrade a small board example first so device support and programming can be checked independently of the full application.
Re: Simplicity SDK or Gecko SDK: which branch belongs in an existing Silicon Labs project?
#4Run functional tests for commissioning, reconnects, stored credentials and firmware recovery after the migration. Compare flash and RAM use as well as radio behavior. A successful compilation does not demonstrate that existing deployed devices can safely accept the new image.