Hi all,

A rework of the ADC driver API is now ready and existing ADC implementations are being ported to the new API. You can check out the PR [1] with the API and a reference implementation for more details.

However, the Atmel SAM ADC (AFEC) driver [2] is currently orphan of a maintainer and we are asking for help to port this driver to the new API. If you have experience with this SoC family and want to contribute a port, you can do so in a PR or branch that we can later include when the new API and adapted implementations are merged.

Thanks in advance on behalf of the Zephyr TSC.

Regards,

Carles

[1] https://github.com/zephyrproject-rtos/zephyr/pull/7691
[2] https://github.com/zephyrproject-rtos/zephyr/blob/master/drivers/adc/adc_sam_afec.c

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: /usr/bin/python3 (found suitable version "3.6.5", minimum required is "3.4") 

-- Selected BOARD sodaq_one_v3

Zephyr version: 1.12.99

Parsing Kconfig tree in /home/leonard/gitrepo/zephyr_fork/Kconfig

Using /home/leonard/gitrepo/TravailBachelor/src/Zephyr_sodaq_one_v3/boards/arm/sodaq_one_v3/sodaq_one_v3_defconfig as base

Merging /home/leonard/gitrepo/TravailBachelor/src/Zephyr_sodaq_one_v3/prj.conf

-- Generating zephyr/include/generated/generated_dts_board.h

Error: sodaq_one_v3.dts.pre.tmp:164.21-22 syntax error

FATAL ERROR: Unable to parse input tree

CMake Error at /home/leonard/gitrepo/zephyr_fork/cmake/dts.cmake:83 (message):

  command failed with return code: 1

Call Stack (most recent call first):

  /home/leonard/gitrepo/zephyr_fork/cmake/app/boilerplate.cmake:275 (include)

  CMakeLists.txt:9 (include)

As soon as I comment the following block in my dts file it works again. So I assume that it is related to the new atmel,sam0-i2c binding I added.

I added the atmel,sam0-i2c.yaml file in dts/bindings/i2c but I'm not sure if I missed something elsewhere?

&sercom3 {

status = "ok";

compatible = "atmel,sam0-i2c";

clock-frequency = <I2C_BITRATE_FAST>;

#address-cells = <1>;

#size-cells = <0>;

};

Thank you,

Léonard.

On 2 July 2018 at 09:13, Erwan Gouriou <erwan.gouriou@...> wrote:

Hi Léonard,

Some additional information on build error would help to provide you support.

Cheers

Erwan

On Sun, 1 Jul 2018 at 13:37, Léonard Bise <leonard.bise@...> wrote:

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 zephyr/dts/bindings/i2c/atmel,sam0-i2c.yaml and hitting a wall.

---

title: Atmel SAM0 SERCOM I2C driver

id: atmel,sam0-i2c

version: 0.1

 

description: >

    This binding gives a base representation of the Atmel SAM0 SERCOM I2C driver

 

inherits:

    !include i2c.yaml

 

properties:

    compatible:

      type: string

      category: required

      description: compatible strings

      constraint: "atmel,sam0-i2c"

 

    reg:

      type: array

      description: mmio register space

      generation: define

      category: required

 

...

Then in my board dts I added the following:

&sercom3 {

status = "ok";

compatible = "atmel,sam0-i2c";

clock-frequency = <I2C_BITRATE_FAST>;

#address-cells = <1>;

#size-cells = <0>;

};

But something is missing because I keep getting an error when building that it cannot parse the device tree.
I looked around how the other SAM0 device are setup but I didn't find what I'm missing.

Any pointer on how I should go about setting up this binding ?

Best regards,
Léonard.

Hi Léonard,

Some additional information on build error would help to provide you support.

Cheers

Erwan

On Sun, 1 Jul 2018 at 13:37, Léonard Bise <leonard.bise@...> wrote:

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 zephyr/dts/bindings/i2c/atmel,sam0-i2c.yaml and hitting a wall.

---

title: Atmel SAM0 SERCOM I2C driver

id: atmel,sam0-i2c

version: 0.1

 

description: >

    This binding gives a base representation of the Atmel SAM0 SERCOM I2C driver

 

inherits:

    !include i2c.yaml

 

properties:

    compatible:

      type: string

      category: required

      description: compatible strings

      constraint: "atmel,sam0-i2c"

 

    reg:

      type: array

      description: mmio register space

      generation: define

      category: required

 

