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
2G4RF_ION pin connection on EFR32 Series 1 devices
Question
What is the correct connection of 2G4RF_ION pin on EFR32 Series 1 wireless MCUs?
Answer
On EFR32 Series 1 wireless MCUs 2G4RF_ION pin should always be connected to the ground. The external L-C matching network should be connected to 2G4RF_IOP pin.