Honour values of configCPU_CLOCK_HZ & configTICK_RATE_HZ for tick rate
Fixes #147 * Can vary tick rate from 100Hz via configTICK_RATE_HZ. Note that the SDK binary libraries are hard-coded to assume the tick rate is 100Hz, so changing the tick rate may have unexpected consequences for lower layer WiFi behaviour (such as certain kinds of timeouts happening faster/slower.) * Setting configCPU_CLOCK_HZ to 160MHz means ESP will set 160MHz during initialisation. Only 80MHz and 160MHz are supported. * Timing of tasks is no longer affected by current CPU freq (whether set via configCPU_CLOCK_HZ or via sdk_system_update_cpu_freq().) Previously doubling the CPU frequency would double the tick rate.
This commit is contained in:
parent
701a4c4284
commit
678b59babf
5 changed files with 19 additions and 2 deletions
|
@ -34,6 +34,13 @@
|
|||
#define configUSE_TICK_HOOK 0
|
||||
#endif
|
||||
#ifndef configCPU_CLOCK_HZ
|
||||
/* This is the _default_ clock speed for the CPU. Can be either 80MHz
|
||||
* or 160MHz, and the system will set the clock speed to match at startup.
|
||||
|
||||
Note that it's possible to change the clock speed at runtime, so you
|
||||
can/should use sdk_system_get_cpu_frequency() in order to determine the
|
||||
current CPU frequency, in preference to this macro.
|
||||
*/
|
||||
#define configCPU_CLOCK_HZ ( ( unsigned long ) 80000000 )
|
||||
#endif
|
||||
#ifndef configTICK_RATE_HZ
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue