Forum Discussion
Hi sneha_wagh
Any update on this case?
Regards
Jingyang, Teh
- sneha_wagh3 years ago
New Contributor
Hi Jingyang,
Purpose of I2C Slave in our project is as below:
BMC Controller on Board will read the temperature, health status of FPGA via the I2C bus. BMC Controller requests the status via I2C Bus connected to I2C slave. I2C Slave then sends this request to Processor. Processor in turn gathers the relevant information and provides the status back to I2C Slave which in turn passes this information to BMC controller via I2C bus.
The I2C Slave with memory mapped master agent will not solve the purpose.
There is I2C Slave IP comes along with the processor which acts as a processor subsystem IP and it is present in SDM component. If we use the in-built SDM infrastructure of Intel FPGA, we will get our purpose solved. But in our project, we are using our own Processor and not the SDM structure. Thus we need I2C Slave IP component which is exactly same as the one gets enabled when we use in-built SDM architecture.
Thus I think, below infrastructure that you had suggested won't help here:
Avalon Agent >>> AXI Bridge Master --- AXI Bridge Slave >>> AXI Master Port
Also can you comment on mailbox-client IP integrated as a bridge between processor and SDM [SDM: Secure Device Manager is used to access Flash] ?
In case of more understanding, we can have a call.
Regards
Sneha