I meant to say master.ini. If you downloaded the test project from the link above from my website, there is a file called "master.ini" that is preprocessed in the debug tab of the options for the target in Keil.

When I was reviewing the asm version of the I2C to see how it worked, the I2C simulator was working using that assembly code. When I read part of a website, it explained that the master.ini is creating a psuedo slave device with a fixed address that commands could be sent to, to see if the data from the master is being received, acknowledged, and responding correctly.

Then you mention using an eeprom, I assumed you were talking about a way to simulate the eeprom the same way. Right now I have no hardware to test any of this, only the I2C simulation plugin to see if my code is configured properly to send I2C commands from the Master MPU to the Slave MPU.

The boards will be here in a couple of days and that is what this is for, so I'm trying to get ahead of the game now instead of later. If the simulation works like the asm does, then I should have less troubleshooting and debugging to do in a couple of days.

Sorry for the confusion, I hope this makes my last post more understandable.