Hi Steve, Here's version 2. The first attempt didn't take the account the jump to a label in the success case. So ignore the earlier and test this one, please. Johan

Hi John, Didn't fix it. Identical log. Steve

Hi Steve, I went through the patch in question, and found a leak of a net_buf object. I wonder if the available buffer count has been so well fine-tuned that loosing just one causes this issue.

Hi, I am using the eclipse CDT standalone debugger without any issues. Yannis

I've been using Eclipse <https://www.eclipse.org/> + "C/C++ Hardware Debugging" plug-in for a while. It works flawlessly and is reasonably easy to setup. If you are developing on ARM there is also

The samples/bluetooth/mesh fails on my nrf52840_pca10056 Below is the debug output of both the failing and non-failing cases. I bisected down to: first bad commit:

Hi Pushpal, We are in the process of switching from Make/Kbuild to CMake. Once this transition is complete it should be possible to generate IDE projects from CMake itself, although the focus

Thanks for the suggestion Justin. Haha, by old school, I meant they are very far removed from CLI debugging through gdb (which is what I'm used to) as they've been using tools like IAR for a while.

I would look into Segger https://www.segger.com/. They make a great debugger and they have a debugger IDE. I use it with Zephyr and I code with Sublime text. Some peripherals can't be debugged with

Hi All, I'm trying to convince my company to switch to Zephyr, but the lack of an actual IDE with a nice graphical debugger startles them (these are old-school type firmware people who have gotten

Hi all, I plan to rework GPIO API to fix the issue #2529 https://github.com/zephyrproject-rtos/zephyr/issues/2529. But first I would like to clean it up a bit. One thing which is confusing and feels

Hi Tamra, This PR is merged now, so simply rebuilding and flashing your nRF51 & Quark SE Zephyr images from the upstream master branch should yield a solution where the Bluetooth address remains the

Hi Johan, Setting CONFIG_BT_MESH_ADV_BUF_COUNT to 7 solved the issue. Thanks, Jehudi 2017-10-17 12:26 GMT+02:00 Johan Hedberg <johan.hedberg@...>:

Hi Jehudi, Sorry, there's an internal define called BT_MESH_TX_SEG_COUNT, but it actually gets its value from a different Kconfig variable. From the transport.h header file: #define

Hi Johan, Thanks for the response. I couldn't find CONFIG_BT_MESH_TX_SEG_COUNT as configuration option, but I tried changing CONFIG_BT_MESH_TX_SEG_MSG_COUNT which defaults to 1. I changed it to 10

Hi Tamara, I might be wrong, but I don't think a public address is what you're looking for, since that address space is formally managed by companies. Instead, I think you're looking to get a

Hi Jehudi, I think you need to change CONFIG_BT_MESH_TX_SEG_COUNT. IIRC it defaults to 3, and with your two elements you've created a composition data that doesn't fit in three segments anymore.

Hi, I am trying to make a bluetooth mesh zephyr node with 2 elements. After provisioning (which assigns 2 node adresses) meshctl ask for the composition data. This fails with Not enough tailroom for

Hi Steve, You're right. It's an oversight that needs fixing. Friend support is not yet complete (there's just a very basic and incomplete skeleton for it), so this is less of an issue.

Hi everyone, Does anyone know how to make a device ID public instead of random? I ran the bluetooth sample, scan_adv, provided by zephyr. Below is what happens when I run it. Starting