hi Valter,

The user guide of Simplicity Studio provides much more information about how to create / import / build the projects, it may helps.
https://www.silabs.com/documents/public/application-notes/AN0822-simplicity-studio-user-guide.pdf

Simply speaking, import the projects with the steps "File" -> "Import" -> select the folder of the simplicity studio project file -> "Next" -> "Finish", and then build it.

The simplest way is making the STK/WSTK stay in EM4 (consume few nA of current), and then power your target board with VMCU of the STK/WSTK board.

https://www.silabs.com/community/mcu/32-bit/knowledge-base.entry.html/2014/05/21/using_aem_to_measure-BdWl

The simplest way is making the STK/WSTK stay in EM4 (consume few nA of current), and then power your target board with VMCU of the STK/WSTK board.

hi Billyw,

I tried to reproduce the symptom what you described above, set the watchdog period around 32 seconds, and select the warning timer as 75% of the watchdog timeout (around 24s). However, the warning interrupt never be triggered.
Please check the enclosed main.c, and tell me if you still can reproduce the symptom.

Thanks

hi Valter,

The readme.txt file under each project folder provided detailed explanation on how to use the peripheral examples. For example, the readme here explained the purpose of the project, and show you how to test it on different STK/WSTK.
https://github.com/SiliconLabs/peripheral_examples/tree/public/gpio/switch_led_polled

Thanks

I2CSPM_Init_TypeDef is a typedef, during the I2C master initialization, it will pass the I2CSPM_Init_TypeDef type variable to the function I2CSPM_Init() rather than the typedef. You can customize the variable as Devner mentioned above.

Looks like there is a similar discussion in another thread here.
https://www.silabs.com/community/wireless/bluetooth/forum.topic.html/debug_error-UfZ7

This "Unexpected DW_OP 243" issue is related to the debugger trying to peek the state of the application by tracking variable values etc. Please try to change the optimization level to -O0 (none) and check it angin.

Do you need to use the NVM3 with Zigbee application or Bluetooth application ?
AN1135 explained how to use it in Zigbee applications.

The tutorial is a good starting point for understanding how to control the gpio, how to enter energy mode. However, the example based on series 0 devices, few of the registers (e.g. GPIO_CTRL, GPIO_CMD) in the example were deprecated or replaced with other ones for BGM13P.
As Delu mentioned before, we will suggest to start your project with the latest peripheral examples.

for example, erase the bootloader region with the commander below. Refer to 5.9.2 of the UG162.

commander device pageerase --region @bootloader