tests/benchmarks/timing_info failed on mec15xxevb_assy6853 board. #23414
Assignees
Labels
Comments
|
The reason why some benchmark results in thetest cases is "0" is that "RTOS" Timer is used to calucate elapsed time. But "RTOS" timer is operated on 32kHz oscillator(Please refer to section 22 in the data sheet). It is impossible to reach "ns" precision with it. However, CPU core on the board runs on 48MHz. We can enble the high percision timer (16/32 BIT BASIC TIMER--refer to section 19 in the data sheet) to resolve the issue. Someone has to wirte a driver for that timer. The data sheet. |
dcpleung
added a commit
to dcpleung/zephyr
that referenced
this issue
Mar 31, 2020
The timer counter for ticks on MEC1501 SoC is based on the RTOS timer which runs at 32kHz. This is too slow for timing benchmarks as most cases can be finished within one or two ticks. Since the SoC has higher frequency timers running at 48MHz, add the necessary bits to use these for timing benchmarks. Fix zephyrproject-rtos#23414 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
nashif
pushed a commit
that referenced
this issue
Mar 31, 2020
The timer counter for ticks on MEC1501 SoC is based on the RTOS timer which runs at 32kHz. This is too slow for timing benchmarks as most cases can be finished within one or two ticks. Since the SoC has higher frequency timers running at 48MHz, add the necessary bits to use these for timing benchmarks. Fix #23414 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
hakehuang
pushed a commit
to hakehuang/zephyr
that referenced
this issue
Apr 30, 2020
The timer counter for ticks on MEC1501 SoC is based on the RTOS timer which runs at 32kHz. This is too slow for timing benchmarks as most cases can be finished within one or two ticks. Since the SoC has higher frequency timers running at 48MHz, add the necessary bits to use these for timing benchmarks. Fix zephyrproject-rtos#23414 Signed-off-by: Daniel Leung <daniel.leung@intel.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Running tests/benchmarks/timing_info on mec15xxevb_assy6853 board, the test result is incorrect, for example, the "Clock Frequency is 0 MHz".
To Reproduce
Steps to reproduce the behavior:
Screenshots or console output
*** Booting Zephyr OS build zephyr-v2.2.0-219-g86bfc489f4a7 ***
starting test - Time Measurement
Timing Results: Clock Frequency: 0 MHz
Context switch : 0 cycles , 0 ns
Interrupt latency : 0 cycles , 0 ns
Tick overhead : 0 cycles , 0 ns
Thread Creation : 1 cycles , 30517 ns
Thread cancel : 0 cycles , 0 ns
Thread abort : 0 cycles , 0 ns
Thread Suspend : 1 cycles , 30517 ns
Thread Resume : 0 cycles , 0 ns
Thread Yield : 0 cycles , 0 ns
Thread Sleep : 1 cycles , 30517 ns
Heap Malloc : 0 cycles , 0 ns
Heap Free : 0 cycles , 0 ns
Semaphore Take with context switch : 0 cycles , 0 ns
Semaphore Give with context switch : 1 cycles , 30517 ns
Semaphore Take without context switch : 0 cycles , 0 ns
Semaphore Give without context switch : 1 cycles , 30517 ns
Mutex lock : 0 cycles , 0 ns
Mutex unlock : 0 cycles , 0 ns
Message Queue Put with context switch : 1 cycles , 30517 ns
Message Queue Put without context switch : 0 cycles , 0 ns
Message Queue get with context switch : 1 cycles , 30517 ns
Message Queue get without context switch : 0 cycles , 0 ns
MailBox synchronous put : 0 cycles , 0 ns
MailBox synchronous get : 1 cycles , 30517 ns
MailBox asynchronous put : 0 cycles , 0 ns
Environment (please complete the following information):
The text was updated successfully, but these errors were encountered: