Given that there are other parties that have an interest in lwm2m, I think we should put our focus into supporting newtmgr for upgrades. The other protocols (lwm2m, and USB DFU) will probably be

How this works in Mynewt (and will with Zephyr, if we use newtmgr) is that mcuboot has two partitions: slot0 is where the primary code lives, and slot1 is where the upgrade is written. It can be

I had a conversation with Sterling Hughes yesterday, and he explained that this was pretty much the primary reason for developing the news manager protocol instead of just using lwm2m. This is the

Hi, i am looking for a solution like that and just want to contribute my requirements. My devices are in a BLE mesh network with no direct internet connectivity to the outer world. The user can

Hi Richard,

Hi Community, i would like to use zephyr with an external bootloader like the Nordic DFU, where i can update firmware via bluetooth. There is no documentation in zephyr, how to achieve this. Do i

Hello,

Hi Andrew,

Hi David,

It is still possible to assert bit-field implementation (static assert). Then in case of incompatibilities we will have an early porting alarm. This could be done even once for a SoC. Andrzej

Boie, Andrew P wrote: Yeah, this is sorta wrong. GCC[1] is AFAIK consistent and sane within a single architecture, but the packing order varies between endianness conventions and officially they

I think we have a fair number of drivers that define structs that use the above technique, to have fields in the struct which correspond to particular bits in a register. Or see the data structures

One other protocol I just realized is already out there is lwm2m. There is starting to be some support for it in Zephyr, it works over other transports, supports device management, and has support

I believe the answer is that the transition to using the DTS will occur when the structure generation support is solidified. If you look at the outdir/<STM board>/include/generated/ directory you will

surfing in the sources tree I can find dts/arm/st/stm32f412-pinctrl.dtsi usart3_pins_a: usart3@0 { rx_tx { rx = <STM32_PIN_PB11 (STM32_PINMUX_ALT_FUNC_7 | STM32_PUSHPULL_PULLUP)>; tx =

Hi David, Thanks for the feedback.

My first suggestion. Unless we are stricly implementing the USB DFU protocol, we really should call this something else. DFU is defined by USB standards, and is a very specific protocol with a very

Hi Johann, Thanks for the feedback.

Hi, That surprised me a little, can you describe it in more detail what you mean with "it maps specifically to particular USB endpoints and classes". I think if you have USB, then USB DFU is the most

Hi all, As you might already know, we've been working on the introduction of DFU (Device Firmware Upgrade) to Zephyr. Several Pull Requests have been posted dealing with the low-level flash and image