I2C - docs are misleading.

[duaneellissd]

This is issue #1 of 2

The documentation on this site imply or suggests that the I2C interface is identical to the standalone APB_I2C module.

For example the documentation states and uses the term COREI2C - which would imply that it is the same as the COREI2C microsemi offers here:

https://www.microsemi.com/document-portal/doc_view/1245253-corei2c-hb

But the MIV_ESS module is very different.

https://github.com/Mi-V-Soft-RISC-V/miv-rv32-documentation/blob/main/soft-ip-driver-user-guides/CoreI2C/corei2c-driver-user-guide.md

In fact it is not the same it is very different.
Example the CONTROL register is at offset 0 in the CoreI2C PDF Guide.

Where as the CTRL register in the MIV core is a address 2 (my assumption is that translates to address 8)

I think the fix here is to NOT use the TERM CoreI2C in any of the documentation associated with this.

[CLappin]

Hi @duaneellissd ,

Apologies for the confusion.
The MIV_ESS does not use the CoreI2C module. It uses an open source module from Richard Herveille. Chapter 7 of the MIV_ESS User Guide for more information on this. The firmware related to the MIV_ESS I2C module is available here

If you would like to use the CoreI2C module with the MIV_ESS, you could enable one of the APB interfaces to the fabric and attach the CoreI2C module.