Unable to get Interrupt for I2C TWIS while using AWS IoT

RE: Unable to get Interrupt for I2C TWIS while using AWS IoT

Jared — Mon, 04 Apr 2022 09:25:59 GMT

Hi,

Not sure exactly why this helped, but that config will turn on the UART since it activates the logger module.

Anyways, I'm happy that you returned with the solution. I'm sure it will help others on this forum.

best regards

Jared

RE: Unable to get Interrupt for I2C TWIS while using AWS IoT

Nikone — Sun, 03 Apr 2022 12:31:08 GMT

Hi Jared, sorry for my late reply.

In the end i solved the problem by removing the line

CONFIG_NCS_SAMPLES_DEFAULTS=y

from the prj.conf file.

I tested this by adding all the prj.conf lines one by one to a project with only the i2c part and the spm were present until i found the line that was blocking the i2c peripheral.

I'm not sure why this configuration was causing problems but i think is related to the spm.

Thank you for your time, i hope that my solution will be helpful to others

RE: Unable to get Interrupt for I2C TWIS while using AWS IoT

Jared — Wed, 30 Mar 2022 12:35:59 GMT

Hi there,

Could you share your entire project?

regards

Jared

RE: Unable to get Interrupt for I2C TWIS while using AWS IoT

Nikone — Tue, 29 Mar 2022 14:59:34 GMT

Hi,

i'm able to use GPIO without any problem. I've actually added a blinking LED to help me debug the AWS IoT example when i was configuring APN and other things.

As i said before i switched to TWIS3 to try but still no luck.

I checked in the .config files both for SPM and the application and all the peripheral sharing the same ID (SPIS3, SPIM3, UARTE3) are not enabled.

To get SPI3 to be disabled i added the following to the application overlay file both in the application overlay and in the spm overlay:

&spi3 {
	status = "disabled";
};

&uart3 {
	status = "disabled";
};

Still no luck even with these

RE: Unable to get Interrupt for I2C TWIS while using AWS IoT

Jared — Tue, 29 Mar 2022 13:40:46 GMT

Hi,

Are you using any other peripheral than UART0(AWS IoT) in your example? It might be a conflict of resources if you're using more than one peripheral with the same ID. Are you able to use any other simpler peripheral such as the GPIO peripheral?

regards

Jared

RE: Unable to get Interrupt for I2C TWIS while using AWS IoT

Nikone — Tue, 29 Mar 2022 09:54:53 GMT

Hi,

Yes the AWS part is working completely fine, it's like the i2c part is not present.

As i said before i'm unable to reach interrupt on i2c messages or even get ACK, that's the strange thing.

It seems that something is interfering with the peripheral.

I event tried to move to TWIS3 but without success.

Nicolò

RE: Unable to get Interrupt for I2C TWIS while using AWS IoT

Jared — Tue, 29 Mar 2022 08:41:34 GMT

Hi,

Does the AWS IoT part work? Is there any output on the log?

RE: Unable to get Interrupt for I2C TWIS while using AWS IoT

Nikone — Mon, 28 Mar 2022 13:03:14 GMT

Hi Jared,

Yes the TWIS peripheral is running in non-secure.

Am i missing some configurations of the SPM?

Thanks,

Nicolò

RE: Unable to get Interrupt for I2C TWIS while using AWS IoT

Jared — Mon, 28 Mar 2022 12:54:35 GMT

Hi there,

What domain is the TWIS peripheral running at? Non-secure?

regards

Jared