Compiling error with VScode and Ninca C2909 tag (nrf52833)

[NCKGTW]

Hi all,

I have ublox nina modules including your nrf52833 .

I downaloaded the ublox application here:

Release C209 AoA Tag v2.0.1 · u-blox/c209-aoa-tag

and opened it with VS IDE in which I have the nrf connect SDK installed by following your youtube nRF Connect for VS Code, part 1: Installation series .

As you can see I buit the configuration with the following settings:

When I build the code i have the following error in the terminal:

In file included from C:/Users/xxxxx/Documents/Project/RTLS/FW/TAG/src/bt_adv.c:17:
C:/Users/xxxx/Documents/Project/RTLS/FW/TAG/src/bt_adv.h:20:10: fatal error: zephyr.h: No such file or directory
20 | #include <zephyr.h>
| ^~~~~~~~~~
compilation terminated.

Of course I can post all the log here but please let me know if I can avoid it.

Do you know why I get the error like  this ?

Thanks in advance,

Nicola

[Benjamin]

Hi,

Please update #include <zephyr.h> to #include <zephyr/kernel.h>, as zephyr.h is now deprecated and has been replaced by kernel.h. Note that this application was intended for an older SDK and significant porting could be needed as already mentioned here.

[NCKGTW]

Hi Banjamin,

thanks for reply.

I would start by changing:

• SDK version
• SDK toochain

HAve you idea which version for both in order to get the FW compiling with no error ?

Thanks

[NCKGTW]

Ok Turbo J , lets think on the opposite way:

ublox TAG  nina b406 has a nrf52833 inside it. We will use this chip in their RTLS ecosystem so the TAG will send  to their anchors the following 2 packets:

• extended advertising beacons with eddystone profile and specific namespace
• periodic advertising CTE packets 

Who will support us or other people in designing such application with newer SDK (e.g.3.2.0) from scratch? Do you have example project with these two fw requirements above?

Hope you can help.

Nicola

[Benjamin]

Hi,

We are not able to help with designing applications, as that is something you need to do yourself. However, what is your use case for this application? We may have some samples or resources that could be helpful.

[NCKGTW]

Hi Benjamin ,

FW will run on your nrf52833 DK

we need 3 example and merge them:

1. I2C Slave

2. send Eddystone Beacon with specific namespace in the extended advertising packets

3. send CTE packets  in the periodic advertising 

Please see below

We will have the use nRF52840 dongle to sniff both type of packets

Thanks

[Benjamin]

Hi,

I think these samples could be relevant for you!

direction_finding_connectionless_rx

extended_adv

eddystone

DevAcademy also provides good rescourses.

Here is the I2C lesson:

I2C - DevAcademy

[NCKGTW]

Hi Benjamin,

I started with direction_finding_connectionless_tx by trying to send the CTE packet (so that I can also send the eddystone packet once done) from an nrf52833DK board. From the other side I tried with 2 Kind of sniffer:

• nrf52840 USB dongle sniffer
• another nrf52833DK  sniffer

and by using wireshark I cant see any "CTE present=1".

What its strange to me is that both sniffer see the TX like Anonymous device.

I post the related info below 

Can you help us about this?

Thanks a lot.

Nicola

[PaKa]

Note for the receiver part the only SDK with qualification for this is the nRF Connect SDK 2.1.0 so if you plan to ship this into the market you have to use this version.

For the AoA transmitter you can use the newer SDKs but then you have to use the SDC (SoftDevice Controller subsystem) as that is the only one with qualification for AoA transmitter. This is only up to and including nRF Connect SDK version 2.9.2, version 3.0.n does not have qualification for direction finding at all.

[NCKGTW]

Hi Benjamin,

thanks for helping. We need just the transmitting part. 

So do you think by replacing sdk 3.0.2 to 2.9.2 I should see the CTE ?

Im going to try by today and let you know.

Thanks.

Nicola

[NCKGTW]

Hi Benjamin, I can confirm 2.9.2 is working with Tx AOA since Ublox RX is getting the beacon. What I see is that I cant see any CTE present yet in both nordic sniffers. DO you know why? Do I have to put an older version of sniffer on them (nrf52833dk, nrf52840 dongle) ?

Thanks

[PaKa]

If you are talking about the nRF Sniffer then this does not support Direction Finding, check the documentation for supported Bluetooth features.

If you are talking about another sniffer then I would check the documentation for that as well as not supporting Direction Finding may be quite common as it is a specialized feature that may be requiring extra payment.

[NCKGTW]

Hi Paka,

I mean every time I need to check if the CTE packet is present , how can I do in the receiver side ? Supposo I have a TX sendindg the CTE , how can I check such packets its really sent ?

Thanks