Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

Vidar Berg — Mon, 28 Apr 2025 07:16:36 GMT

[quote userid="134301" url="~/f/nordic-q-a/120702/peripheral-initialization-issue-after-wake-up-from-deep-sleep-nrf5340/532954"]
Have you tried to probe the bus lines with a logic analyzer or scope?
I have not tried this option.[/quote]

Please try this if possible. This will provide us with more clues.

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

REDHAT — Fri, 25 Apr 2025 06:04:06 GMT

What does "EEPROM Init successful" indicate? Were there any successful I2C transactions with the EEPROM prior to the write and read failure?

i am checking this

if (!device_is_ready(i2c_dev)) {

return AT24CM02_ERR_INIT;

}

How are sensors powered? Are they connected directly to VDD?
it connect to VDD same as controller.

Have you tried to probe the bus lines with a logic analyzer or scope?
I have not tried this option.

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

REDHAT — Fri, 25 Apr 2025 05:50:47 GMT

Hi Vidar Berg,

Sorry, while programming the device is working fine when the device is wake up from the System off mode, i am getting issue with writing and reading to the EEPROM and some I2C connected peripherals.

i want to know like do i need to take care of them before putting to the sleep or need to do some thing when the device is wake up from the system off mode.

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

Vidar Berg — Fri, 25 Apr 2025 05:37:04 GMT

Sorry, but you're only partially answering my questions and not providing enough information for me to work with.

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

REDHAT — Fri, 25 Apr 2025 05:33:54 GMT

What does "EEPROM Init successful" indicate? Were there any successful I2C transactions with the EEPROM prior to the write and read failure?
i am checking i2C is ready or not

How are sensors powered? Are they connected directly to VDD?
yes

Have you tried to probe the bus lines with a logic analyzer or scope?
no

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

Vidar Berg — Fri, 25 Apr 2025 05:15:53 GMT

What does "EEPROM Init successful" indicate? Were there any successful I2C transactions with the EEPROM prior to the write and read failure?

[quote userid="134301" url="~/f/nordic-q-a/120702/peripheral-initialization-issue-after-wake-up-from-deep-sleep-nrf5340/532934"]Do the sensors remain powered on in System OFF?

yes[/quote]

How are sensors powered? Are they connected directly to VDD?

[quote userid="134301" url="~/f/nordic-q-a/120702/peripheral-initialization-issue-after-wake-up-from-deep-sleep-nrf5340/532934"]This are those error that i am getting[/quote]

Have you tried to probe the bus lines with a logic analyzer or scope?

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

REDHAT — Fri, 25 Apr 2025 03:56:30 GMT

Hi Vidar Berg
Good day!

I don't see any references to this driver in the SDK. Is this your own implementation, or is the source code available somewhere?

#define AT24CM02_ERR_WRITE -3

#define AT24CM02_ERR_READ -4

This are those error that i am getting

Do the sensors remain powered on in System OFF?

yes

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

Vidar Berg — Thu, 24 Apr 2025 11:03:19 GMT

[quote user="REDHAT"][00:00:01.050,964] <err> Eeprom: EEPROM Read Error at address_fp_one: -4[/quote]

I don't see any references to this driver in the SDK. Is this your own implementation, or is the source code available somewhere?

[quote user="REDHAT"]I'm not getting any I2C initialization error, but the I2C-connected peripheral is not functioning properly after wake-up.[/quote]

Do the sensors remain powered on in System OFF?

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

REDHAT — Mon, 21 Apr 2025 04:32:45 GMT

Hi Asbjørn,
Good day!

We’re in a bit of a hurry and really need to resolve this issue as soon as possible. We're counting on your support and would greatly appreciate your assistance.

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

REDHAT — Mon, 21 Apr 2025 04:00:01 GMT

Hi Asbjørn,

Good day!

Kindly provide some inputs on this !!!!!!

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

REDHAT — Tue, 15 Apr 2025 12:56:53 GMT

Now it's not taking 10 seconds after wake-up from the System OFF mode, but there's an issue with I2C.

1) I'm not getting any I2C initialization error, but the I2C-connected peripheral is not functioning properly after wake-up.

First, I'm letting some peripherals initialize, and after that, I'm trying to read the EEPROM. This is the error I'm getting:

[00:00:01.050,964] <err> Eeprom: EEPROM Read Error at address_fp_one: -4

Also, some I2C peripherals are not working properly.

RE: Peripheral Initialization Issue After Wake-Up from Deep Sleep (nRF5340)

Asbjørn — Tue, 15 Apr 2025 11:54:32 GMT

Hello Pavan,

From the log you attached it seems there's a 10 second delay in the EEPROM related functionality after coming out of deep sleep.

[00:00:00.568,084] <inf> main: EEPROM Init successful
[00:00:11.108,367] <inf> main: XXXX: 120
[00:00:11.608,642] <inf> main: XXXXX: 60
[00:00:12.111,267] <inf> main: XXXXX: 20
[00:00:14.117,095] <inf> main: XXXXX: 0 | XXXXXX: 0 | XXXXX: 0 | XXXXX: 0
[00:00:24.145,904] <err> main: Failed to read XXXXXXXX from EEPROM
--- 11 messages dropped ---
[00:00:25.149,047] <inf> main: xxxxx: 10

What is running from EEPROM and what happen if you for the test skip using the EEPROM functionality, does the nRF5340 still take 10 seconds to wake up?

Best regards

Asbjørn