It's almost identical to what happened to me with the SDK 2.5.1 update.

https://www.silabs.com/community/software/simplicity-studio/forum.topic.html/update_killed_emlib-kMo7

I had to jump through the same hoops to get it properly installed.

What might be related is that I have a project in my workspace that builds emlib and emdrv into a static library.

Hello,

Am I once again the only one to experience this that after updating the Gecko SDK from 2.7 to 2.7.1 there no longer is an emdrv folder in sdks/gecko_sdk_suite/v2.7/platform ?

Maarten

I'm using the GNU ARM v7.2.1

The question mark says I have a Syntax Error.

But now I see, that sometimes it is recognized correctly. Maybe it has to do with building a Static Library or building an Executable?

I'm using the GNU ARM v7.2.1

The question mark says I have a Syntax Error.

The WSTK only supports a change of baudrate through a telnet session. That is really not good enough. I want to be able to run an application on the PC and be able to change the baudrate on both the PC and the MCU during execution. Any decent USB-UART implementation lets you do this through normal serial port functions. But for the STK or WSTK you must jump through all sorts of hoops.

I'll explain the use case: I want my bootloader to start at 9600 baud to spare the battery. But once a connection is made I want to go to a high baudrate. And currently I cannot debug this bootloader because the UART on the (W)STK is so limited.

The WSTK only supports a change of baudrate through a telnet session. That is really not good enough. I want to be able to run an application on the PC and be able to change the baudrate on both the PC and the MCU during execution. Any decent USB-UART implementation lets you do this through normal serial port functions. But for the STK or WSTK you must jump through all sorts of hoops.

I'll explain the use case: I want my bootloader to start at 9600 baud to spare the battery. But once a connection is made I want to go to a high baudrate.