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.

Hello,

I am curious if there is any progress in this matter. I've just checked the latest firmware in a WSTK and it still does not support setting the baudrate from the USB VCOM.

Silicon Labs, please do something about this. This is getting ridiculous.

Hello,

Simplicity Studio contains a code analysis tool, but it refuses to accept a static_assert() as valid syntax even though I have already set the C compiler dialect to ISO C11. Is there a way to tell the code analyzer that I'm using C11?

Maarten

setjmp/longjmp is standard C. I see no reason why Keil would leave it out. I'm sure you could have included and/or opened setjmp.h to find this out.

But be sure to know what you're doing. longjmp can only be called downstream from setjmp in the calling tree. It expects the stack frame above setjmp to be intact.