Hi Léonard, I've been working on adding I2C support for the SAMD21 but I don't feel it is in a state where making a pull request would be relevant: this is my first foray in Zephyr development plus I

Thanks for the additional info. It would be nice to see what at line 164 in file sodaq_one_v3.dts.pre.tmp. Anyway, my first guess would be that you miss i2c.h binding file inclusion in your dtsi

Hello Erwan, Thanks for your help. Well the thing is that is one of my problem, I don't have much to go by. All I get is a syntax error message from dtc when running cmake: -- Found PythonInterp:

Hi Léonard, Some additional information on build error would help to provide you support. Cheers Erwan

I'm trying to add support for SAM0 I2C. Currently my code is compiling as I see warnings in my i2c_sam0.c file. However I'm trying to add a new binding for that in

Hello Michael, I would be willing to try at least. Hopefully with some guidance it wouldn't be too hard. I'm currently setting up my fork to have a clean dev env. Just so I'm clear on what exactly

I'm currently working on the board configuration for the SODAQ One which is very similar to the Adafruit Feather M0 already supported by Zephyr. Console is working and I setup the SPI bus. I also

Hi Leonard. I did a bit of the original SAMD21 bring up. There's no support for I2C ATM but you're welcome to add it.

I'm currently working on the board configuration for the SODAQ One which is very similar to the Adafruit Feather M0 already supported by Zephyr. Console is working and I setup the SPI bus. I also

Hi, How to reduce time required to "provisioning + reconnection to proxy service" (in case of OOB authentication disabled) compared to default configuration ? Thank You !!

Hi You could also try following patch which is currently under review: https://github.com/zephyrproject-rtos/zephyr/pull/7034#issuecomment-401265397 Regards, Ismael

Back again! So this is weird because I got it working but without TX interrupts. RX interrupts work fine however as soon as I enable TX interrupts with uart_irq_tx_enable I enter an interruption

550uA usually means that the HFCLK is running. The HFCLK will run when something (peripheral) needs it. You need to find out what is using it, unfortunately neither the HW or the SW is able to tell

Hi all, I've ran some power consumption tests with Zephyr 1.12 #... a00646a5 Using the samples/boards/nrf52/pwr_mgr at lowest power mode, I find that the nrf52840 has a sleep current of ~550uA. When I

I'm having difficulties trying to communicate with the LoRa UART interface. I set it up like so: pinmux.c #if CONFIG_UART_SAM0_SERCOM2_BASE_ADDRESS /* SERCOM2 LoRa UART on RX=PA13/pad 1, TX=PA12/pad

---------- Forwarded message ---------- From: Lubos, Robert <Robert.Lubos@...> Date: Thu, Jun 28, 2018 at 1:14 PM Subject: RE: [Zephyr-users] OpenThread example from embedded world conf #nrf52840 To:

There are still buffer/variable overflow problems, so I would make sure those are fixed before trying to figure out why else it might not be working. For example: char buffer[2]; ...

I'm back again! I think I sent the last mail only to Brix by mistake. I'm happy to say that I fixed my issue... I needed to set my pin mux function as D not C. #if

Hi there, I just tried this but instead of using menuconfig I changed my prj.conf like this: diff --git a/samples/bluetooth/peripheral_hr/prj.conf

Hi Tamra, The format of the data (behind ad->data with length ad->len) is specified in the Bluetooth Core Specification (5.0) Volume 3, Part C, section 11 (page 2086 in the pdf). In practice it's