Here's a project on the MG12 using version 2.7 of the SDK:

2.- I see there has been deleted a lot of files regarding I/O and BSP and so on in Micrium OS files, if I need to use those functionalities I should just keep those files, right?

You should be able to keep the files. Which ones do you need and to what purpose?

Regards,

Janos

Hi Davide,

Can you send me your application file so that I can try and replicate the behavior on my side?

Also, was this a project you created from v2.7.0 or is it one that you are migrating from an older SDK and used to work fine?

Thanks,

Janos

Hi Davide,

Which version of the Gecko SDK are you using in your project?

Hi Aleksandr,

In order to support context switching in a multi-task application, each task must have its own stack—use of the C stack alone, as in a single-task application, is not feasible. Micrium’s applications typically rely on the C stack in main(), but afterwards, once multi-tasking operation has begun, they make use of the task stacks. In these applications, each time the kernel passes control of the CPU to a new task, it loads the stack pointer register to reference that task’s stack.

Unfortunately, there is not, at the current time, a mechanism by which IAR’s Embedded Workbench can be informed that a multi-task project is being debugged and that, accordingly, the stack pointer will often lie outside the bounds of the C stack.  However, if you’d like to suppress the warning messages that the supposedly out-of-bounds stack pointer may evoke, you can easily do so.  The IDE Options dialog, which is accessible via the Options… entry in the Tools menu, allows you to control a variety of settings affecting the appearance and functionality of Embedded Workbench.  To eliminate the warning messages for the stack, you should simply clear the box for Warn when stack pointer is out of bounds within this dialog’s Stack options, as shown below.
 

Hi Ishaan,

The protocol stacks that are part of Micrium OS are also free to use provided that you have a registered Silabs kit.

However, the GUI is not part of the protocol stacks, it is a separate product.

Regards,

Janos

Hi Andy,

Micrium OS is free to use on Silicon Labs hardware. All you need to have is a registered development kit.

Regards,

Janos

Are you calling CPU_TS_TmrInit() in your initialization code?

I'm not sure about the 1us interrupt, maybe someone from the Wireless team can chime in regarding that.

Hi Andy,

Micrium OS, including its network stack, is now free to use on Silicon Labs hardware.

In order to have access, you will need to have your development kit registered.

Regards,

Janos

Hi Andy,

Micrium OS, including its network stack, is now free to use on Silicon Labs hardware.

In order to have access, you will need to have your development kit registered.

Regards,

Janos