Hi Jacob,
Excellent point about the flash usage, and figuring out how to perhaps
make it easier for packages to play well together in a single filesystem
without hijacking the config system out of necessity.
I dont agree with that comment, whats thats actually doing is turning on
the config
Sorry, I can see the flash writes here starting at 32KB testing against
the default file (/tmp/native_flash.XX) as well as a hard-coded path
(-f simflash.bin).
$ xxd -s 0x8000 -l 128 simflash.bin
0008000: e231 8ab9 8c42 b07f 5382 e0ac 8efc 85b1 .1...B..S...
0008010: 0040
Hi Chris,
I don't know if this helps in your particular case, but you can specify
"-f " to use a local file for internal flash (assuming the app
calls `mcu_sim_parse_args()` in main). If you specify the name of an
existing file, the simulator will reuse its contents.
It doesn't look like
Hi Chris,
I think cases like the one you described are usually solved by adding a
> new setting to the driver package (e.g., `TSL2591_CONFIG`). If that
> setting is enabled, the driver package depends on `sys/config`, e.g.,
>
> pkg.deps.TSL2591_CONFIG:
> -
On Sat, Jul 07, 2018 at 06:13:22PM +0200, Kevin Townsend wrote:
> In the sys/config package, there are two main flags to test against in
> code, depending on your implementation:
>
> * CONFIG_FCB (storage in FCB)
> * CONFIG_NFFS (storage in NFFS)
>
>
In the sys/config package, there are two main flags to test against in
code, depending on your implementation:
* CONFIG_FCB (storage in FCB)
* CONFIG_NFFS (storage in NFFS)
https://github.com/apache/mynewt-core/blob/master/sys/config/syscfg.yml
I'd like to add config key-pairs as an option
