hi ArmandR,

Here is a simple draft example code, it can route the output of VDAC to PB12.

However, there is an errata VDAC_E201 below related to VDAC. When VDACn_OPAx_OUT.APORTOUTEN is set, the VDACn/OPAx will drive all its connected APORT buses (BUSAY, BUSBY, BUSCY, and BUSDY) instead of only the APORT bus selected via APORTOUTSEL.
https://www.silabs.com/documents/public/errata/efm32pg12-errata.pdf

If none of the other APORT clients (e.g. ADC, ACMP, OPAx input muxes, etc.) use BUSAY, BUSBY, BUSCY, and BUSDY, then no problem exists and the potential simultaneous driving of these buses by VDACn/OPAx can be ignored.

Alternatively, the VDACn/OPAx can be configured to use direct connections of its main or alternative outputs to certain pins, thereby bypassing the APORT. Direct output connections can be enabled by programming MAINOUTEN=1 and/or ALTOUTEN=1 (while keeping APORTOUTEN=0) in the VDACn_OPAx_OUT register. The device data sheet lists the available main output and alternative output connections to pins per VDAC output or OPAMP.

And I will also suggest to adopt the main output or alternative output connections.

Thanks

hi Jean,

We have some resources that can help as examples of how to integrate the mbedTLS library into your Simplicity Studio projects for the EFM32PG1B (the example also can work with EFR32BG1B). First, there is the application note AN0955. Additionally, in Simplicity Studio SDK, the "SLSTK3401A_aescrypt" and "SLSTK3401A_ecdsa" example projects for the Pearl Gecko Starter Kit demonstrate the integration of the mbedTLS library into a Studio project.
https://www.silabs.com/documents/public/application-notes/AN0955.pdf

Thanks

hi Renee,

We do have provide the USB HID example for EFM8UB1 within the SDK, you can find the examples after install the Simplicity Studion and 8051 SDK.
C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\8051\v4.x.x\examples\EFM8UB1_SLSTK2000A\USB

Thanks

In general, the reason of popping the wrong message "Error Getting Data From Hex File" is that the USBBootloader.exe cannot read the Hex image and store it into the software memory correctly. It will assert the first byte as ':', and then read the length/offset information, and then process the data depend on the record type, what the supported record type is 0x00 and 0x01.
Did you compare the Hex files generated by the LX51 and BL51, it's better to upload these two Hex files here for our investigation.

Thanks

Also can take a look at the AN447 to get more information about the printed circuit design. BTW, I will suggest to monitor the raw data with the Capacitive Sense Profiler to work out a reasonable active or inactive threshold setting for your overlay.
https://www.silabs.com/documents/public/application-notes/AN447.pdf

hi,

You can try to close the connection refer to the code below if need to reject the connection (bond).

 case gecko_evt_le_connection_opened_id:
   if(evt->data.evt_le_connection_opened.bonding == 0xFF && bondable == 0)
   {
    gecko_cmd_endpoint_close(evt->data.evt_le_connection_opened.connection);
   }
 break;

Take a look at the post below for more information.
https://www.silabs.com/community/wireless/bluetooth/forum.topic.html/bgm121_how_to_reject-FDTj

Thanks

You should install the Gecko Platform SDK within Simplicity Studio, and then refer to the UG266 and AN1084 for how to get start with the bootloader.

https://www.silabs.com/documents/public/user-guides/ug266-gecko-bootloader-user-guide.pdf
https://www.silabs.com/documents/public/application-notes/an1084-gecko-bootloader-emberznet-silicon-labs-thread.pdf

Make sure that you have installed the Micrium OS correctly. You should be able to find the network related source code here.

C:\SiliconLabs\SimplicityStudio\v4\developer\sdks\gecko_sdk_suite\v2.2\platform\micrium_os\net\source