When I am trying to connect EFR32MG12P432F1024GM48 from simplicity studio with the help of WSTK then simplicity studio displays error as :-

"Could not connect to debugger"

Tried every possible ways but unable to detect the board.

Attached is the screenshot of recovery board command output.

 

Since the new update 2.7.0.0 (from 2.6.something), I frequently get an error "Error while opening a device: Cannot connect to J-Link via USB" when connecting. This is annoying, because the error occurs more often than successful connections.

If that happens, the flash upload stalls and fails ( even the simplicity commander freezes on access).

Many (not all) times, the debug adapter even has to be disconnected from USB and reconnected again to be identified in the debug adapter section of simplicity after restart of simplicity after such incidents.

In simplicity commander, the first step (connecting to the board) sometimes (yes only sometimes) works. If the first step works,  the commander often stalls after I press Target Connect. After some times shows "commander is not responding", where I have to choose "force quit".

It even happens on two different computer with different kernel versions and on several different boards with the newest adapter firmware... Any idea what's wrong? What has been changed between the releases?

 

I am using the BRD4001 board sn 161614298 with WGM160P

I try to use the energy profiler but when it start it ask to upgrade the J-link firmware

Current 0.14.3.471

but the upgrade procedure can't find the new firmware

Also from main page in simplicity studio the new firmware download fail

 

Hi

Just getting started with the BGM13p22 Blue gecko and the wireless Starter kit mainboard

I'm looking for a document/tutorial or guide that explains how to program with Simplicity Studio. On how to, for example, program a gap to act as a clock signal, or to send a number bit by bit, or to detect when a button is pressed and output a high signal.

Also, where can I find the HTM example program documentation?

Thanks in advance

 

 

Hello,

I am using the wireless starter kit mainboard development board for the BGM111, after uninstalling Simplicity Studio and getting the update of December 2019 the programming of my modules became really slow! Either for external modules (programmed through the the debug adapter and mini interface) or the onboard module from the starter kit.

I tried on several computers and the same thing is happening all the time: instead of loading the program on the BGM111 in instants, it taking every time exactly 2 minutes...

On another computer with an older version of Simplicity Studio, everything is running just fine, how can I solve that issue?

I tried to get back to older version of Simplicity but it seems impossible due to the installer downloading the IDE online, is it even possible to get back to an older version?

Thank you.

Hello,
I own a custom PCB with a BGM113 device. The PCB exports the SWDIO, SWCLK, RESET signals to a connector.
How can I flash the device using an external JLINK-Base?

please tell me the steps to follow to get the license for Evaluation version

Hello,

I am trying to get set up with my new BGM210P module and am having some issues getting my program (developed on the starter kit) running on it. The first issue I ran into was the RTCC was hanging as described in this post here: https://www.silabs.com/community/software/simplicity-studio/forum.topic.html/real_time_clock_lockingup-iBvt I modified the register to use the LFRCO in the rtcdriver.c file and also added the code to disable the LFXO in the init_mcu.c file.

The program no longer hangs due to the RTCC but now the program never leaves the OSStart() function. I stepped through it and it seems to be hanging on the semaphore waiting for the tick interrupt in os_tick.c. It looks like it never receives the tick interrupt. I have also tried also uncommenting the lines in init_mcu.c to use the LFRCO for other clock sources with no luck. 

