Tags
- Wireless
- RF Hardware
- EFR32MG1P232F256GM48
- EFR32MG21 Series 2 SoCs
- Proprietary
- Development Environments
- ETRX357
- Zigbee SDK
- ZigBee and Thread
- Connect SDK
- Software Development Kits
- Blue Gecko Bluetooth Low Energy SoCs
- 32-bit MCUs
- Bluetooth Low Energy
- Gecko SDK
- Zigbee and Thread Kits
- EFR32MG1P132F256GM48
- Telegesis Legacy Modules
- RF Synthesizers
- Flex Gecko
- Knowledge Base Articles
- Simplicity Studio
- Telegesis ETRX Driver
- EFR32MG21 Series 2 Modules
- EFR32MG22 Series 2 SoCs
- Software
- Mighty Gecko SoCs
- MGM111A256
Top Authors
Archives
- 2016 March
- 2016 May
- 2016 June
- 2016 July
- 2016 September
- 2016 November
- 2016 December
- 2017 January
- 2017 February
- 2017 March
- 2017 April
- 2017 May
- 2017 June
- 2017 July
- 2017 August
- 2017 September
- 2017 October
- 2017 November
- 2017 December
- 2018 January
- 2018 February
- 2018 March
- 2018 April
- 2018 May
- 2018 June
- 2018 July
- 2018 August
- 2018 September
- 2018 October
- 2018 November
- 2018 December
- 2019 January
- 2019 February
- 2019 March
- 2019 May
- 2019 August
- 2020 February
- 2020 March
- 2020 April
- 2020 May
- 2020 June
- 2020 July
- 2020 August
- 2020 October
- 2020 November
- 2020 December
- 2021 January
- 2021 February
Are all EFR32 series 1 parts of the same package variant pin-compatible?
Question
Are all EFR32 series 1 parts of the same package variant pin-compatible?
Answer
No. The pin-outs are dependent on frequency band: Sub-G Band, 2.4G Band, and dual-band (Sub-GHz and 2.4GHz). Using EFR32FG1 QFN48 as an example, per the datasheet (http://www.silabs.com/Support%20Documents/TechnicalDocs/EFR32FG1-DataSheet.pdf) section 6 shows the pin definitions per package type and variant. Figure 6.1 shows the QFN48 sub-GHz pin-out, Figure 6.2 shows the QFN48 2.4GHz pin-out, and Figure 6.3 shows the QFN48 dual-band pin-out. All 3 pin-outs differ for pin function of pin numbers 13 through 21. And other pins' definitions are the same. The pin definition differences are listed as below: