-
Notifications
You must be signed in to change notification settings - Fork 76
Conversation
Use static variables, saved in UICR, initialized to DEFINEs. This mitigates the need to modify sources and compile to just change (the frequently requested) TX_power, transmit interval, accelerometer thresholds ToDo: add code in gatt to allow these to be modified iff the password is == 0.
Let's keep this on hold until the configuration is implemented. Tagging issue #145 for reference. |
Keep on hold ( I intended that). I don't understand why these (and mode) should be in "flash" rather than in "user information configuration registers " (UICR) which is Non-volatile memory. Seems that using UICR is much simpler. Easily findable and viewable (modifiable ?) with j-link. |
UICR would not support wear leveling and is pretty limited in regards to amount of data that can be stored. But it would definitely be possible to store the data in UICR too. |
Regarding version 2.4.2, |
Remove initialization from main to uncluttered it. Begin initialization with setting of tunable variables used in the code to the values from NVM UICR. This commit is for code not yes complete but a work on progress.
Really easy(?) way to setup tuneables in UICR is using nrfjprog or j-link .
|
move packet formatters from library to same directory as main. add errorPacket remove URL code A work in progress
I closed this pull request because I am not confident in the completeness of my code at this time and the fact that there are multiple changes between the current version and my fork (like moving packet packer from library to be with main). |
Use static variables, saved in UICR, initialized to DEFINEs.
This mitigates the need to modify sources and compile to just change (the frequently requested) TX_power, transmit interval, accelerometer thresholds
ToDo: add code in gatt to allow these to be modified iff the password is == 0.