SDK

[alleekhaan]

Hi,

I have a question about SDK.
Why not a single example build out of the box in SDK.
As a beginner to learn about nRF devices, if i have to face all these weird issues in all examples then how i will be able to understand the code.

First, waste a lot of time to fix issues then test the codes.

Why it is like that?

I am using Segger studio and latest SDK>

Can someone guide me what i am missing here?

Thanks

[alleekhaan]

I setup VS and Connect SDK by following the course at academy.
I am facing these issues in a simple blinky example

#include errors detected based on information provided by the configurationProvider setting. Squiggles are disabled for this translation unit (C:\nordic\myApps\blinky_pwm\src\main.c).
cannot open source file "syscall_list.h" (dependency of "C:\Users\ALIKH\.vscode\extensions\ms-vscode.cpptools-1.20.5-win32-x64\bin\zephyr\kernel.h")
cannot open source file "devicetree_generated.h" (dependency of "C:\Users\ALIKH\.vscode\extensions\ms-vscode.cpptools-1.20.5-win32-x64\bin\zephyr\device.h")
cannot open source file "syscalls/pwm.h" (dependency of "C:\Users\ALIKH\.vscode\extensions\ms-vscode.cpptools-1.20.5-win32-x64\bin\zephyr\drivers\pwm.h")
The PWM drivers must be enabled by CONFIG_PWM to be included in the build

[AHaug]

Hi,

Segger Studio and the latest nRF Connect SDK are not compatible so you will have to go through https://academy.nordicsemi.com/courses/nrf-connect-sdk-fundamentals/ as you say to to see how to get started with nRF Connect SDK in VS Code.

alleekhaan said:

I am facing these issues in a simple blinky example

Could you verify what release of the SDK you're using? And is the sample from the same SDK or is it from the Academy course github repo? In general you should also include the full build log as there may be items you've missed when only pasting a snippet.

Kind regards,
Andreas

[alleekhaan]

Hi AHaug 
I downloaded latest Segger studio and latest verions of SDK nRF5_SDK_17.1.0_ddde560
I am using SDK sample but not any GitHub repo. As you said they are not compatible. I agreed but i also downloaded VS and nRF connect in VS. Their blinky example also has problem. Actually, i opened this thread related to VS and nRF connect but not segger studio. I mistakenly mentioned Segger studio in first message.
Although, i worked on Segger studio and make it work a blinky examples after some research and fixing bugs

[alleekhaan]

I was able to compile this example by deleting SEGGER_RTT_Syscalls_SES.c: file from the project(read in another threads)

Now i want to understand, what this example is supposed to do after reading Analog channel?

Will it print something on some terminal or what?

/*
   Author : Abdelali Boussetta @rmptxf
   Description : This saadc example uses one channel (AIN1 (P0.3)), samples at 100ms (10 samples) =  get result each (1 second).
   It uses 14Bit as a resolution.
*/

#include <stdbool.h>
#include <stdint.h>
#include <stdio.h>
#include <string.h>
#include "nrf.h"
#include "nrf_drv_saadc.h"
#include "nrf_drv_ppi.h"
#include "nrf_drv_timer.h"
#include "boards.h"
#include "app_error.h"
#include "nrf_delay.h"
#include "app_util_platform.h"
#include "nrf_pwr_mgmt.h"

#include "nrf_log.h"
#include "nrf_log_ctrl.h"
#include "nrf_log_default_backends.h"

#define SAMPLES_IN_BUFFER 10

static const nrf_drv_timer_t m_timer = NRF_DRV_TIMER_INSTANCE(0);
static nrf_saadc_value_t     m_buffer_pool[2][SAMPLES_IN_BUFFER];
static nrf_ppi_channel_t     m_ppi_channel;
static uint32_t              m_adc_evt_counter;

// RESULT = [V(P) � V(N) ] * GAIN/REFERENCE * 2(RESOLUTION - m)
// (m=0) if CONFIG.MODE=SE, or (m=1) if CONFIG.MODE=Diff.

