Adapting ble_app_blinky_c to work with nRF52840 Dongle

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Thu, 10 Jun 2021 15:15:31 GMT

Oh, okay. I guess I just remove the D!

Thanks.

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

JONATHAN LL — Thu, 10 Jun 2021 14:29:25 GMT

Thanks again for keeping this updated,

As fare as I am aware, look at the example you want to reference and take a peek at the makefile to see what defines are there.

Then add the info to the json file in VSC, so that the .json and makfile match

Regards,
Jonathan

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Sun, 06 Jun 2021 12:38:31 GMT

Spoke too soon, but here is a better list of defines that I grabbed by downloading and installing Segger SES and looking through the pre-processor options

            "defines": [
                "APP_TIMER_V2",
                "APP_TIMER_V2_RTC1_ENABLED",
                "BOARD_PCA10059",
                "CONFIG_GPIO_AS_PINRESET",
                "FLOAT_ABI_HARD",
                "INITIALIZE_USER_SECTIONS",
                "NO_VTOR_CONFIG",
                "NRF52840_XXAA",
                "NRF_SD_BLE_API_VERSION=7",
                "S140",
                "SOFTDEVICE_PRESENT"
            ],

There is another one as well: "NDEBUG" which I think is for release code.

I have opened another ticket on how to locate the documentation which tells us what defines we should consider as I am not certain this is an exhaustive list, but at least I'm not getting any VS Code "PROBLEMS" with intellisense on any opened files.

🙂

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

JONATHAN LL — Fri, 04 Jun 2021 14:22:57 GMT

Thanks for keeping the post up to date, great work!

Regards,
Jonathan

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Fri, 04 Jun 2021 14:19:19 GMT

Yay O frabjous day! Callooh! Callay! I have slain the Jabberwock!!!

So, all of these issues resolved down to VS Code deciding to search all kinds of paths looking for include files. I have quite a few projects which I cloned from Github that contained various versions of the nRF sdk rather than one.

So I removed all my includes from c_cpp_properties.json, removed the unused soft devices from the sdk leaving just s140 and the within VS Code ran the command: "Reset IntelliSense Database" (Use F1 or ctrl+shift+p).

Then I slowly re-introduced my include paths ending up with:

            "includePath": [
                "${workspaceFolder}/pca10059/s140/config/**",

                "C:/nRF52840/nRF5_SDK_17.0.2_d674dde/components/**",
                "C:/nRF52840/nRF5_SDK_17.0.2_d674dde/modules/**",

                "${env:GNU_GCC}/**"
            ],

The errors have now all gone and I can get on with trying to understand the code.

Hope this helps someone 🙂

Gordon

This can be closed now.

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Fri, 04 Jun 2021 12:47:34 GMT

So, I seem to be narrowing down on the issue (perhaps).

If I go to the definition for "params" in the offending line in main.c

err_code = sd_ble_gap_conn_param_update(p_gap_evt->conn_handle,

&p_gap_evt->params.conn_param_update_request.conn_params);

I go to ble_gap.h

However on closer examination and by fluke I noted this was referring to the soft device s112 headers and not s140 which is the sd I need for pca10059. So I think I need to fix how this wrong reference is occurring.

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Fri, 04 Jun 2021 12:21:53 GMT

Any ideas why this is causing an error please?

It seems odd that it's just this and not all the rest?

From this in main.c

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Fri, 04 Jun 2021 11:25:30 GMT

So this seems related to the last define I added : "BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST",

In ble_gap.h there is an error in the enum BLE_GAP_EVTS at the point where it is listed

line 132

BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST = BLE_GAP_EVT_BASE + 15,

So something isn't right with my define perhaps?? Does it need a value?

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Fri, 04 Jun 2021 11:14:45 GMT

Not really "figured out" et. I'd really like to stick with VS Code and I think I'm very close. Why do you think it is a VS Code linker issue. I'm not getting any errors with the linker as the thing builds. The VS Code linker is just the

GNU Arm Embedded Toolchain/10 2020-q4-major

toolchain one isn't it?

The issue seems to be with configuring includes or defines I think. I'm only a newbie at this stuff. More a Javascript guy.

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

JONATHAN LL — Fri, 04 Jun 2021 11:10:10 GMT

