pc-ble-driver-js 2.8.2 + pc-ble-driver 4.1.4 + node 14.19.1 - SIGSEGV on linux, but success on windows

RE: pc-ble-driver-js 2.8.2 + pc-ble-driver 4.1.4 + node 14.19.1 - SIGSEGV on linux, but success on windows

user26071 — Fri, 03 Jun 2022 13:16:43 GMT

[quote user="A.P"]

However, as I understand it, this doesn't address the segmentation fault poping up when using firmware 4.1.4 and pc-ble-driver version 4.1.4 on an Ubuntu machine, which is what was described here.

[/quote]

That is true. The 4.1.2 is a workaround. I will ping the internal ticket and update this here if I hear anything.

Best regards,

Edvin

RE: pc-ble-driver-js 2.8.2 + pc-ble-driver 4.1.4 + node 14.19.1 - SIGSEGV on linux, but success on windows

user83878 — Tue, 31 May 2022 11:41:42 GMT

Hi Edvin!
I see that the 4.1.2 firmware can be used with a pc-ble-driver version 4.1.4.
However, as I understand it, this doesn't address the segmentation fault poping up when using firmware 4.1.4 and pc-ble-driver version 4.1.4 on an Ubuntu machine, which is what was described here.

Am I misunderstanding something?

RE: pc-ble-driver-js 2.8.2 + pc-ble-driver 4.1.4 + node 14.19.1 - SIGSEGV on linux, but success on windows

user26071 — Tue, 31 May 2022 10:03:36 GMT

Hello,
The last update on this case was in a duplicate (not strictly a duplicate, but same user and same subject), which you can find here:

https://devzone.nordicsemi.com/f/nordic-q-a/87463/pc-ble-driver-backwards-compatability

Best regards,

Edvin

RE: pc-ble-driver-js 2.8.2 + pc-ble-driver 4.1.4 + node 14.19.1 - SIGSEGV on linux, but success on windows

user83878 — Tue, 31 May 2022 07:01:04 GMT

Hi Edvin!

Is there any update on this?

Thanks!

RE: pc-ble-driver-js 2.8.2 + pc-ble-driver 4.1.4 + node 14.19.1 - SIGSEGV on linux, but success on windows

user91473 — Thu, 28 Apr 2022 13:34:56 GMT

Hi,
An additional update: with the same build logic above (for node 14 on linux), we are able to run the dongle and connect to our peripherals with a dongle burnt with 4.1.2:

Go through the process above to compile and create the node bindings files for pc-ble-driver-js v2.8.2 and pc-ble-driver 4.1.4
Unzip our typescript code
"sudo yarn install" to install all our packages, including pc-ble-driver-js.
Replace the bindings files in node_modules/pc-ble-driver-js/build/Release with the bindings files we built in step 1.
Run our central - so far, we have been able to open the adapter, and connect to our peripherals with no issues.

Is this expected? Should a node bindings file compiled against a 4.1.4 pc-ble-driver work with a 4.1.2 dongle?
Has this been tested before?
Roi

RE: pc-ble-driver-js 2.8.2 + pc-ble-driver 4.1.4 + node 14.19.1 - SIGSEGV on linux, but success on windows

user91473 — Sun, 24 Apr 2022 13:39:40 GMT

Hi,
Just an update that we also tried to build both pc-ble-driver and pc-ble-driver-js from source, and we still receive the same error both on api v2 and v5:

cloning pc-ble-driver + git checkout v4.1.4
cloning pc-ble-driver-js + git checkout v2.8.2
Add to CMakeLists in pc-ble-driver repo (so that the targets.cmake file is created):

export(TARGETS nrf_ble_driver_sd_api_v2_static NAMESPACE nrf:: FILE nrf-ble-driverTargets.cmake)

export(TARGETS nrf_ble_driver_sd_api_v3_static NAMESPACE nrf:: APPEND FILE nrf-ble-driverTargets.cmake)

export(TARGETS nrf_ble_driver_sd_api_v5_static NAMESPACE nrf:: APPEND FILE nrf-ble-driverTargets.cmake)

export(TARGETS nrf_ble_driver_sd_api_v6_static NAMESPACE nrf:: APPEND FILE nrf-ble-driverTargets.cmake)

export(TARGETS nrf_ble_driver_sd_api_v2_shared NAMESPACE nrf:: APPEND FILE nrf-ble-driverTargets.cmake)

export(TARGETS nrf_ble_driver_sd_api_v3_shared NAMESPACE nrf:: APPEND FILE nrf-ble-driverTargets.cmake)

export(TARGETS nrf_ble_driver_sd_api_v5_shared NAMESPACE nrf:: APPEND FILE nrf-ble-driverTargets.cmake)

export(TARGETS nrf_ble_driver_sd_api_v6_shared NAMESPACE nrf:: APPEND FILE nrf-ble-driverTargets.cmake)
Run cmake within build folder: sudo cmake -Dspdlog_DIR=/vcpkg/packages/spdlog_x64-linux/share/spdlog -Dfmt_DIR=/vcpkg/packages/fmt_x64-linux/share/fmt -DASIO_INCLUDE_DIR=/vcpkg/packages/asio_x64-linux/include -DCatch2_DIR=/vcpkg/packages/catch2_x64-linux/share/catch2 -DNRF_BLE_DRIVER_VERSION=4.1.4 -G Ninja ..
Build: sudo cmake --build .
Change CMakeLists.txt in pc-ble-driver-js to only build v5 (by changing the foreach).
sudo node build.js --CDnrf-ble-driver_DIR="/pc-ble-driver/build" --CDCMAKE_CXX_FLAGS="-I /pc-ble-driver/include/ -I /pc-ble-driver/include/common -I /pc-ble-driver/include/common/sdk_compat -I /pc-ble-driver/include/common/config -I /pc-ble-driver/include/sd_api_v5"
Remove CMakeCache.txt from build
Change CMakeLists.txt in pc-ble-driver-js to only build v2 (by changing the foreach).
sudo node build.js --CDnrf-ble-driver_DIR="/pc-ble-driver/build" --CDCMAKE_CXX_FLAGS="-I /pc-ble-driver/include/ -I /pc-ble-driver/include/common -I /pc-ble-driver/include/common/sdk_compat -I /pc-ble-driver/include/common/config -I /pc-ble-driver/include/sd_api_v2"
After this, build/Release will hold both node bindings files. Move them to the node_modules/pc-ble-driver-js/build/Release folder.

After this, we still receive the same serialization error.

Roi

RE: pc-ble-driver-js 2.8.2 + pc-ble-driver 4.1.4 + node 14.19.1 - SIGSEGV on linux, but success on windows

user26071 — Tue, 19 Apr 2022 14:25:18 GMT

Hello,

I will have to forward this to our serialization team. I will let you know when I hear from them.

Best regards,

Edvin