// V(N) = 0;
// GAIN = 1/6;
// REFERENCE Voltage = internal (0.6V);
// RESOLUTION : 12 bit;
// m = 0;

// 12bit
// V(P) = RESULT x REFERENCE / ( GAIN x RESOLUTION) = RESULT x (600 / (1/6 x 2^(12)) =  ADC_RESULT x 0.87890625;
//#define ADC_RESULT_IN_MILLI_VOLTS(ADC_RESULT) ((ADC_RESULT * 0.87890625))

// 14bit
// V(P) = RESULT x REFERENCE / ( GAIN x RESOLUTION) = RESULT x (600 / (1/6 x 2^(14)) =  ADC_RESULT x 0.2197265625;
#define ADC_RESULT_IN_MILLI_VOLTS(ADC_RESULT) ((ADC_RESULT * 0.2197265625))


void timer_handler(nrf_timer_event_t event_type, void * p_context)
{

}


void saadc_sampling_event_init(void)
{
    ret_code_t err_code;

    err_code = nrf_drv_ppi_init();
    APP_ERROR_CHECK(err_code);

    nrf_drv_timer_config_t timer_cfg = NRF_DRV_TIMER_DEFAULT_CONFIG;
    timer_cfg.bit_width = NRF_TIMER_BIT_WIDTH_32;
    err_code = nrf_drv_timer_init(&m_timer, &timer_cfg, timer_handler);
    APP_ERROR_CHECK(err_code);

    /* setup m_timer for compare event every 100ms */
    uint32_t ticks = nrf_drv_timer_ms_to_ticks(&m_timer, 100);
    nrf_drv_timer_extended_compare(&m_timer,
                                   NRF_TIMER_CC_CHANNEL0,
                                   ticks,
                                   NRF_TIMER_SHORT_COMPARE0_CLEAR_MASK,
                                   false);
    nrf_drv_timer_enable(&m_timer);

    uint32_t timer_compare_event_addr = nrf_drv_timer_compare_event_address_get(&m_timer,
                                                                                NRF_TIMER_CC_CHANNEL0);
    uint32_t saadc_sample_task_addr   = nrf_drv_saadc_sample_task_get();

    /* setup ppi channel so that timer compare event is triggering sample task in SAADC */
    err_code = nrf_drv_ppi_channel_alloc(&m_ppi_channel);
    APP_ERROR_CHECK(err_code);

    err_code = nrf_drv_ppi_channel_assign(m_ppi_channel,
                                          timer_compare_event_addr,
                                          saadc_sample_task_addr);
    APP_ERROR_CHECK(err_code);
}


void saadc_sampling_event_enable(void)
{
    ret_code_t err_code = nrf_drv_ppi_channel_enable(m_ppi_channel);

    APP_ERROR_CHECK(err_code);
}


void saadc_callback(nrf_drv_saadc_evt_t const * p_event)
{
    ret_code_t err_code;

    if (p_event->type == NRF_DRV_SAADC_EVT_DONE)
    {     
        uint32_t buffer_samples = 0;
        uint16_t adc_result = 0;
        uint16_t adc_voltage_mv = 0;

        err_code = nrf_drv_saadc_buffer_convert(p_event->data.done.p_buffer, SAMPLES_IN_BUFFER);
        APP_ERROR_CHECK(err_code);

        m_adc_evt_counter++;

        NRF_LOG_INFO("ADC event number: %d", (int)m_adc_evt_counter);

        for (uint8_t i = 0; i < SAMPLES_IN_BUFFER; i++)
        {
            buffer_samples += p_event->data.done.p_buffer[i];
        }

        adc_result = buffer_samples/SAMPLES_IN_BUFFER;
        adc_voltage_mv = ADC_RESULT_IN_MILLI_VOLTS(adc_result);

        NRF_LOG_INFO("adc result : %d.", adc_result);
        NRF_LOG_INFO("voltage : %d mV.", adc_voltage_mv);
         
        NRF_LOG_INFO("---------------------------");
    }
}


