Hello, I am working on a project using Mesh with nrf52 boards. I have 3 boards for now, two of them are in a mesh network (boards A and B) (I will have more later to hava a real mesh network), and the

Hi Carles, Finally I got it up and running :). So indeed changing the pinning in the overlay file did the trick, although I also had to redefine the cts/rts despite not using them as one of the values

Hi, Yes, it is recommended to use counter API instead. Regards, Krzysztof From: devel@... <devel@...>On Behalf Of Aaron Xu via Lists.Zephyrproject.Org Sent: Tuesday, April 9, 2019 3:44

Hi, I just heard rtc api is deprecated, but I can not find any clue in the documentation or in this mail list. What's that mean? Should we avoid to use rtc api in the future and change to counter

Hi there, The default PINs are configured in the board .dts file: https://github.com/zephyrproject-rtos/zephyr/blob/master/boards/arm/nrf52_pca10040/nrf52_pca10040.dts#L95 You can indeed

Hi Zephyr community, So far I couldn't see where the default UART rx/tx pin mapping (RX = 8 and TX = 6) is happening in the Zephyr code. I want to run the hci_uart on the nRF52832 SoC to implement

Hi Henry, I wonder if this could be related to the lack of buffers on the host, I assume you would use bt_gatt_notify with NULL conn which will take care of notifying each connection but that may end

Hi Johan, Thanks for the prompt reply, this is useful for me. I think it's good idea to become a contributor of Zephyr project. Regards, Kai On 2019/4/5, 11:09 PM, "Hedberg, Johan"

Hello, I'm working on an project that involves Open Supervised Device Protocol (OSDP) [1], an access control communication protocol used in the security industry. I'm working on this as an

Hi All, I am kind of new to Zephyr dev community. Previously our team was using Zephyr without actively involved in kernel development. Recently we just noticed that RPL module will be removed in

Hi Kai, The API to get information on a connection is bt_conn_get_info(). Out of the parameters you mentioned you can get at least get the interval, however DLE or PHY information is not currently

Hello, I’m trying to find the APIs on Zephyr,https://docs.zephyrproject.org/latest/reference/bluetooth/index.html ,using these APIs can get ConnInterval, whether Data Length Extension is enable or

"Does the ". = 0x1000;" indicate the padding?" Yes, you would want to compare it to the source to see what it's trying to do, and possibly how to make it

Hi, That's where I'm not sure on, I see the fill section but can't work out where it's coming from: Memory Configuration Name Origin Length Attributes FLASH

Okay, if I was you I would have a look at the map file and try to figure out what it's putting there and why. ________________________________________ Sent: Thursday, April 4, 2019 2:34 PM To: Bøe,

Hi, I have tried that but it still pads the first section with 0x00 bytes. I'm using a custom board file and project so tried switched to trying it with the hello world sample using the

Hi, try enabling CONFIG_BUILD_NO_GAP_FILL IMHO this should be the default. Needing to fill the gaps is indicative of a problem elsewhere, e.g. in the linker

Hi, Is it possible when building projects to have the flash sections that are defined in thedts but unused (in this instance, the Nordic MBR) and not have them filled but instead left blank/empty? I

Hi Billy, That depends on your application and the source of the faults. All the stack requires is for you to keep track of the fault history. You could do that e.g. with a simple u8_t array like the

Hi, The Zephyr mesh health server leaves fault registration up to the application, however you do need to register a bt_mesh_health_srv_cb struct which includes callbacks for retrieving the faults,