MicroZed I2C for PMOD Trouble

I have successfully used I2C on a ZC706 but I find I'm really struggling to troubleshoot the I2C on the MicroZed.

The process seems like it should be simple. I created a block design that simply contains a Zynq and turns on the I2C 0 and assigns it to MIO 14 + 15 (pins 9 + 10 on J5).

I'm trying to access it from Linux, and when I run a command like i2cdetect, I don't even see the clock on the any of the J5 pins when using an oscilloscope. Also, if I enable the pullup on those lines, I still don't see any of the pins being pulled high.

Is anyone succesfully using and I2C PMOD on J5 and able to point me in the right direction?

Thanks

0 Former Member over 10 years ago

I was not updating the FSBL for the new design. With an updated FSBL everything was fine.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bkamen over 9 years ago in reply to Former Member

What did you do to do this?

I tried the "petalinux-config --get-hw-description=<path to my project.sdk>" and it doesn't seem to work. Or at least I'm not sure.

I've scoped the signals and while I have in my Vivado project the SCL/SDA lines config'd with PULLUPS, the voltages on the line are 0 and not Vdd.

Thanks,

-Ben
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 bkamen over 9 years ago in reply to bkamen

nevermind -- it seems the command previously listed wasn't doing something right to update the FSBL.

I saved out my changes to system-top.dts and then nuked the directory and re-created the project from scratch -- THEN it worked.

So something with the bootloader build scripts is messed up.

(this was with Petalinux 2014.2)

Yay -- more bugs.

-Ben
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel