Range Finding, nrf_dm won't build cleanly or at all.

RE: Range Finding, nrf_dm won't build cleanly or at all.

Sigurd — Mon, 25 Sep 2023 07:05:21 GMT

Hi!

Please open a new case for this new question: https://devzone.nordicsemi.com/support/add

RE: Range Finding, nrf_dm won't build cleanly or at all.

mej7000 — Sun, 24 Sep 2023 22:36:24 GMT

I have nrf_dm running on two nrf52832dk boards working perfectly. I can read the information in the UART. But I need help interpreting the BLE data.

I can see the 3 characteristics that return measurements:

/** @brief UUID of the Distance Measurement Characteristic. **/
#define BT_UUID_DDFS_DISTANCE_MEAS_VAL \
BT_UUID_128_ENCODE(0x21490001, 0x494a, 0x4573, 0x98af, 0xf126af76f490)

/** @brief UUID of the Azimuth Measurement Characteristic. **/
#define BT_UUID_DDFS_AZIMUTH_MEAS_VAL \
BT_UUID_128_ENCODE(0x21490002, 0x494a, 0x4573, 0x98af, 0xf126af76f490)

/** @brief UUID of the Elevation Measurement Characteristic. **/
#define BT_UUID_DDFS_ELEVATION_MEAS_VAL \
BT_UUID_128_ENCODE(0x21490003, 0x494a, 0x4573, 0x98af, 0xf126af76f490)

From the 3 different notifies I get BLE data such as:

DISTANCE_MEAS_VAL: 0x020082BA2E1FAEC601050009000C000500
AZIMUTH_MEAS_VAL: 0x0000FFEEDDCCBBAA011401
ELEVATION_MEAS_VAL: 0x0002FFEEDDCCBBAA01F5

I assume the above is meant to be read into an application and not just used/required for the distance measurement firmware? If so, I need help on how to turn the above into decimal information. thanks!

RE: Range Finding, nrf_dm won't build cleanly or at all.

Sigurd — Thu, 21 Sep 2023 23:53:19 GMT

[quote user="mej7000"]

Is there a good way to start nrf_dm development now? Is there is a "best" dk that specifically works well with nrf_dm?

Eventually I was planning to use the nrf5340 in production because it has the memory to do the higher end distance calculations and seems to have the best power profile, but as long as I can develop successfully on something now I can move the project forward with the client.

If the nrf_dm team revises the example to make it more nrf5340dk friendly is there a good way to get notified when they are done? Do you have any sense of how long that might take? Weeks/Months?

[/quote]

The sample should work fine on the nRF5340-DK. There are some warnings when building, yes, but I don't see why that should stop you from going forward with developing your project with the nRF5340.

RE: Range Finding, nrf_dm won't build cleanly or at all.

mej7000 — Wed, 20 Sep 2023 13:59:57 GMT

Thanks! That is good to know. Helps me qualify that maybe my installation is better than I thought...

Is there a good way to start nrf_dm development now? Is there is a "best" dk that specifically works well with nrf_dm?

If the nrf_dm team revises the example to make it more nrf5340dk friendly is there a good way to get notified when they are done? Do you have any sense of how long that might take? Weeks/Months?

RE: Range Finding, nrf_dm won't build cleanly or at all.

Sigurd — Wed, 20 Sep 2023 08:45:36 GMT

Hi,

I'm seeing these warnings for this sample when building for nRF53-DK as well.

I will report this to the nrf_dm developers.

RE: Range Finding, nrf_dm won't build cleanly or at all.

mej7000 — Mon, 18 Sep 2023 14:45:20 GMT

No Thingy53. That makes sense. Thanks.

This build is straight out of the samples, using the nrf5340dk board. No code revisions. I am concerned my environment is not setup correctly because it's generating 10 warnings, some that look fairly serious...
Is there any way for me to improve my IDE environment so that I generate less Warnings?
I always have to "scan for kits", but "no kit selected" is always returned in the bottom toolbar. Is that something I should be concerned about?

[{
"resource": "/../../../CMakeLists.txt",
"owner": "nrf-connect",
"severity": 4,
"message": "No SOURCES given to Zephyr library: lib__libc__common",
"source": "cmake",
"startLineNumber": 839,
"startColumn": 1,
"endLineNumber": 839,
"endColumn": 2147483647
},{
"resource": "/c:/ncs/v2.4.2/nrf/subsys/dm/dm.c",
"owner": "cpptools",
"severity": 4,
"message": "#warning \"The ncs,dm-timer chosen node is not set; defaulting to TIMER2\" [-Wcpp]",
"source": "gcc",
"startLineNumber": 43,
"startColumn": 2,
"endLineNumber": 43,
"endColumn": 2
},{
"resource": "/c:/ncs/v2.4.2/zephyr/CMakeLists.txt",
"owner": "nrf-connect",
"severity": 4,
"message": "No SOURCES given to Zephyr library: lib__libc__common",
"source": "cmake",
"startLineNumber": 839,
"startColumn": 1,
"endLineNumber": 839,
"endColumn": 2147483647
},{
"resource": "/c:/ncs/v2.4.2/zephyr/CMakeLists.txt",
"owner": "nrf-connect",
"severity": 4,
"message": "__ASSERT() statements are globally ENABLED",
"source": "cmake",
"startLineNumber": 1865,
"startColumn": 1,
"endLineNumber": 1865,
"endColumn": 2147483647
},{
"resource": "/c:/nordic/myApps/nrf_dm_4/boards/nrf5340dk_nrf5340_cpuapp.conf",
"owner": "kconfig0",
"severity": 4,
"message": "CONFIG_MPSL was assigned the value n, but got the value n. Missing dependencies:\nSOC_SERIES_BSIM_NRFXX || SOC_SERIES_NRF52X || SOC_NRF5340_CPUNET",
"startLineNumber": 12,
"startColumn": 1,
"endLineNumber": 12,
"endColumn": 12
},{
"resource": "/c:/nordic/myApps/nrf_dm_4/child_image/hci_rpmsg.conf",
"owner": "kconfig0",
"severity": 4,
"message": "MAIN_STACK_SIZE set more than once. Old value \"512\", new value \"680\".",
"startLineNumber": 20,
"startColumn": 1,
"endLineNumber": 20,
"endColumn": 27,
"relatedInformation": [
{
"startLineNumber": 6,
"startColumn": 1,
"endLineNumber": 6,
"endColumn": 23,
"message": "Already set to \"512\" here",
"resource": "/c:/ncs/v2.4.2/zephyr/samples/bluetooth/hci_rpmsg/prj.conf"
}
]
},{
"resource": "/c:/nordic/myApps/nrf_dm_4/child_image/hci_rpmsg.conf",
"owner": "kconfig0",
"severity": 4,
"message": "HEAP_MEM_POOL_SIZE set more than once. Old value \"8192\", new value \"2048\".",
"startLineNumber": 27,
"startColumn": 1,
"endLineNumber": 27,
"endColumn": 31,
"relatedInformation": [
{
"startLineNumber": 4,
"startColumn": 1,
"endLineNumber": 4,
"endColumn": 26,
"message": "Already set to \"8192\" here",
"resource": "/c:/ncs/v2.4.2/zephyr/samples/bluetooth/hci_rpmsg/prj.conf"
}
]
},{
"resource": "/c:/nordic/myApps/nrf_dm_4/prj.conf",
"owner": "kconfig0",
"severity": 4,
"message": "CONFIG_MPSL was assigned the value y, but got the value n. Missing dependencies:\nSOC_SERIES_BSIM_NRFXX || SOC_SERIES_NRF52X || SOC_NRF5340_CPUNET",
"startLineNumber": 30,
"startColumn": 1,
"endLineNumber": 30,
"endColumn": 12
}]

RE: Range Finding, nrf_dm won't build cleanly or at all.

Sigurd — Mon, 18 Sep 2023 11:55:33 GMT

Hi!

See the requirements here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/bluetooth/nrf_dm/README.html

Thingy:53 is not supported by this sample.