DesignSomething.org
Leopardboard - Home
Join
Sign in
Search
Search Options
Search Everything
Search Leopardboard
Overview
Forums
Videos
Projects
How to Buy
Support
i2c read problem
Tags
1.3
1.5
355 Leopard Board Kernel SD telnet upload
5MP
Aptina Camera
Bayer array
board
bootloader
buffer
callback
camera module
camera quality 1080p dual output
Capture
CMEM
DM355
DM355 Leopard board dvsdk version?
dm355 nand
dm355 ramdisk kernel panic
dm355 ridgerun bootloader
dm365
DM365ECDK+USB MOUSE
erase
fakesink
getting started
GPIO
Details
0
Replies
1
Subscriber
Posted
over 3 years ago
Options
Share this
Home
»
Leopardboard
»
Leopardboard 355
»
i2c read problem
i2c read problem
This question is not answered
Posted by
Gonzha Dmitriy
on
27 Dec 2010 2:00 PM
Hello About two weeks I have problem accessing to i2c bus on leopard dm355 at kernels other than 2.6.10_mvl401_IPNC-1.1.0 (i have tried new kernels 2.6.32r2-davinci1, 2.6.37.rc6, 2.6.29 and others): at new kernels i can't read on i2c anything but on 0x18 address (using i2cdetect, i2cdump and from kernel modules). But I need to have access to device on 0x48 (MT9P031 camera). I tried to use another uboot versions (U-Boot 2009.11), and tried to access i2c from uboot commands (i2c probe, i2c md), but i have same result, as in new kernels: "Valid chip addresses: 18" and errors accessing to 0x48. In 2.6.10 kernel i2c works only with old uboot 1.2.0, with new u-boot I have same result I even tried to modify memory at PINMUX (0x01C40000), GPIO (0x01C67000) and I2C (0x01c21000) base addresses, to make it same as in working 2.6.10, made 2.6.10 i2c driver up-port to 2.6.32r2, but I haven't got any result.
leopard
camera module
DM355
5MP
i2c
You have posted to a forum that requires a moderator to approve posts before they are publicly available.