void saadc_init(void)
{
    ret_code_t err_code;
    // Using the channel default single ended (SE) config
    // pin NRF_SAADC_INPUT_AIN1 : P0.03
    nrf_saadc_channel_config_t channel_config =
        NRF_DRV_SAADC_DEFAULT_CHANNEL_CONFIG_SE(NRF_SAADC_INPUT_AIN1);

    // changing the saadc resolution to 12bit
    nrf_drv_saadc_config_t saadc_config ;
    saadc_config.resolution = NRF_SAADC_RESOLUTION_14BIT;

    err_code = nrf_drv_saadc_init(&saadc_config, saadc_callback);
    APP_ERROR_CHECK(err_code);

    err_code = nrf_drv_saadc_channel_init(0, &channel_config);
    APP_ERROR_CHECK(err_code);

    err_code = nrf_drv_saadc_buffer_convert(m_buffer_pool[0], SAMPLES_IN_BUFFER);
    APP_ERROR_CHECK(err_code);

    err_code = nrf_drv_saadc_buffer_convert(m_buffer_pool[1], SAMPLES_IN_BUFFER);
    APP_ERROR_CHECK(err_code);

}


/**
 * @brief Function for main application entry.
 */
int main(void)
{
    uint32_t err_code = NRF_LOG_INIT(NULL);
    APP_ERROR_CHECK(err_code);

    NRF_LOG_DEFAULT_BACKENDS_INIT();

    ret_code_t ret_code = nrf_pwr_mgmt_init();
    APP_ERROR_CHECK(ret_code);

    saadc_init();
    saadc_sampling_event_init();
    saadc_sampling_event_enable();
    NRF_LOG_INFO("SAADC HAL simple example started.");

    while (1)
    {
        nrf_pwr_mgmt_run();
        NRF_LOG_FLUSH();
    }
}


/** @} */

[AHaug]

Hi,

You need to be a bit more clear here. Are you using nRF Connect SDK or nRF5 connect SDK?  "SDK" is not and means "Software Development Kit". The names of the respective SDK's are either "nRF 5" SDK or "nRF Connect" SDK so to find the proper resources that you need to follow you need to always specify.  

Your comment here 

alleekhaan said:

I setup VS and Connect SDK by following the course at academy.

implies nRF Connect SDK. All of the other previous comments are ambigious (except for your latest comment)

What SDK do you want to use? nRF5 or nRF Connect? What's your end goal? 

alleekhaan said:

I agreed but i also downloaded VS and nRF connect in VS. Their blinky example also has problem. Actually, i opened this thread related to VS and nRF connect but not segger studio.

Could you post the build log here and state what version of nRF Connect you were using?

alleekhaan said:

I mistakenly mentioned Segger studio in first message.
Although, i worked on Segger studio and make it work a blinky examples after some research and fixing bugs

Noted, thats clear. Thank you for specifying

Kind regards,
Andreas

[alleekhaan]

Hi AHaug 
Thanks for clarification.
I have following ends goals
1: Read analog pins and test if it is working(UART or RTT)
2: I2C sensor interfacing and test it's working(UART or RTT)


I started Visual studio using this tutorial from Nordic
https://www.youtube.com/playlist?list=PLx_tBuQ_KSqEt7NK-H7Lu78lT2OijwIMl

Here is the picture of versions

When i compile simply blinky example. This is what i got errors on log screen

