Re: STM32 Support Roadmap

Daniel Thompson <daniel.thompson@...>

On 22/05/17 13:40, Neil Armstrong wrote:
Hi Paul,
On 05/22/2017 02:04 PM, Paul Sokolovsky wrote:
Hello Neil,

I'm surprised to not see USB (at least device-side) support below. I'd
think USB is a popular and generic interface to pose enough interest
for wide array of users, and indeed, I know that there're different
parties interested in STM32 USB support, though apparently critical
mass is still lacking.
Yes, but since you were already working on it, I removed it from the list.

But Yes, it is important, and having a clean support here is critical.
If you're talking about my picking up Christer's previous work I'm only experimentally kicking the tyres here (and mostly in my spare time); I'm not working to any particular roadmap...


Besides usefulness of USB on its own, there would be following reasons
to give priority to USB:

1. Intel Quark appears to be the only SoC in Zephyr with USB support.
That means that USB support in Zephyr is in general skewed, e.g.
recently there were patches to generic USB examples to workaround
issues seen on just Arduino 101.
I still plan to take a look on the DW code and make it work on F4/L4...

2. USB support is required e.g. for Zephyr.js WebIDE: , which can make a cute demo
engineers can show to managers to prove that Zephyr already can do cute
things, to back increase of timeshare they spend working on Zephyr ;-).
Yes, it could help !


On Mon, 22 May 2017 10:38:27 +0200
Neil Armstrong <> wrote:

Hi Erwann, Zephyr community,

I'm wondering about the next steps for the STM32 Platform support.

First of all, I'm still trying to push a SPI driver for STM32Lx, but
it seems it could work on STM32Fx platforms but it will lack the
clean CS management introduced in the Lx serie. I still need to
update it to the new SPI API.

I started trying to make the FMC work for PSRAM, SRAM and NOR devices
work, but is there a plan to support external memory-mapped devices ?
It's the same question for the QSPI mapped support. Some API should
be added to support dynamic mapping/unmapping, write protection and

Other useful devices would be the I2C (for !Lx), ADCs, RTC, CAN and
integration with the DMA controller introduced earlier by Lee Jones.
(Since the F4x and L4x flash drivers has been merged, the F3x should
also be merged, but I need some testers since I do not own any F3x

Finally, a strong point would be support for Ultra Low power modes
and dynamic SYSCLK switching, what is the stays of that for the
global Zephyr codebase ?


Zephyr-devel mailing list

Join to automatically receive all group messages.