Friday, April 20th 2018, 4:48am UTC+2

You are not logged in.

  • Login
  • Register


Dear visitor, welcome to SEGGER Forum. If this is your first visit here, please read the Help. It explains how this page works. You must be registered before you can use all the page's features. Please use the registration form, to register here or read more information about the registration process. If you are already registered, please login here.

Message information
Automatically converts internet addresses into links by adding [url] and [/url] around them.
Smiley code in your message such as :) is automatically displayed as image.
You can use BBCode to format your message, if this option is enabled.
Security measure

Please enter the letters that are shown in the picture below (without spaces, and upper or lower case can be used).

The last 2 posts

Tuesday, March 27th 2018, 9:45am

by SEGGER - Til

Hi Lior,

did you make any changes to the board support package, especially OS_GetTime_Cycles()?
I'll check if we have the same device/evalboard here and give it a try.
But I am pretty sure it should work as expected.

Best regards,

Tuesday, March 27th 2018, 9:40am

by Lior Haimovich

OS_Delayus() not fast enough


I've noticed that when I use OS_Delayus() the actual delay I receive never goes below 1 [ms], this is something new I am experiencing (in the past the delay was much more accurate).
I can't put my finger on what has changed that causes this so I want to ask what can effect this delay function in such a way?

NOTE: I am currently not running any tasks.

1. Which embOS do you use?
I use embOS trial for Cortex-M and IAR compiler version 4.40 with IAR workbench 8.20.1 (embOS_CortexM_IAR_V8_Trial_V440).

2. Which CPU and eval board do you use?
I use Silicon Labs EFR32FG13P231F512GM48 cpu.