Hey Mario,

The assetEFM() that you're reaching should provide you with some information on what is causing the hang. Can you step through each statement within sl_cli_command_execute? 

I also need a lot more information about your application. Are you using Simplicity Studio V5 or V4? I am guessing V5, but please confirm. What example are you basing this code on? Do you have any wireless stacks enabled? 

More information about CLI commands - https://docs.silabs.com/gecko-platform/latest/service/api/group-cli#gae1309199325e0fb0a912f5fef51221b8

Hi,

Im using gecko SDK 2.7.4 for EFR32BG13P732F512GM32.

when i using  gecko_cmd_hardware_set_soft_timer (32768*5, 0x01, 1); 

Theoretically after 5 seconds the gecko_evt_hardware_soft_timer_id event would run but it did run immediately.

When i use Gecko SDK 1.1.1 it works normally.

Did I miss somethings?

Thanks!

Hey Ralf,

I am able to open the link attached by Denver. I have attached an image of the KBA here if you still cannot open it. 

 Have a look at https://www.silabs.com/developers/8-bit-8051-microcontroller-software-studio#flash

The Flash Programming Utilities allow you to download your code to a device and perform other memory operations without needing to use the Silicon Labs IDE or Simplicity Studio. These utilities are static examples of the C8051Fxxx On-Chip Interface Utilities DLL detailed in application note AN117. The downloaded installation utility installs both the Windows Flash Programming Utility and the Command-line (32-bit) Flash Programming Utility.

https://www.silabs.com/Support%20Documents/Software/FLASHUtil_rel_notes.txt

That has a DLL that communicates with SiLabs debug firmware to program flash. We have a FlashUtilCL.exe that can be used if needed by your system and you can roll your own error reporting.

For other production programming options, this webpage should help - https://www.silabs.com/mcu/programming-options

NK,

The return values listed in AN433 include only those errors that are set within the interface library; AN433 does not list the errors that are generated by the CP2114 device and simply passed through the library to the app code.

Is the return value in decimal? I am going to assume it is for now. Table 5.4 in AN433 has a list of all possible status values and 38d = 0x26. This is corresponding to HID_UART_BOOT_INDEX_UNCHANGED.

The CP2114 status is sticky, i.e. any error set by the firmware will persist until the CP2114_GetDeviceStatus function is called. This error is returned if the boot index is already stored in the OTP. It is possible that you're trying to set the boot config to the same value two times in a row. 

NK,

The return values listed in AN433 include only those errors that are set within the interface library; AN433 does not list the errors that are generated by the CP2114 device and simply passed through the library to the app code.

Is the return value in decimal? I am going to assume it is for now. Table 5.4 in AN433 has a list of all possible status values and 38d = 0x26. This is corresponding to HID_UART_BOOT_INDEX_UNCHANGED.

The CP2114 status is sticky, i.e. any error set by the firmware will persist until the CP2114_GetDeviceStatus function is called. This error is returned if the boot index is already stored in the OTP. It is possible that you're trying to set the boot config to the same value two times in a row. 

Hey Adrian,

Are you using a WSTK or a custom board?

I was looking at your HFXO initialization code. I don't see where you have enabled the HFXO oscillator? Please try to make sure you have all the items below implemented in your HFXO initialization code - 

void initHFXO(void)
{
  // Initialization structure for HFXO configuration
  CMU_HFXOInit_TypeDef hfxoInit = CMU_HFXOINIT_DEFAULT;

  // Apply board specific tuning capacitor values
  hfxoInit.ctuneXiAna = HFXO_CTUNE_VALUE;
  hfxoInit.ctuneXoAna = HFXO_CTUNE_VALUE;

  // Configure HFXO settings
  CMU_HFXOInit(&hfxoInit);

  // Set system HFXO frequency
  SystemHFXOClockSet(HFXO_FREQ);

  // Enable HFXO oscillator, and wait for it to be stable
  CMU_OscillatorEnable(cmuOsc_HFXO, true, true);
}

Your DCDC initialization looks good to me. Can you first try to change the HFXO initialization and let me know if that fixes the issue? 

Hi,

I am using Thunderboard(EFR32BG22).  I'm working on SoC_Thundeboard.  My requirement is that,

I need to constantly check the light value from the light sensor. When the light value reaches certain point, my thunderboard should advertise and ready for the connection if requested.

during the advertising I should check the light value and if it reaches certain point again It should stop advertising.

I'm not able to do both the tasks at a time.

when the control goes to the app.c , its not going to main function.

How can I achieve this?

  while (1) {
	SI1133_measureLuxUvi(&lux,&uvi);
    if(lux < 200)
	{
    struct gecko_cmd_packet* evt;
    evt = gecko_wait_event();
    appHandleEvents(evt);
    }
    if(lux > 300)
	{
      do something
    }
    
  }