BSP_ALARM_FREQUENCY in TWRK60N512 set to 100 ??

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

BSP_ALARM_FREQUENCY in TWRK60N512 set to 100 ??

Jump to solution
1,008 Views
GottiLuca
Contributor IV

In all the MQX documentation ( and on this forum too .. )  it's clearly stated that the minimun tick delay of MQX is 5 ms which means that the macro BSP_ALARM_FREQUENCY is set to 200 ( 1000 / 200 = 5 ms ) .

Today I've cheched the BSP_ALARM_FREQUENCY value for TWRK60 BSP and i found it's 100 ( which means 10 ms minumum delay  time )... 

I'd like to know what is the reason of this settings and , more important, if there is any problem to set this value to a greater value ( like 500   ).

 

 

0 Kudos
1 Solution
386 Views
petr_uhlir
NXP Employee
NXP Employee

Luca,

the BSP_ALARM_FREQUENCY should be defined to 200 (5ms timer tick) in all BSPs . In powerfull MCUs like Coldfire V4, MPC512x,  (Kinetis) you can try higher frequency.  But is some application you may have troubles as context switching load also increases.

View solution in original post

0 Kudos
1 Reply
387 Views
petr_uhlir
NXP Employee
NXP Employee

Luca,

the BSP_ALARM_FREQUENCY should be defined to 200 (5ms timer tick) in all BSPs . In powerfull MCUs like Coldfire V4, MPC512x,  (Kinetis) you can try higher frequency.  But is some application you may have troubles as context switching load also increases.

0 Kudos