Nice to see that you figured it out. As for the red squiggles that is probably a vs code linker problem and not a actual issue, if you can open the project in SES then the "problem" might be solved.

Regards,
Jonathan

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Fri, 04 Jun 2021 11:06:11 GMT

Uhmmm, so I found that adding the following to the "defines" section of c_cpp_properties.json (a part of vscode c/c++ extension) gets rid of ost errors:

"NRF_SDH_BLE_ENABLED",

"NRF_BLE_GQ_DATAPOOL_ELEMENT_SIZE=20",

"NRF_BLE_GQ_DATAPOOL_ELEMENT_COUNT=8",

"BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST",

But why I need to do this I don't get, especially as they are in sdk_config.h ???

How do I figure out/know what defines I need???

One last error remain, I hope!

union "<unnamed>" has no field "conn_param_update_request"

referring to

case BLE_GAP_EVT_CONN_PARAM_UPDATE_REQUEST:

{

// Accept parameters requested by peer.

err_code = sd_ble_gap_conn_param_update(p_gap_evt->conn_handle,

&p_gap_evt->params.conn_param_update_request.conn_params);

APP_ERROR_CHECK(err_code);

} break;

in the

static void ble_evt_handler(ble_evt_t const * p_ble_evt, void * p_context)

{

function.

???

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Fri, 04 Jun 2021 09:23:05 GMT

So I went and checked the ble_blinky app that is set up for the dongle and now I see that there were problems with that code in main.c as well that I'd never noticed. So there must be something wrong with my VS Code setup. I have no idea what. This is driving me nuts! 😞 Yet it builds and runs!!!!

For example in main.c pn the ble_blinky, similar to ble_blinky_c

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Fri, 04 Jun 2021 08:53:57 GMT

I think the uint32_t error may be a distraction. I turned them to uint16_t temporarily that got rid of that squiggle, but the error in main.c is still there:

function "LOCAL_ERR_CODE" may not be initialized

So I'm off hunting for this.

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Fri, 04 Jun 2021 08:15:43 GMT

Oooh that's interesting. If I change uint32_t to uint8_t the error goes away!!! Now what could possibly be wrong with uint32_t - that's pretty fundamental isn't it? <stdint.h>

Actually if I right click the uint32_t and "Goto definition" it doesn't go anywhere, however the uint8_t goes to C:\Program Files (x86)\GNU Arm Embedded Toolchain\10 2020-q4-major\arm-none-eabi\include\sys\_stdint.h - note the underscore _stdint.h. Mind this doesn't define uint32_t or any other unint anyway.

I have no idea why the code is structured this way????

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Fri, 04 Jun 2021 06:40:45 GMT

Okay, so I'm trying to track down these errors which to my understanding are possibly down to header files not being found. A main one was to make sure that sdk_config.h was referenced. Bit I think it was already. BTW I am open to the suggestion that the VS Code intellisense may be at fault here???

Anyhow, let's look at one that is odd: If I can solve this one then a majority of errors disappear and should be straightforward:

In main.c it is reported that

function "LOCAL_ERR_CODE" may not be initialized (line 146)

line 146

APP_ERROR_CHECK(err_code);

So I right click and look at the definition: it's in app_error.h (Can I assume that if VS Code can find the definition then it's in the include path?)

Then after a time while the intellisense scans I get

a function type is not allowed here (line 82)

And here is the kicker.

typedef struct

{

uint32_t line_num; /**< The line number where the error occurred. */

uint8_t const * p_file_name; /**< The file in which the error occurred. */

uint32_t err_code; /**< The error code representing the error that occurred. */

} error_info_t;

line_num and err_code have squiggles under them? I mean they are just variable names, aren't they? They aren't functions? Are they?

The file has a <stdint.h> include, so I can't see it being uint32_t

The only other message apart from duplicates of above is

identifier "NRF_BLE_GQ_DATAPOOL_ELEMENT_SIZE" is undefined

Yet it is defined in sdk_config.h and I added that to my include list as an absolute path to make sure.

Anyone got any ideas?

RE: Adapting ble_app_blinky_c to work with nRF52840 Dongle

gfmoore — Thu, 03 Jun 2021 16:13:53 GMT

Well, would you believe it. I went and built it anyway just for a laugh and it compiled with no errors, so I flashed it and man it works.

However, I'd still like to know what is causing the red squiggle problems!