[{
	"resource": "/c:/nordic/myApps/blinky/src/main.c",
	"owner": "C/C++: IntelliSense",
	"code": "1696",
	"severity": 8,
	"message": "#include errors detected based on information provided by the configurationProvider setting. Squiggles are disabled for this translation unit (C:\\nordic\\myApps\\blinky\\src\\main.c).",
	"source": "C/C++",
	"startLineNumber": 8,
	"startColumn": 1,
	"endLineNumber": 8,
	"endColumn": 27
},{
	"resource": "/c:/nordic/myApps/blinky/src/main.c",
	"owner": "C/C++: IntelliSense",
	"code": "1696",
	"severity": 8,
	"message": "cannot open source file \"syscall_list.h\" (dependency of \"C:\\Users\\ALIKH\\.vscode\\extensions\\ms-vscode.cpptools-1.20.5-win32-x64\\bin\\zephyr\\kernel.h\")",
	"source": "C/C++",
	"startLineNumber": 8,
	"startColumn": 1,
	"endLineNumber": 8,
	"endColumn": 27
},{
	"resource": "/c:/nordic/myApps/blinky/src/main.c",
	"owner": "C/C++: IntelliSense",
	"code": "1696",
	"severity": 8,
	"message": "cannot open source file \"devicetree_generated.h\" (dependency of \"C:\\Users\\ALIKH\\.vscode\\extensions\\ms-vscode.cpptools-1.20.5-win32-x64\\bin\\zephyr\\drivers\\gpio.h\")",
	"source": "C/C++",
	"startLineNumber": 9,
	"startColumn": 1,
	"endLineNumber": 9,
	"endColumn": 33
},{
	"resource": "/c:/nordic/myApps/blinky/src/main.c",
	"owner": "Kconfig options",
	"code": "missing_kconfig_param",
	"severity": 4,
	"message": "The GPIO drivers must be enabled by CONFIG_GPIO to be included in the build",
	"startLineNumber": 9,
	"startColumn": 1,
	"endLineNumber": 9,
	"endColumn": 34
}]

Then i moved to SEGGER studio to do the same blinky example test.

I was able there to do blinky test on nRF52DVK after fixing some issues already discussed on threads.

Now the reason, creating this thread to know why there are so many issues in both platforms.

Why nothing works out of the box? What I am missing(Sorry to being nobe here)

I simply want to perform these tests
1: Read analog pins and test if it is working(UART or RTT)
2: I2C sensor interfacing and test it's working(UART or RTT)

So i can later design my own custom board.

Thanks

[AHaug]

Hi,

alleekhaan said:

Why nothing works out of the box? What I am missing(Sorry to being nobe here)

No worries, it's a bit much when you're starting out.

I see that you have a mismatch in between your toolchain and your SDK version :

  

You should always ensure that you've selected the toolchain that corresponds to the SDK you're using, which is what I believe is causing the issues. For more details this should be explained in the fundamentals course on the academy pages you referred to at the start of the case

Could you try to make sure that you match the SDK and toolchain versions? it's always best to use a stable release than a "CS" or "RC" (release candidate).

You should use 2.6.1, but if should look like this when it is matching (the sample in the picture uses 2.4.1):

Kind regards,
Andreas

[alleekhaan]

Hi AHaug 
I installed same SDK and i am still getting same error.

It's  seems like it is not founding headers directories

#include <zephyr/kernel.h>

#include <zephyr/drivers/gpio.h>

 

[{
	"resource": "/c:/nordic/myApps/blinky_2/src/main.c",
	"owner": "Kconfig options",
	"code": "missing_kconfig_param",
	"severity": 4,
	"message": "The GPIO drivers must be enabled by CONFIG_GPIO to be included in the build",
	"startLineNumber": 8,
	"startColumn": 1,
	"endLineNumber": 8,
	"endColumn": 34
}]

[AHaug]

Hi,

How are you building this sample? I tried reproducing it by setting up a clean NCS v2.6.1 instance and building the blinky sample. It worked both in terminal and in the VS Code extension

Command prompt opened through nRF Connect Terminal:

 Directory of C:\Nordic\SDKs\ncs\v2.6.1\zephyr\samples\basic\blinky

08.07.2024  12:13    <DIR>          .
08.07.2024  12:13    <DIR>          ..
08.07.2024  12:13               195 CMakeLists.txt
08.07.2024  12:13                15 prj.conf
08.07.2024  12:13             2 736 README.rst
08.07.2024  12:13               259 sample.yaml
08.07.2024  12:13    <DIR>          src
               4 File(s)          3 205 bytes
               3 Dir(s)  105 279 221 760 bytes free

