After Upgrade Kernel from 3.8.13 -> 4.9, i2c1 can not find slave device

[Shimon Filtzer]

After Upgrade Kernel from 3.8.13 -> 4.9, and i2c1 overlay configuration in uEnv.txt,

I tried to find slave i2c device without success.

In /dev, i2c-1 exists. When I check pin-config, I see correct pin configuration.

Execution i2cdetect, can not find anything.

When I run on same BBB card, kernel 3.8.13(from SD slot) i2c slave found and work without problem.

I have no idea, about solving the problem.. 

Please, help.

[Robert Nelson]

The i2c bus number changed in the 3.8.x -> 4.1.x+..

Double check your overlay, and double check what port you are using in
userapce..

Regards,

--
Robert Nelson
https://rcn-ee.com/

[Shimon Filtzer]

uboot_overlay_addr4=/lib/firmware/BB-I2C1-00A0.dtbo

i2c1

P9-19

P9-20

[Robert Nelson]

On Thu, Jan 18, 2018 at 11:37 AM, Shimon Filtzer <simo...@gmail.com> wrote:
> uboot_overlay_addr4=/lib/firmware/BB-I2C1-00A0.dtbo
> i2c1
> P9-19
> P9-20

Yeah, no...

BB-I2C1-00A0 = P9.18/P9.17:

https://github.com/beagleboard/bb.org-overlays/blob/master/src/arm/BB-I2C1-00A0.dts#L36-L37

[Shimon Filtzer]

Ok, 

On P9-19/P9-20, i2c2?

I, tried i2cdetect -r 2, and my slave doesn't exist.

May be I need some additional overlay/definition?

[Robert Nelson]

On Thu, Jan 18, 2018 at 11:52 AM, Shimon Filtzer <simo...@gmail.com> wrote:
> Ok,
> On P9-19/P9-20, i2c2?
> I, tried i2cdetect -r 2, and my slave doesn't exist.
> May be I need some additional overlay/definition?

Did you load it?

uboot_overlay_addr4=/lib/firmware/BB-I2C2-00A0.dtbo

ps, double check with:

sudo /opt/scripts/tools/version.sh

[Shimon Filtzer]

git:/opt/scripts/:[2ce750d881941c5189db9e189af90517e11c079f]

eeprom:[A335BNLT00C02017BBBK1432]

dogtag:[BeagleBoard.org Debian Image 2017-08-31]

bootloader:[eMMC-(default)]:[/dev/mmcblk1]:[U-Boot 2017.09-rc2-00002-g7c9353]

kernel:[4.9.45-ti-r57]

nodejs:[v6.11.2]

uboot_overlay_options:[enable_uboot_overlays=1]

uboot_overlay_options:[uboot_overlay_addr4=/lib/firmware/BB-I2C2-00A0.dtbo]

uboot_overlay_options:[uboot_overlay_addr5=/lib/firmware/BB-UART1-00A0.dtbo]

uboot_overlay_options:[uboot_overlay_addr6=/lib/firmware/BB-UART2-00A0.dtbo]

uboot_overlay_options:[uboot_overlay_addr7=/lib/firmware/BB-UART4-00A0.dtbo]

uboot_overlay_options:[enable_uboot_cape_universal=1]

pkg:[bb-cape-overlays]:[4.4.20170728.0-0rcnee1~stretch+20170728]

pkg:[bb-wl18xx-firmware]:[1.20170829-0rcnee1~stretch+20170829]

pkg:[firmware-ti-connectivity]:[20170823-1rcnee0~stretch+20170830]

[Shimon Filtzer]

Yes, it's correct.

I tried overlay_addr4=/lib/firmware/BB-I2C2-00A0.dtbo 

and overlay_addr0=/lib/firmware/BB-I2C2-00A0.dtbo 

May be exists some additional way?

Regards

четверг, 18 января 2018 г., 19:59:17 UTC+2 пользователь RobertCNelson написал:

[Shimon Filtzer]

I checked twice...

--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to a topic in the Google Groups "BeagleBoard" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/beagleboard/3gtyXxdBxfc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to beagleboard+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/beagleboard/a831f671-1509-4cc7-8b34-62270cdcc910%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.