...

Then in my board dts I added the following:

&sercom3 {

status = "ok";

compatible = "atmel,sam0-i2c";

clock-frequency = <I2C_BITRATE_FAST>;

#address-cells = <1>;

#size-cells = <0>;

};

But something is missing because I keep getting an error when building that it cannot parse the device tree.
I looked around how the other SAM0 device are setup but I didn't find what I'm missing.

Any pointer on how I should go about setting up this binding ?

Best regards,
Léonard.

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 zephyr/dts/bindings/i2c/atmel,sam0-i2c.yaml and hitting a wall.

---

title: Atmel SAM0 SERCOM I2C driver

id: atmel,sam0-i2c

version: 0.1

 

description: >

    This binding gives a base representation of the Atmel SAM0 SERCOM I2C driver

 

inherits:

    !include i2c.yaml

 

properties:

    compatible:

      type: string

      category: required

      description: compatible strings

      constraint: "atmel,sam0-i2c"

 

    reg:

      type: array

      description: mmio register space

      generation: define

      category: required

 

...

Then in my board dts I added the following:

&sercom3 {

status = "ok";

compatible = "atmel,sam0-i2c";

clock-frequency = <I2C_BITRATE_FAST>;

#address-cells = <1>;

#size-cells = <0>;

};

But something is missing because I keep getting an error when building that it cannot parse the device tree.
I looked around how the other SAM0 device are setup but I didn't find what I'm missing.

Any pointer on how I should go about setting up this binding ?

Best regards,
Léonard.

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 managed to operate the RN2483 LoRa chip through UART.

 

This board has an uBlox EVA 8M GPS and LSM303AGR Accelerometer connected to the I2C bus (SERCOM3) which I'm trying to configure properly.

 

My problem is that the other SAM0 Family boards supported don't mention any I2C in their configuration.

I was expecting of finding something like for the UART/SPI i.e. CONFIG_I2C_SAM0 but it doesn't exist. I found however a generic SAM one, can I use this one? (CONFIG_I2C_SAM_TWI).

 

Any pointer on how to configure the i2c device please?

 

Thank you,

Léonard.

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 0 */

pinmux_pin_set(muxa, 12, PINMUX_FUNC_C);

pinmux_pin_set(muxa, 13, PINMUX_FUNC_C);

#endif

board.h

/* SERCOM2 LoRa UART on RX=PA13/pad 1, TX=PA12/pad 0 */

#define CONFIG_UART_SAM0_SERCOM2_PADS \

(SERCOM_USART_CTRLA_RXPO(1) | SERCOM_USART_CTRLA_TXPO(0))

sodaq_one_v3.dts

&sercom2 {

status = "ok";

compatible = "atmel,sam0-uart";

current-speed = <57600>;

};

I created a test program similar to samples/subsys/usb/cdc_arm

In my test program I get the device like so.

lora = device_get_binding(ATMEL_SAM0_UART_42001000_LABEL);

I didn't find any documentation on how to determine the device names and I'm not sure it's the correct one, could someone enlighten me?

However as soon as I enable the RX or TX IRQ I'm stuck in an interruption loop so I guess something must be off with my configuration.

Best regards,

Léonard.

On 1 June 2018 at 19:03, Henrik Brix Andersen <henrik@...> wrote:

Hi Léonard

> On 18 May 2018, at 11.56, Léonard Bise <leodido99@...> wrote:
> I'm going to work on a project which is going to use the SODAQ One board (https://shop.sodaq.com/en/sodaq-one-eu-rn2483-v3.html).

Sweet.

> In the supported hardware I see that the Adafruit Feather M0 Basic Prot is listed, which has this exact same microcontroller. I also read the Board Porting Guide and as I understand it basically I'd need to take the Adafruit configuration as a base and add these new components to the kconfiguration. All of the aspects related to the microcontroller are already there.

I did the port to the Adafruit Feather M0 Basic Proto. Let me know if I can help with the port for the SODAQ board.

> In particular I'm also wondering how to handle the LoRa microchip, since Zephyr has no LoRaWAN stack what would be the best way to handle the porting of this part?

Perhaps a simple solution could be to just add a sample application using the LoRaWAN chip over UART from the application layer?

Best regards,
Brix
-- 
Henrik Brix Andersen