C:\Nordic\SDKs\ncs\v2.6.1\zephyr\samples\basic\blinky>west build -b nrf52840dk_nrf52840
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: C:/Nordic/SDKs/ncs/v2.6.1/zephyr/samples/basic/blinky
-- CMake version: 3.21.0
-- Using NCS Toolchain 2.6.20240304.889616714482 for building. (C:/Nordic/SDKs/ncs/toolchains/cf2149caf2/cmake)
-- Found Python3: C:/Nordic/SDKs/ncs/toolchains/cf2149caf2/opt/bin/python.exe (found suitable version "3.9.13", minimum required is "3.8") found components: Interpreter
-- Cache files will be written to: C:/Nordic/SDKs/ncs/v2.6.1/zephyr/.cache
-- Zephyr version: 3.5.99 (C:/Nordic/SDKs/ncs/v2.6.1/zephyr)
-- Found west (found suitable version "1.2.0", minimum required is "0.14.0")
-- Board: nrf52840dk_nrf52840
-- Found host-tools: zephyr 0.16.5 (C:/Nordic/SDKs/ncs/toolchains/cf2149caf2/opt/zephyr-sdk)
-- Found toolchain: zephyr 0.16.5 (C:/Nordic/SDKs/ncs/toolchains/cf2149caf2/opt/zephyr-sdk)
-- Found Dtc: C:/Nordic/SDKs/ncs/toolchains/cf2149caf2/opt/bin/dtc.exe (found suitable version "1.4.7", minimum required is "1.4.6")
-- Found BOARD.dts: C:/Nordic/SDKs/ncs/v2.6.1/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840.dts
-- Generated zephyr.dts: C:/Nordic/SDKs/ncs/v2.6.1/zephyr/samples/basic/blinky/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: C:/Nordic/SDKs/ncs/v2.6.1/zephyr/samples/basic/blinky/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: C:/Nordic/SDKs/ncs/v2.6.1/zephyr/samples/basic/blinky/build/zephyr/dts.cmake
Parsing C:/Nordic/SDKs/ncs/v2.6.1/zephyr/Kconfig
Loaded configuration 'C:/Nordic/SDKs/ncs/v2.6.1/zephyr/boards/arm/nrf52840dk_nrf52840/nrf52840dk_nrf52840_defconfig'
Merged configuration 'C:/Nordic/SDKs/ncs/v2.6.1/zephyr/samples/basic/blinky/prj.conf'
Configuration saved to 'C:/Nordic/SDKs/ncs/v2.6.1/zephyr/samples/basic/blinky/build/zephyr/.config'
Kconfig header saved to 'C:/Nordic/SDKs/ncs/v2.6.1/zephyr/samples/basic/blinky/build/zephyr/include/generated/autoconf.h'
-- Found GnuLd: c:/nordic/sdks/ncs/toolchains/cf2149caf2/opt/zephyr-sdk/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.2.0/../../../../arm-zephyr-eabi/bin/ld.bfd.exe (found version "2.38")
-- The C compiler identification is GNU 12.2.0
-- The CXX compiler identification is GNU 12.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/Nordic/SDKs/ncs/toolchains/cf2149caf2/opt/zephyr-sdk/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc.exe
-- Configuring done
-- Generating done
-- Build files have been written to: C:/Nordic/SDKs/ncs/v2.6.1/zephyr/samples/basic/blinky/build
←[92m-- west build: building application
[2/139] Generating include/generated/version.h
-- Zephyr version: 3.5.99 (C:/Nordic/SDKs/ncs/v2.6.1/zephyr), build: v3.5.99-ncs1-1
[139/139] Linking C executable zephyr\zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:       21880 B         1 MB      2.09%
             RAM:        7552 B       256 KB      2.88%
        IDT_LIST:          0 GB        32 KB      0.00%

VS Code extension (shows the same, successfull log):

Are you using West to build your sample or something else?

Kind regards,
Andreas