Project

General

Profile

Actions

Bug #12

closed

Can't get data from BLE sensor

Added by Emmanuel Jubera [SAFT] over 2 years ago. Updated almost 2 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Valentin LEFEBVRE [IoT.bzh]
Target version:
Start date:
05/04/2022
Due date:
% Done:

0%

Estimated time:
Hardware platform:
Solidrun (aarch64)
OS Affects Version/s:
arz-1.0
OS Fix Version/s:
arz-1.0.1
Labels:

Description

When using the iPad in order to monitor the battery, no data from the BLE sensor get displayed.

Some bluetooth related errors can be found in the system log:

bluetoothd[375]: Failed to open RFKILL control device
bluetoothd[375]: Unable to open adapter storage directory: /var/lib/bluetooth/48:EB:62:C6:26:B5

"rfkill" command in poc-service script fails the same way and the reason seems to be that file /dev/rfkill doesn't exist.

I tried to reinstall the package providing "rfkill" (util-linux) but it didn't create the missing file.

On my openSUSE machine I see there's a driver named "rfkill" which isn't present on the redpesk image, could be the root cause maybe...

Actions #1

Updated by Vincent Rubiolo over 2 years ago

  • Assignee changed from Vincent Rubiolo to Valentin LEFEBVRE [IoT.bzh]
Actions #2

Updated by Emmanuel Jubera [SAFT] over 2 years ago

From what I read on the "rfkill" topic, it seems it can be either a module or an executable. This has to be decided when building the Linux kernel by setting variable CONFIG_RFKILL to either 'm' or 'y'. On the redpesk image I use, /proc/config.gz indicates CONFIG_RFKILL wasn't set at all so I guess setting it to 'y' and rebuilding the kernel should fix the problem.

Actions #3

Updated by Valentin LEFEBVRE [IoT.bzh] over 2 years ago

  • Status changed from New to In Progress

Thank for your report and your analyses. Indeed, our new solidrun image has a missing driver. We are adding this one, and we will take the opportunity to integrate the new Solidrun patches which improve the BLE activation on your solidsense board

Actions #4

Updated by Vincent Rubiolo over 2 years ago

  • Status changed from In Progress to Closed

Emmanuel confirmed today the issue is gone in the latest builds and images.

Closing as a result.

Actions #5

Updated by Sebastien Douheret [IoT.bzh] about 2 years ago

  • OS Affects Version/s arz-1.0.0 added
Actions #6

Updated by Sebastien Douheret [IoT.bzh] almost 2 years ago

  • Target version changed from arz-1.0-update to arz-1.0.1
  • OS Affects Version/s arz-1.0 added
  • OS Affects Version/s deleted (arz-1.0.0)
  • OS Fix Version/s arz-1.0.1 added
Actions

Also available in: Atom PDF