thingy53 using twic qwiic boards.

RE: thingy53 using twic qwiic boards.

tldr — Tue, 30 Apr 2024 05:05:33 GMT

I found that the super cap on the board had no charge. I found the documentation to turn the trickle charger on and now the reads work fine! Thanks for the help.

RE: thingy53 using twic qwiic boards.

tldr — Tue, 30 Apr 2024 03:32:22 GMT

I found that CONFIG_RTC_INIT_PRIORITY was 50 the same as CONFIG_I2C_INIT_PRIORITY. To get the init running I changed the priority to 90 using CONFIG_SENSOR_INIT_PRIORITY.

DEVICE_DT_INST_DEFINE(inst, &am1805_init, NULL, &am1805_data_##inst, \
&am1805_config_##inst, POST_KERNEL, CONFIG_SENSOR_INIT_PRIORITY, \
&am1805_driver_api);

When I flash reset the board the following code works and err is 0:
err = i2c_reg_read_byte_dt(&config->int_i2c, REG_STATUS_ADDR, &reg);
if (err != 0) {
printk("failed to read the status register %d", err);
return -ENODEV;
}

when I reset switch the i2c_reg_read_byte_dt returns -5.
am1805_init
failed to read the status register -5

RE: thingy53 using twic qwiic boards.

tldr — Mon, 29 Apr 2024 16:17:46 GMT

When I flash and the board resets, the RTC device shows as enabled and set and get are working. When I turn off the board and turn it back on via switch, the device shows as DISABLED. Any ideas on that strangeness?

If I set the time and do multiple flashes, the time stays. Turning off and on via switch and the device is disabled. The rtc reports uninitialized time on subsequent flashes. I changed to using I2C_BITRATE_STANDARD as set was not working always using FAST.

Even when the device is showing as DISABLED.

i2c scan i2c@b000
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- 34 -- -- -- -- -- -- -- -- -- -- --
40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- --
70: -- -- -- -- -- -- -- --

I see the device in a scan.

here is the rtc device using the driver.
rv18055: rv18055@69 {
reg = <0x69>;
label = "RV18055";
compatible= "ambiq,am1805";
status = "okay";
};

RE: thingy53 using twic qwiic boards.

tldr — Mon, 29 Apr 2024 16:07:20 GMT

If you see something wrong, lmk. Here is the overlay for the next guy.

&pinctrl {

i2c2_default: i2c2_default {
group1 {
psels = <NRF_PSEL(TWIM_SDA, 0, 5)>,
<NRF_PSEL(TWIM_SCL, 0, 4)>;
};
};

i2c2_sleep: i2c2_sleep {
group1 {
psels = <NRF_PSEL(TWIM_SDA, 0, 5)>,
<NRF_PSEL(TWIM_SCL, 0, 4)>;
low-power-enable;
};
};
};

&i2c2 {
compatible = "nordic,nrf-twim";
status = "okay";
clock-frequency = <I2C_BITRATE_FAST>;
pinctrl-0 = <&i2c2_default>;
pinctrl-1 = <&i2c2_sleep>;
pinctrl-names = "default", "sleep";

rv18055: rv18055@69 {
compatible= "i2c-device";
reg = <0x69>;
label = "RV18055";
};
buzz344: buzz344@34 {
compatible= "i2c-device";
reg = <0x34>;
label = "BUZZ344";
};
};

I didn't have to change the prj.config I2C=y is enough. Thanks for your help!

RE: thingy53 using twic qwiic boards.

tldr — Mon, 29 Apr 2024 14:47:17 GMT

Thank you very much for the additional information.

added the following to the prj.conf
CONFIG_I2C_2=y
CONFIG_I2C_2_NRF_TWIM=y

added the following to the overlay

&i2c2 {

compatible = "nordic,nrf-twim";

status = "okay";

clock-frequency = <I2C_BITRATE_FAST>;

pinctrl-0 = <5>;

pinctrl-1 = <4>;

sda-pin = < 5 >;

scl-pin = < 4 >;

rv18055: rv18055@69 {

compatible= "i2c-device";

reg = <0x69>;

label = "RV18055";

};

buzz344: buzz344@34 {

compatible= "i2c-device";

reg = <0x34>;

label = "BUZZ344";

};

First I tried using sda and scl pin, which was not ok
devicetree.dtlib.DTError: expected property 'pinctrl-0' on /soc/peripheral@50000000/i2c@b000 in empty_file.c to be assigned with 'pinctrl-0 = < &foo &bar ... >;', not 'pinctrl-0 = < 0x5 >;

I've not spent much time with the pinctrl. Can you help me with the device device tree config required?

RE: thingy53 using twic qwiic boards.

Jørgen Holmefjord — Mon, 29 Apr 2024 14:25:25 GMT

Hi,

According to the Thingy53 HW files, the expansion board header is connected to GPIOs P0.04 and P0.05:

The other I2C sensor on the board are connected to P1.02/P1.03 (default pins for I2C1 node). To interface the sensors connected to the expansion board connector, you should use a separate i2c instance configured to use these GPIOs.

Best regards,
Jørgen