TDA4VH-Q1: Can I trigger in interrupt in I2C if there are no I2C devices connected ?

Hi Miguel,

What is your use case for this? Is it to solely test if interrupts are triggered on the I2C channel?

Thanks,

Neehar

Yes, that's correct.

I would also like to know if it's possible to trigger Main domain I2C interrupts from the MCU domain.

Hi Miguel,

What SDK version are you using? I will need to look into the software implementation of interrupts for I2C further.

Thanks,

Neehar

Hello, 

Hi Miguel,

I will need to look into this further, there may be a delay due to holidays in India.

Thanks,

Neehar

Hello, is there any update on this ?

Do you have any example to trigger Main Domain I2C interrupts into the MCU domain, I am running in the MCU1_0 core.

Hi Miguel, 

Our expert has been out of office. Please expect a delay in response.

Thanks,
Sarabesh S.

Hi Miguel,

Miguel Flores said:

Do you have any example to trigger Main Domain I2C interrupts into the MCU domain, I am running in the MCU1_0 core.

We do not have an example within our SDK on triggering Main domain I2C interrupts on MCU1_0, however, the EEPROM read example within the PDK performs WKUP_I2C interrupts on almost all cores such as Main R5, MCU R5, and C66x/C7x.

Thanks,

Neehar

Is there a route mapping configuration that needs to be done in order to trigger the interrupts ?

And if so, what registers should I configure ?

Hi Miguel,

The I2C example within the PDK as well as the I2C APIs show how to set up interrupts and how the routing is done.

Additionally, you can look at I2C_configSocIntrPath() API on more information on how the interrupt path is configured and what registers must be manipulated.

Thanks,

Neehar

Hello, why configuring I2C peripherals from the Main Domain using the I2c driver provided by you, an exception is reached when the addresses from the Main domain are trying to be accessed, specifically when reading from: 0x020000A4 to check the status of Main I2C0.

I am running in MCU1_0, do you have any idea why this Main domain address is not accesible ?

BTW, this behaviour happens in EV5 but not in EVM.

Hi Miguel,

Please expect a delay in responses due to holiday in the US. Thanks for your patience.

Thanks,

Neehar

Hi Miguel,

How are you trying to access the register? Are you trying to read or write?

You should have no issues accessing Main domain I2C registers even if you are running on MCU1_0.

Miguel Flores said:

BTW, this behaviour happens in EV5 but not in EVM.

Is this specifically the behavior of seeing an exception when accessing main domain addresses?

Thanks,

Neehar

I am trying to read the register.

Yes, this exception when accessing the main domain address only happens in EV5.

Hi Miguel,

What method do you use to access the register?

Miguel Flores said:

Yes, this exception when accessing the main domain address only happens in EV5.

I'm not sure what could be causing this to occur on EV5 but not the EVM.

Thanks,

Neehar

Hello, just *reg = value. Where reg is a pointer that points to the register address.

Hi Miguel,

Please ensure any configuration registers are the same running on EVM and EV5 to try to get identical setup on the devices.  

Thanks,

Neehar

Hello, what configuration registers could affect this reading ?

Hi Miguel,

Could you provide a register dump for both E5 and EVM such as I2C? I am unable to help with much debugging otherwise as you should have no issues accessing Main domain I2C registers even if you are running on MCU1_0.

Thanks,

Neehar