This website requires JavaScript.
Explore
Help
Sign In
OrgZephyr
/
zephyr
mirror of
https://github.com/zephyrproject-rtos/zephyr.git
Watch
1
Star
0
Fork
You've already forked zephyr
0
Code
Issues
Releases
Wiki
Activity
81dbe94a16
zephyr
/
samples
/
basic
/
minimal
/
no-timers.conf
3 lines
59 B
Plaintext
Raw
Normal View
History
Unescape
Escape
samples: basic: Add a minimal sample Add a minimal sample that showcases minimal ROM sizes. It can be built in several configurations, all very restrictive when it comes to features enabled in order to verify the fact that we can fit in small devices and to be able to accurately measure the sizes of the kernel's basic features. Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
2019-05-10 01:48:17 +08:00
# No timer support in the kernel
kernel: Crank up default tick rate When tickless is available, all existing devices can handle much higher timing precision than 10ms. A 10kHz default seems acceptable without introducing too much range limitation (rollover for a signed time delta will happen at 2.5 days). Leave the 100 Hz default in place for ticked configurations, as those are going to be special purpose usages where the user probably actually cares about interrupt rate. Note that the defaulting logic interacts with an obscure trick: setting the tick rate to zero would indicate "no clock exists" to the configuration (some platforms use this to drop code from the build). But now that becomes a kconfig cycle, so to break it we expose CONFIG_SYS_CLOCK_EXISTS as an app-defined tunable and not a derived value from the tick rate. Only one test actually did this. Signed-off-by: Andy Ross <andrew.j.ross@intel.com>
2019-06-12 02:18:20 +08:00
CONFIG_SYS_CLOCK_EXISTS=n