Hi All, I have been working on RPL node example(which is in zephyr/samples/net/rpl_node), to work it as both central and peripheral concurrently. I have successfully integrated peripheral code with

Hi Carles, I am trying to build Zephyr to fit in a memory constrained device of 64kB. My device doesn’t require multithreading and hence I disabled multithreading to save on the memory. However,

Hi, I'm working on creating a custom out-of-tree board with soc for the Terasic SocKit board. Though there are certainly many things not done correct yet, I'm currently stuck at linking the simple

Hello Jukka, "Jukka Rissanen" <jukka.rissanen@...> wrote: Well, I kinda was interested in this, given all my criticism of the older API and implementation. But I'm in reservations after

Hello, currently Zephyr has HTTP server & client APIs that are built on top of net-app API. As we are currently trying to deprecate the net-app API, the HTTP APIs would need to be rewritten to use

Hi Martin, We’re not trying to enforce anything like that as receivers. As senders it’s also not really possible to exceed it currently. Even with the minimum advertising interval (20ms) and

Hi, the Bluetooth Mesh Profile specification says that "A node should originate less than 100 Lower Transport PDUs in a moving 10-second window." on p. 94. Can anyone tell me if Zephyr OS is observing

There is no requirement to copy the data, but usually, usb device drivers copy the data to the controller FIFO. There is no defined data size limit when calling the function, but at then end, driver

+ Johann, Andrei, Pawel

Hi all, I see many USB controller drivers implement usb_dc_ep_write function with one copy, copy the data (passed to usb_dc_ep_write) to one self’s buffer then do the transfer. Do I need do this

Thanks Carles, I have realized it.

Hi Robert, Can you please open a GitHub issue and assign it to @jhedberg ? Thanks, Carles

Hi Akash, Look the at the hardware information and setup procedure in "samples/net/rpl_border_router/README.rst". - Ravi

Hi There is a platform_whitelist in the sample.yaml file. In your case: "platform_whitelist: frdm_k64f " So you need this nxp board or have to port the sample

Hi All, I have been working on ipv6 over ble on zephyr RTOS to form mesh network.I have been successfully integrated "rpl_node"(which is in zephyr/samples/net/rpl_node) with ble(nrf52832), and it has

Hi there, If you are building the hci_uart then CONFIG_BT_PRIVACY is irrelevant because it’s only tied to the Host. What you need is CONFIG_BT_CTLR_PRIVACY, which enables privacy in the

In the "soc/arm/nxp_imx/mcimx7_m4/Kconfig.defconfig.mcimx7_m4" we default the GPIO config to "y" which will make the GPIO_IMX config default to "y" as well. I think you can have "CONFIG_GPIO=n" in

Hello, I am new zephyr user and I try to integrate the Pico-Pi i.MX7D board, during my compilations, I have this warning : warning: 'imx_gpio_driver_api' defined but not used

Hi, For me only x86 works. Regard, Flavio Ceolin

Hello, I'm new to zephyr and yet working on examples. I like the modular structure of arch, toolchain, board and the use of cmake. Thats just what I was tweaking around with. Also was thinking to use