According to Mesh Profile 4.3.2.27, this is an acknowledged message. The implementation in cfg.c:mod_sub_get doesn't seem to send the ack, just the subscription list. Ditto for subscription get

Hi Johan, Works like a charm. Haha, completely forgot about having to flash the BLE core with hci_uart. My firmware was still at 1.8.0. Thanks Johan and Vinayak, you guys are the best! Thanks, Jie

Hi Jie, You still need to update the nRF51 on the tinyTILE with a new hci_uart application based on latest master branch. You're now getting errors because the controller-side firmware doesn't yet

Hi Johan, Thanks for the clarification, below is my scan_adv output from the most recent master branch. MAC address still changes. I can see there are three warnings causing it to default into

Hi Jie, You need to use the master branch as I suggested. Not 1.9.1. I don't think the necessary patches are part of any release yet. I think this worked for Vinayak because with a combined build the

Hi Jie, I have tested both on upstream master and v1.9.1 (on a nRF52 though), and my boards use the same identity address as assigned by the factory and used by the Zephyr Host. I am afraid you may

Still have the same issue where MAC address changes every time. I'm in version zephyr 1.9.1

Hi, Looking at the ARM architecture code it seems that the SysTick interrupt priority is currently the same as the highest priority an application/driver can get. I.e. the same as interrupt priority

Ad 2.) You might also introduce any compiler option using menuconfig: Compile and Link Features > Compiler Options > Custom compiler options. You can for example put here "-O0" for disabling any

I see, I am using zephyr version 1.8.0. I will get back to you guys. Thanks everyone!

Hi Jie, Have you built your nRF51 and Quark SE images from the latest master branch? If not, please do so. It contains code to properly utilize the factory programmed static random address in the

Hi Vinayak, CONFIG_BT_PRIVACY=n is something I already tried, and it seems to still advertises with a temporary random static address. Here's the output of the scan/advertise the addition to the conf

Hi Jie, On all supported nRF5 based boards, a constant unique factory assigned random static address will be used across power cycles of the board as the identity address. And to use only random

Hey Johan, Thanks for the info! My objective is to have a unique and fixed BT address displayed during advertising. I want to use the manufacturer's BT address as a static address for testing

Anas, If we go into Coverity and items as a “bug” will there be some sort of automation that will generate a bug ticket in the github issues? David

Hi Jie, Usually a host stack doesn't have to do anything special with public addresses since controllers that support them come with the address pre-programmed. All you need to say is that you want

Hello,

Hi JC, One obvious thing you need to do, which nevertheless is easy to overlook, is setting Kconfig option CONFIG_DEBUG=y It disables compiler optimizations and adds debug symbols to the bin file.

I was indeed only responding on MTU handling (as both PR do in a way). As I am not using at all user APIs, I can't tell what would be the best. But the issue is mostly found in the API usage it

Regards, Anas Nashif Begin forwarded message: