Hi all, For a few months now we have been working on a meta-tool named west, designed to act both as a command-line tool to build, flash an debug Zephyr-based applications and also to manage the

Hi Frank. For NFC support with Zephyr on the Nordic HW can you have a look at the nRF Connect SDK (https://www.nordicsemi.com/Software-and-Tools/Software/nRF-Connect-SDK) For OOB support in the

Hi Johan, I was already aware this part was missing... :(. Unfortunately for the moment we are on a very strict time schedule to come up with a BLE architecture for our near future wireless

Hi Frank, Note that the APIs Rodrigo referred to are for Mesh provisioning, not for pairing. Zephyr doesn’t currently expose any OOB APIs for pairing, except bt_le_oob_get_local(), which only

Hi Rodrigo, Thanks for your valuable feedback. I will have a look at it and see how far I can get. Best regards, Frank

Frank, as far as I know, there are some functions that are being called during the provisioning process like "static int output_number(bt_mesh_output_action_t action, u32_t number)". This function (in

Hi Rodrigo, No not yet... So far I'm still in the process of trying to understand how the NFC message (as described by the Bluetooth SIG) gets into the Bluetooth SW stack for the OOB pairing process.

Frank, I have a piece of code that wakes up the MCU through NFC, but I could not write or read data from it yet. We are using only the HAL code. The only tricky is to register the interrupt with

Hi all, As far as I can see there is no real support for NFC in Zephyr. Correct? I'm really getting stuck in the LE OOB pairing process... I would really feel a pity I will need to fallback to

Hi Johan, Thanks for clarifying this one out, that is already a great relief. Honestly I'm a little bit stuck with what I want to do about security in my BLE architecture. So far I was able to combine

Hi, I wanna clarify that Black box means implementation is based on Bluetooth Mesh specification release in 2017 but it is available in close source lib. At app level there are some limited APIs to

I meant naturally bluetoothd (stupid auto-correct :) Johan

Hi, SSP is a BR/EDR feature, whereas Zephyr on Nordic MCUs only supports LE (known as a single-mode controller). So you’re not missing anything essential in this regard. The security feature in LE

Hi all, Carles, It seems when trying to set the SSP (Secure Simple Pairing) via the btmgmt tool I also get the error message the SSP is not supported for this adapter. So it seems when setting up a

Hi all, Carles, During the last months I have been doing a lot of research in BLE technologies. Finally for implementing our use case we came up with the following BLE architecture: - a Linux

Hi, Johan, I'm researching zephyr ble mesh too, have a questions to ask you: In zephyr/samples/boards/nrf52/mesh/onoff-app example, use meshctl as the provisioner and configurer, is there a

I’m here on the mailing list as well, but I don’t have much knowledge of the “black boxes” of proprietary Mesh products that Vikrant was referring to. Johan

Hi, vikrant, You can go here: https://zephyrproject.slack.com/messages/C18PLHN8H/convo/C18PLHN8H-1547649579.774500/?cdn_fallback=1 in general channel, talk to Johan Hedberg by @jhe, who's

Hello, "Jukka Rissanen" <jukka.rissanen@...> wrote: +1 for deprecation, -1 for removal in 1.14. 1.14 is supposed to be LTS release, and we shouldn't leave users who used prior versions

Here are the discussion items for today’s meeting, if you have any others let me know: https://github.com/zephyrproject-rtos/zephyr/labels/dev-review * Target Capabilities / Board Directory Layout