AM6442: Cortex-M4F I2C Interface Support on AM6442 Custom Board

Hello Vaibhav,

Vaibhav Kumar said:

The assigned expert has created an FAQ which might resolve your issue: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1501801/faq-processor-sdk-am64x-not-able-to-open-i2c-drivers-for-mcu-i2c

I've implemented the changes as discussed in the thread. However, I have a doubt regarding the final step — building the library. I'm currently building the project directly, and there are no errors during compilation. But when I debug using JTAG, it seems the newly added instructions are not being considered. Could you please elaborate on the correct procedure for building the library using the provided command?

Also, if I only build the example project, does that mean the library files are not rebuilt or included in the build process?"

Please do provide your inputs on this.

Thanks and regards

Ganesh Pawar 

Hi Ganesh,

What command are you using to build the library?

ganesh pawar said:

Also, if I only build the example project, does that mean the library files are not rebuilt or included in the build process?"

Yes, the library files need to built explicitly. It is not part of example build.

First you have build the library for both release and debug profile then build the example.

Regards,

Tushar

Hi Tushar

Tushar Thakur said:

What command are you using to build the library?

Could you please assist me with building this library? I’m currently unable to get it to build successfully. I’ve attached the logs for reference.

Thanks and regards

Ganesh Pawar

Hi Ganesh,

Looks like you don't have the CCS v12.7.0 installed on your system. Can you please confirm you have the required tools installed?

Regards,

Tushar

Hi Tushar,

I’ve installed CCS v12.8.1 and can confirm that all the required tools are in place.

SDK version: mcu_plus_sdk_am64x_10_00_00_20.

Thanks and regards

Ganesh Pawar

Hi Ganesh,

You are using a CCS v12.8.1 and the gmake is looking for CCS v12.7.0. Please update the imports.mak file with correct CCS path.

After modifying the path you should be able to build the library.

Regards,

Tushar

Hi Tushar,

Thanks for your guidance on building the library image — I was able to successfully build it in both debug and release configurations.

After building both the library and the project, I tested the initialization of the I2C0 lines. However, the status still returns -3.

Observations:

 Assigned I2C base address:

         #define CSL_MCU_I2C0_CFG_BASE (0x4900000UL).

This address appears to differ from the translated address observed during runtime (as shown in the attached image).

Can we directly verify the base address using CSL_MCU_I2C0_CFG_BASE, similar to how we compare with other base addresses like CSL_I2C0_CFG_BASE, instead of relying on address translation?"

Thanks and regards

Ganesh Pawar

Hi Ganesh,

ganesh pawar said:

Can we directly verify the base address using CSL_MCU_I2C0_CFG_BASE, similar to how we compare with other base addresses like CSL_I2C0_CFG_BASE, instead of relying on address translation?"

This will not work. Whenever you change the RAT region in application the code will break if you hard code the addresses.

The changes mentioned in the FAQ should work for your case.

Regards,

Tushar

Hi Tushar

Tushar Thakur said:

This will not work. Whenever you change the RAT region in application the code will break if you hard code the addresses

What I meant was:

 (baseAddr == SL_I2C0_CFG_BASE) || (baseAddr == CSL_MCU_I2C0_CFG_BASE)

instead of 

  (baseAddr == (uint32_t)AddrTranslateP_getLocalAddr(CSL_MCU_I2C0_CFG_BASE))

If this approach doesn’t work, then despite applying the changes as per the FAQ, it’s evident that the translated address does not match the base address, resulting in a status of -3.

Since the I2C instance is not initialized, the I2C_LLD_PROBE returns the state as I2C_STATE_RESET, and the peripheral remains in a busy state.
This prevents the MCU_I2C to be available to communicate.

Is there anything additional that needs to be done to bring the I2C peripheral to an active state?
I’d appreciate your inputs on this.

Thanks and regards

Ganesh Pawar

Hi Ganesh,

ganesh pawar said:

it’s evident that the translated address does not match the base address, resulting in a status of -3.

Can you share what is the value of CSL_MCU_I2C0_CFG_BASE macro before address translation and after translation?

I have seen after applying the changes specified in the FAQ, customers are able to enable I2C communication using MCU_I2C.

Regards,

Tushar

Hi Tushar,

Tushar Thakur said:

Can you share what is the value of CSL_MCU_I2C0_CFG_BASE macro before address translation and after translation?

Here are the details on the Base address and address after Translation.

Base Address: 

     #define CSL_MCU_I2C0_CFG_BASE (0x4900000UL)
     #define CSL_MCU_I2C0_CFG_SIZE (0x100UL)

Address after Translation:  I2C0: Translated Address (0x84900000) also attached the image for reference.

Please provide your input on this.

Thanks and regards

Ganesh Pawar

Hi Ganesh,

Please share the value of baseaddr variable which is used inside I2C_lld_isBaseAddrValid() API.

Regards,

Tushar

Hi Tushar,

baseaddr variable which is used inside I2C_lld_isBaseAddrValid() API is (0x4900000UL) and translated address is (0x84900000).

Regards

Ganesh

Hi Ganesh,

The baseAddr variable value should be equal to translated address. Looks like you have not done changes in the  ${MCU+SDK}/source/drivers/i2c/v0/i2c_v0.c file as mentioned in FAQ.

Regards,

Tushar

Hi Tushar,

The Changes as mentioned in the FAQ are done, with no exclusions and library is also built.

For Reference i am following "i2c_temperature_polling_lld_am64x-evm_r5fss0-0_nortos_ti-arm-clang" project i have integrated the i2c interface for my Cortex-M4 project.

Regards

Ganesh

Hi Ganesh,

Are you trying to access MCU_I2C from R5F core or are you trying to access it from MCU_M4F core?

Regards,

Tushar

Hi Tushar,

I am accessing the MCU_I2C from CORTEX-M4 core.

Thanks and regards

Ganesh Pawar

Hi Ganesh,

Please share your example.syscfg file with us.

Regards,

Tushar

Hi Tushar,

Sure attached the syscfg file

 syscfgConfiguration.zip

Thanks and regards

Ganesh Pawar

Hi Ganesh,

You have sent incorrect file. I am asking for example.syscfg file configured in the project.

Regards,

Tushar

Hi Tushar,

Pardon for sharing you the wrong file.

Here is the example.syscfg zip attached

.example_SysCfg.zip

Thanks and regards

Ganesh

Hi Ganesh,

Thanks for sharing the above sysconfig file. I did check the above and the configuration looks okay to me.

But I am concerned about why the baseAddr variable in the I2C_lld_isBaseAddrValid API is 0x4900000UL.

Can you please check after executing the below mentioned lines in i2c_v0.c file what is the value of i2cLldHandle->baseAddr variable? The variable should hold 0x84900000 value.

Regards,

Tushar

Hi Tushar,

Thanks for your Input.

Tushar Thakur said:

But I am concerned about why the baseAddr variable in the I2C_lld_isBaseAddrValid API is 0x4900000UL.

Can you please check after executing the below mentioned lines in i2c_v0.c file what is the value of i2cLldHandle->baseAddr variable? The variable should hold 0x84900000 value.

Could you please confirm whether the changes mentioned in the FAQ apply exclusively to the HLD (High-Level Driver) I2C API, or if they also extend support to the LLD (Low-Level Driver) I2C API?

Thanks and regards

Ganesh Pawar