RE: NCS Naming ADC Channels

Håkon Alseth — Tue, 16 Jan 2024 14:56:38 GMT

Hi,

I'm glad to hear that you got things working!

As mentioned, aliases can also help you with this scenario so that you do not have to handle it in runtime.

Kind regards,

Håkon

RE: NCS Naming ADC Channels

tvi — Tue, 16 Jan 2024 12:22:07 GMT

That was very helpful. With help strcmp I was able to determine where the adc value belongs to.

 if (strcmp(io_channels_name_str[i], "T100") == 0) {
    // Do something with the T100 sensor value
 } else if (strcmp(io_channels_name_str[i], "CURRENT_SENSE") == 0) {
    // Do something with the CURRENT_SENSE sensor value
 } else {
    // Unknown sensor
 }

RE: NCS Naming ADC Channels

Håkon Alseth — Mon, 15 Jan 2024 11:38:59 GMT

Hi,

[quote user=""]1. Loop trough each ADC-channel that is defined in the .dts file of the connected board periodically.[/quote]

Each channel that you define in io-channels will be populated in this array:

https://github.com/nrfconnect/sdk-zephyr/blob/v3.4.99-ncs1/samples/drivers/adc/src/main.c#L27-L30

In your case, it would be adc0/1/3/4 that will be populated.

[quote user=""]2. Based on the name of the ADC channel, convert the read-out voltage to something usefull, for example a temperature or light value.[/quote]

You can pick out the name by using the vscode DT plugin, copy c identifier:

Which will give you this, provided as an array of strings:

DT_PROP(DT_PATH(zephyr_user), io_channel_names)

You can then put this into your c-file:

const char * io_channels_name_str[] = DT_PROP(DT_PATH(zephyr_user), io_channel_names);

[quote user=""]Also including a separate header file in the board with all sensor definitions doens't seem right, because the header file will be in the project folder and not in the boards directory.[/quote]

It sounds like you want to use the user selected "aliases" in devicetree?

https://docs.zephyrproject.org/latest/build/dts/howtos.html#get-a-struct-device-from-a-devicetree-node

The aliases section isn't directly documented, but it is used quite often in the documentation, like here in the node identifiers section:

https://developer.nordicsemi.com/nRF_Connect_SDK/doc/2.5.1/zephyr/build/dts/api-usage.html

Kind regards,

Håkon