AM3352: I2C clock stops on GPMC access

paddu2017

Part Number: AM3352

Hi,

We have a strange issue with AM335x I2C operation with GPMC TIMEPARAGRANULARITY ="0".
I2C works normal when we execute code on DDR3, but this issue(The I2C Clock output stops)
occurs when executing code from NOR(XIP) with TIMEPARAGRANULARITY=0, but Works normal when TIMEPARAGRANULARITY=1.

This is a Non-OS bare metal application.

We wonder how does a GPMC setting could effect I2C operation.
Please let us know if there is any idea on troubleshooting this issue.

Best Regards
paddu

over 8 years ago

0 Biser Gatchev-XID over 8 years ago

TI__Guru**** 393215 points

What could be happening is the GPMC taking up the entire interconnect bandwidth. Unfortunately this is a use case that we cannot replicate and debug on our side.

0 paddu2017 over 8 years ago in reply to Biser Gatchev-XID

Expert 2885 points

Hi Biser,

Thank you very much for the helpful information. Will investigate on this.

Please let us know if there is any way to check the load or bandwidth usage of
GPMC and the interconnect.

Best Regards
Paddu

0 JJD over 8 years ago in reply to paddu2017

TI__Guru* 90445 points

Hi Paddu, I don't think there is an interconnect issue. What exactly is happening on the processor? Does code still run and the I2C module is locked up? With TIMEPARAGRANULARITY=0, accesses to the NOR will be faster. Is the NOR interface timing being met in this mode? Are you possibly executing corrupt code?

Regards,
James

Processors

Processors forum

AM3352: I2C clock stops on GPMC access