I2C Not Ack'ing with NXPs K64F

[Harriet1168]

Hi guys really hoping you can help me here, I am creating another model for an already existing product, which uses an old coldfire microprocessor. the new micro is a K64F micro from NXP, I originally had everything working on NXP's freedom development board and have created a PCB to connect to the back plain of the control unit.

My I2C comms isn't acking properly and isn't receiving data, I have set everything up the same as the development board, apart from I have swapped over to using I2C0 rather than I2C1 and am using the internal clock of the micro using FLL to get a bus frequency around 11MHz.

The Coldfire is meant to send 8 bytes worth of data on a successful acknowledgment, but my K64F micro doesn't ack at all.

I have Ensured

- The pull-ups are soldered correctly and are the right resistance values

- The Clock frequency is correct through software pinging shown in figure 6

- No data corruption through the back plain, shown by using a logic analyzer in figure 3

- Configured correctly in MCUexpresso and removed RMII routing peryourhealth

The Coldfire code had libraries made by the company years ago, I know they work since they worked with the dev board originally. The coldifre is the master and will wait 200ms before timing out.

If you need anything else let me know, I can't give the entire PCB circuit or give much more code, since this is a project for work.

[LutherMoon]

With SPI and asynchronous serial, this is not much of a concern because the high  NXP's PCF8563 RTC chip has a read and write address, both of which conflict  Are all parties ACK ing and NACK ing when they should?