Hi Andre, On Thu, Apr 10, 2008 at 4:37 AM, Andre Schwarz <[EMAIL PROTECTED]> wrote: > All, > > in my current system the I2C bus is not working properly on a MPC8343 in > u-boot v1.3.2. > > i2c board config includes : > > #define CONFIG_HARD_I2C > #undef CONFIG_SOFT_I2C > #define CONFIG_FSL_I2C > #define CONFIG_I2C_MULTI_BUS > #define CONFIG_I2C_CMD_TREE > #define CFG_I2C_OFFSET 0x3000 > #define CFG_I2C2_OFFSET 0x3100 > #define CFG_I2C_SPEED 100000 > #define CFG_I2C_SLAVE 0x7F > > > chip probing works fine. > > mvBL-M7> i2c probe > Valid chip addresses: 30 48 50 68 > > reading the Chips gives all "ff" > > mvBL-M7> i2c md 50 0 10 > 0000: ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ff ................ > > > Observing the I2C bus wires show that everything _works excellent_ : > 100kHz speed as well as all data seems ok - but u-boot shows "ff". >
The fact that probing works and your scope shows bits toggling leads me to believe that your command syntax is the problem. Please try something like: "i2c md 50.1 0 10". I2C syntax is a bit goofy - you often have to specify the bus width. I've used 1.3.2 successfully on an MPC8349 (same as yours) with and without Timur's speed patches. regards, Ben ------------------------------------------------------------------------- This SF.net email is sponsored by the 2008 JavaOne(SM) Conference Don't miss this year's exciting event. There's still time to save $100. Use priority code J8TL2D2. http://ad.doubleclick.net/clk;198757673;13503038;p?http://java.sun.com/javaone _______________________________________________ U-Boot-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/u-boot-users
