Hi, We have just posted 0.9.1-rc of the Zephyr SDK. The major changes since the last release bring support for building the Xtensa architecture using GCC and support for running Zephyr inside Qemu.

If we rely on stm32cube SDK, compilation switch "STM32F103x8" was not created because STM32F103xB was enough to specify both STM32F103x8 and STM32F103xB from software point of view. One difference

As it happens this is the other reason that I'm reluctant to make a pull request of the current code base. I've not heard of anyone getting the existing DW driver working on STM32. I certainly agree

Hi Daniel, Thanks for the branch, I'll eventually experiment it on the L4 boards aswell. But, these STM32 SoCs embeds all the same Synopsys IP, except FS one uses a register to power up the internal

Hello, I want to build my own "Security Camera" with Zephyr. For that I am looking for the right board to interact with my USB Webcam. Which board will be the best for such an application? Thanks,

Hi Erwan, Thanks, I did notice that. Infact that's the reason I ORed it to existing headder. But was unsure since none of the existing includes had a anything ORed with them. Perhaps, we should OR all

Yes! It solves the problem in the sense that devices are now enumerating correctly! However I'm afraid that the code isn't really robust enough for me to contemplate a pull request at this point

According to ext/hal/st/stm32cube/stm32f1xx/soc/stm32f1xx.h, you should use STM32F103xB: /* #define STM32F103xB */ /*!< STM32F103C8, STM32F103R8, STM32F103T8, STM32F103V8, STM32F103CB,

Hi Siddharth, Thanks for the update. I'll have a look about STM32F103x8 and get back to you. This is indeed strange not having a define for this part. Erwan

Hi Erwan, Thanks for your speedy response, that was very helpful. After adding the pin mux settings, I was able to get the UART to work. I added a new CONFIG value for STM32F103X8 and had to do a

+list Please remember to keep the list in CC.

Hello, I want to represent my sensor values which are collected with the Arduino DUE in the web over WiFi. For Example in thingsboard.io. How is it possible to realize this? Thanks in AdvanceKevin

Hi Kevin, Temperature sensor support is working in Zephyr. You can search the samples/ directory for the string "SENSOR_CHAN_TEMP" to find example code which reads temperature

Hello, is it possible to read values from not supported sensors, like temperature senors. And how is this possible. Thanks, Kevin

I took a quick look at this. It didn't "just work" for me but I am pretty short of time today and a couple of other things didn't "just work" either (and they should have done). I will get back to

Hello, Given that initial prototyping was complete and issues were identified and at least workarounds exist, I started process of refactoring the code into the in-tree

Hi Daniel, I think I spotted the bug, which is indeed in the commit you pointed. It appears with current code (stm32_clock_control_on), you can't activate AHB2 clock on F4. I've pushed following

Hello Siddharth, It seems your porting miss the pinmux configuration driver file, cf: drivers/pinmux/stm32/pinmux_board_nucleo_f103rb.c Then, you'll have to create a new CONFIG value

Hello, I want to represent my sensor values which are collected with the Arduino DUE in the web over WiFi. For Example in thingsboard.io. How is it possible to realize this? Thanks in Advance Kevin

Hello, I am trying to port Zephyr into one of the cheap, breadboard friendly, "STM32F103C8T6 Minimum System Development Boards" (link not attached due to overwhelming results in Google) and I am