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

Hi, Due to the late release of Zephyr v1.7 and the infrastructure move to github, the TSC has decided to extend the merge window until May 19th. All major changes and feature submissions have to be

Hi Erwan I've taken another look at Christer Weinigel's patched for USB on STM32F4 recently. I'm having a problem with the new LL clock code. I applied the following patch to Christer's work in

So the sensor API (like most things in Zephyr) doesn't specify much in the way dynamic behaviour, or implementation or usage constraints. Specifically in this case, how often trigger handlers get

Be sure to also get the data sheet for the device attached to SPI or I2C. There are configurable options you must do correctly to communicate properly to the device on the other side.

Have you looked at the gpio sample under samples/drivers/gpio? It’s just “GPIO_0”, and it depends whether the app is built for ARC or x86. For x86, it can be built with: $ make

Hi Iam using zephyr 1.6.0 downloaded from the site If I need to toggle a simple GPIO on the Sensor subsystem, In the Kconfig file of the ARC Config options given are GPIO_QMSI , GPIO_QMSI_SS

Hi Mahendravarman, You might try to look at the samples folder in the repository. The below examples are using I2C and SPI on

Hello, Although they are not specific to ARC, you can look over most of the sensor drivers (in drivers/sensor/) for use of I2C and SPI. Use of the I2C/SPI API is the same regardless of the platform,

Hi Team Do you have any sample/example of Using I2C or SPI driver of ARC ( sensor subsystem) in Quark_se ? Thanks

Hi Steve, We do have a plan to provide drivers for most of the nRF5x peripherals by reusing parts of the code that already exists in the standard Nordic SDK. The work has already started and I

Hi folks, I’m sorry if this gets asked a lot but I’m looking for info on the timeline for supporting nrf52 HW PWM and ADC. I’ve started migrating a project over but thats going to be a

Hi Team Do you have any sample/example of Using I2C or SPI driver of ARC ( sensor subsystem) in Quark_se ? Thanks

To answer your initial question, below example should work struct device *uartGPS; uartGPS = device_get_binding(CONFIG_UART_STM32_PORT_1_NAME); while (1) { unsigned char recvChar;

The main reason is that I hadn't thought of doing so ;-) Just had a look at the sensor APIs and they could possibly work. Two immediate questions spring to mind. 1. How to handle screen

Hi Dhamu, I saw the task you entered in Jira afterwards and now better understand your question. Indeed, you might need additional settings to get these ports working: One point is that you should