Thought that myself, but with %u you get: In file included from

Since the type is 'uint32_t' rather than 'unsigned' the correct specifier is: PRIu32 e.g. #include <stdint.h> printf("blah %" PRIu32 " more blah", v); Cheers /Marcus

Hi Kumar, The right format specifier for unsigned integers is %u and not %d, so as far as I see that's the issue and using %u should make the error go away. Johan

Hi, [Second attempt at responding, my arm email address seems to have triggered a moderator approval, sorry about the duplication for those of you that got a direct reply.] This is because the code

Hi, This is because the code is using the wrong format specifier, see JIRA-1181 Cheers /Marcus IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be

It looks like newlib and our mini libc define uint32_t differently and this causes issues with the printf format warning from gcc. We get things

Hi David, If I’m not mistaken the Mynewt bootloader includes support for serial “DFU” (more like app image management and transfer). Are you planning to port that as well as part of the mcuboot

[...] So, when I add DMA support to my uart, everyone project that uses a UART, or device attached through a UART, needs know the magic device specific configuration required and add it their

Hello, is anybody tried to realize composite USB-device? Any hints? Examples? Thank you.

Which STM32 discovery board do you have, this is possibly the best starting point to try and get zephyr up and running. What kinda of work or code have you developed in the past? Any particular area

The DMA API can be used by drivers for DMA operations IMO, ideally the SPI driver should call the DMA API to implement the DMA support. However, I think this is up to the driver to decide to use the

Just to clarify my previous answer which is meant to say that there are existing usage cases a driver use API from another driver. (e.g some sensor drivers uses I2C driver API) For the channel

Baohong,

Dear Sirs, Does Zephyr have SSH support? Thank you.

Hi Erwan, well, it wasn't too hard. Almost everything is already implemented in the STM Cube drivers and only a little bit of glue code was needed. I've only implemented the functions needed by the

We are working on the Mynewt bootloader (which is going to be its own project, called mcuboot). I have the OTA update as something that needs to be done, but I'm not aware of currently plans to

Hi All, Hope everybody is doing well. I recently joined the zephyr devel mailing list and going through the documentation and other starters stuffs as being new to open source development. I want

Hi Johann, Ok sound like it could use the actual RAW use of the driver. So you would need 2 function: - one returning the supported modes - one running the test with requested mode as you

Hi Erwan, It looks quite similar, if I understood this correctly, he's also added some macros to combine the pull up/pull down/function with the alternate function in one

Hi Tomasz, No, it just for the PHY (RF Testing, simular to BT DTM, e.g. DTM_PKT_PRBS9 or CARRIER_TEST ...). It would also needs a shell command. -- Best Regards, Johann Fischer