Questions coming to new code structure - BLE vs old BLE

[chucknorris101]

I pulled my files before alot of the rewrites for BTHome it seems, im a bit lost now in looking at the files on how I can update my system to the latest and greatest.

I think I have the VS code environment set up - at least I get an output file of zephyr elf, hex, map etc.

Its not clear though how to set up kconfig options? Ive found the interface but so far I just see a few options related to sleep and mac address setting, though it sounded like i would be editing the prj.conf file? prj.conf has a few more commented out options as well, but these seem present in the kconfig interface in vs code?

Where can I turn off the LED blinking during each reading? or is it disabled by default now? or was it determined to not drain much power? id prefer to not have the blinking.... looking at the blinky sample it seems this is controlled by GPIO=y but arent there other GPIO settings?

Where do i configure log/debug output to jlink viewer? This would be a nice toggle for calibration or not - is this under printf_fp_support? segger rtt?

Overall I like the simplified interface when it comes to KConfig/prj conf - looking at the various bits of code it seems like KConfig is just the primary source of 'variables' - what would be needed to add more KCONFIG options? looking across the various files for the current kconfig options i didnt see a consistent 'include' file that would prompt that type of feed, is this just a feature of this vscode workspace that it will find the variables?

for example, if i wanted to add inputs for a custom calibration, would it be as simple as adding a kconfig variable line, then adding that variable name in lieu of the specific values to replace? i.e. dry = CONFIG_DRY_X_2_COEFF * x * x + CONFIG_DRY_X_COEFF*x + CONFIG_DRY_INTERCEPT with those 3 being prompts in kconfig?

[rbaron]

Most of your questions are about the nRF Connect/Zephyr. I would highly recommend you take a look at their docs, specially sections about devicetree and Kconfig. I also recommend the Custom Boards section since you are working with your own forked variant. Compare it with our own board definitions in prstlib/boards/. We also have our own Configuration docs for ble that mention our Kconfig/prj.conf options with links.

Where can I turn off the LED blinking during each reading?

There's no more LED flashing during reading.

Where do i configure log/debug output to jlink viewer

CONFIG_PRSTLIB_LOG_LEVEL_DBG=y in your prj.conf.

inputs for a custom calibration, would it be as simple as adding a kconfig variable

Yes, but I would argue that calibration is a property of the board, so I would define it in the custom board. I did something similar in the v2.0.0 branch (WIP, no date for PR), except I used devicetree bindings instead of Kconfig configs.

[chucknorris101]

ah! thanks for the clarifications! yea ill look into it for sure - and i would agree its a board property per se, ill have to dig into the device tree setup. What ive found from the non-thin-film coatings (epoxy) is that the calibration is significantly impacted vs the uncoated board readouts. Maybe this can be remedied with a better application process, but for now im treating each board as 'unique' post-coating so was hoping to make it editable all in one spot. Ill dig in and maybe play around with the structure a bit.

Thanks!!

[rbaron]

Closing due to inactivity. Feel free to reopen if needed. Tks!