This is an example from www.keil.com/.../configWizard.html
// <o TIMESTAMP_SRC>Time Stamp Source // <dwt=> DWT Cycle Counter // <systick=> SysTick // <user=> User Timer // Selects source for 32-bit time stamp #define TIMESTAMP_SRC systick
Try inserting a digit into both instances of "TIMESTAMP_SRC", for example "TIMESTAMP2_SRC" and the parser will fail with "Syntax error in Options Block - line xxx: Invalid numeric number." Pregrammers very frequently use #defined values with digits and this is a severe limitation.
Hello Alex,
The configuration wizard annotations are for making an easy to use Wizard view for Programmers. The Wizard saves typing, and also prevents bad values being entered (since you can control the ranges).
The annotations were designed to build a view like this:
www.keil.com/.../RTX_Conf_CM_Wizard_View.png
If you want to set to systick, you should do that outside of the configuration wizard, that is to say, after this line in the config file:
//------------- <<< end of configuration section >>> -----------------------
#If TIMESTAMP #define TIMESTAMP_SRC systick #endif
///////
Another option is to make a premade list of valid values - these could be the values of systick.
// <o>Tick Timer interval <10=> 10 ms <20=> 20 ms <25=> 25 ms // <40=> 40 ms <50=> 50 ms <100=> 100 ms // <200=> 200 ms // System Tick Timer interval for software timers // Default: 100 ms #define TICK_INTERVAL 100
Thank you for reply, Kevin. The manual at above URL shows that it is possible to assign one predefined value to another through Configuration Wizard, and supplied example works fine (generates GUI)
// <o TIMESTAMP_SRC>Time Stamp Source // <dwt=> DWT Cycle Counter // <systick=> SysTick // <user=> User Timer #define TIMESTAMP_SRC systick
But why doesn't this generate GUI ?
// <o TIMESTAMP2_SRC>Time Stamp Source // <dwt=> DWT Cycle Counter // <systick=> SysTick // <user=> User Timer #define TIMESTAMP2_SRC systick
Allowing labels to have numbers may be convenient, but it would introduce the potential for users accidentally triggering options.
Numbers in labels are already used 2 major ways. The first skip counting would easily become a headache
skip: <qi>; <oi>; <oi.x>; <si>; <si.x>
This will skip i items. Can be applied to all annotation items marked with a * in this table.
----- Modify a bit: <e.i>* <o.i> <s.i>*
These will modify a particular bit of a value
------
I know in your example you hid the number in the middle of a string, but it would be very easy to accidentally put the number at the end of a string, with unintended consequences.
---
If you have any suggestions for the Standard, The CMSIS group it an industry wide community. You could leave ideas at github.com/.../CMSIS_5