static void initMcu_clocks(void)
{
  // Initialize HFXO
  initHFXO();

  // Set system HFXO frequency
  SystemHFXOClockSet(BSP_CLK_HFXO_FREQ);

  CMU_ClockSelectSet(cmuClock_SYSCLK, cmuSelect_HFXO);

  //Fixes as of this post: https://www.silabs.com/community/software/simplicity-studio/forum.topic.html/real_time_clock_lockingup-iBvt
  //Explicitly disable LFXO (Needed for these modules too)
  CMU_LFXOInit_TypeDef lfxoInit = BSP_CLK_LFXO_INIT;
   lfxoInit.disOnDemand = 1;
   CMU_LFXOInit(&lfxoInit);


  //To use PLFRCO please remove commenting of these lines
  //and comment out or delete the LFXO lines if they are present
  //If using PLFRCO update gecko_configuration_t config's
  //.bluetooth.sleep_clock_accuracy to 500 (ppm)
//  #if defined(PLFRCO_PRESENT)
//    /* Ensure LE modules are accessible */
//    CMU_ClockEnable(cmuClock_CORELE, true);
//    /* Enable PLFRCO as Low frequency clock source in CMU (will also enable oscillator if not enabled) */
//    CMU_ClockSelectSet(cmuClock_RTCC, cmuSelect_PLFRCO);
//    CMU_ClockSelectSet(cmuClock_EM23GRPACLK, cmuSelect_PLFRCO);
//    CMU_ClockSelectSet(cmuClock_EM4GRPACLK, cmuSelect_PLFRCO);
//    CMU_ClockSelectSet(cmuClock_WDOG0, cmuSelect_PLFRCO);
//    CMU_ClockSelectSet(cmuClock_WDOG1, cmuSelect_PLFRCO);
//  #endif

  #warning "WARNING: Use the CMU_LFXOInit() function only if the LFXO hardware is actually present!"
  // Initialize LFXO
  //CMU_LFXOInit_TypeDef lfxoInit = BSP_CLK_LFXO_INIT;
  //CMU_LFXOInit(&lfxoInit);
  // Set system LFXO frequency
  //SystemLFXOClockSet(BSP_CLK_LFXO_FREQ);

  #warning "WARNING: Make sure LFXO is present when using it as a clock source for these modules!"
  // Select LFXO as low frequency clock source
//  CMU_ClockSelectSet(cmuClock_RTCC, cmuSelect_LFRCO);
//  CMU_ClockSelectSet(cmuClock_EM23GRPACLK, cmuSelect_LFRCO);
//  CMU_ClockSelectSet(cmuClock_EM4GRPACLK, cmuSelect_LFRCO);
//  CMU_ClockSelectSet(cmuClock_WDOG0, cmuSelect_LFRCO);
//  CMU_ClockSelectSet(cmuClock_WDOG1, cmuSelect_LFRCO);
// Tried uncommenting the 5 lines above with no luck


}

I am not sure why the os is not getting its tick interrupts. I am using the BGM210P32 module with no external crystals. Help with this would be greatly appreciated.

I think we started with the range test project and it has been working fine on one board, but on other ( identical ) boards, it hangs up trying to initialize the real time clock.  RTCC_Init() has the following code:

  if (RTCC->EN != 0U) {
    RTCC_SyncWait();
  }

That looks to me like it is saying that if the RTC is already enabled, wait forever until it magically disables itself.  This code should always lock up, but for some reason, it works fine on the first board.  How can this be?  Why does this code appear to be broken?  I thought that the code was meant to try clearing RTCC->EN to zero, and then wait for it to read back as zero, so I added RTCC->EN = 0, and some unhandled interrupt appears to happen and vector to the default empty interrupt handler.  I also noticed that CMU->RTCCCLKCTRL is supposed to default to a value of 1, but instead has a value of 2, which appears to mean it should use an external 32khz crystal, but there is no such crystal connected.  I don't see anywhere in the application that is setting this register.

 

Simplicity Studio keep asking to update AN0822 even I have pressed updated button. How to fix this update issue?

Hello, I already have a code in Arduino but I need to use Simplicity so I need help to translate the Arduino code into the Simplicity language so I have 2 options to do it, I don't know if they work
1- Copy exactly the same code I have in Arduino to Simplicity.
2- Import the HEX file produced by Arduino and open it in Simplicity.

Other option could be translate the Arduino code into the Simplicity Studio Language but I don't know how to declare  inputs or outputs to the pins of the module that I'm using, I don't know if it is the same way like Arduino.

Hi,

I am trying DMP example.

When i clicked generate on appbuilder, it make error.  

How to solve it? 

Thank you.

 

 

Hey

I have a problem to debug a BGM113 bluetooth module with the EFR32 on it. My IDE is Simplicity Studio V4.

With my own code it doesn't work. The debugger don't have any breakpoints and it seems that it stucks in a loop. It comes out of the blue because yesterday it works fine.

The debugger works fine with a code example for adc for the EFM32PG1B on the same device with the same setup. I think it will be a settings problem.

When I try to generate a new empty-soc the debugger also skipp breakpoints and I have the same issue like I have in my own code. I tried to attach my code and the working example code but it does not load and the attached file appears in grey.

My problem is very similar to this problem but I set the SWD and the debug level to -g.

https://www.silabs.com/community/software/simplicity-studio/forum.topic.html/can_t_debug_withsim-0pUy

What could it be that the debugger not even works with the generated empty-soc example code?