On Mon, Nov 24, 2014 at 5:28 AM, Bremenpl <breme...@gmail.com> wrote:
> Some update on the progress:
> I figured out that I have switched SDA and SCL lines for the monitor
> connection through HDMI. I have flipped that to proper position and I can
> see additional devices on the bus:
>
> root@beaglebone:~# i2cdetect -y -r 1
>      0  1  2  3  4  5  6  7  8  9  a  b  c  d  e  f
> 00:          -- -- -- -- -- -- -- -- -- -- -- -- --
> 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 20: 20 -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
> 30: 30 -- -- -- -- -- -- 37 -- -- 3a -- -- -- -- --
> 40: -- -- -- -- -- -- -- -- -- -- 4a 4b -- -- -- --
> 50: 50 -- -- -- UU UU UU UU -- -- -- -- -- -- -- --
> 60: -- 61 -- -- -- -- -- -- 68 -- -- -- -- -- -- --
> 70: -- -- -- -- -- -- -- --
> root@beaglebone:~#
>
> 0x20 - I/O expander
> 0x61 - external DAC
> 0x68 - RTC clock
>
> 0x20, 0x37, 0x3a, 0x4a, 0x4b and 0x50 appear after I connect the monitor ro
> hdmi connector.
>
> I think I have figured out that I have to put i2c = <&i2c2>; in the overlay
> file, as I think it reffers to the hardware number.
>
> Now when I boot BeagleBone Black in the debug console I see:
>
> .
> .
> .
> Starting kernel ...
>
> Uncompressing Linux... done, booting the kernel.
> [    0.338954] omap2_mbox_probe: platform not supported
> [    0.493953] tps65217-bl tps65217-bl: no platform data provided
> [    0.558115] bone-capemgr bone_capemgr.9: slot #0: No cape found
> [    0.595223] bone-capemgr bone_capemgr.9: slot #1: No cape found
> [    0.632332] bone-capemgr bone_capemgr.9: slot #2: No cape found
> [    0.662506] bone-capemgr bone_capemgr.9: bone: Invalid signature
> '825a93cf' at slot 3
> [    0.670687] bone-capemgr bone_capemgr.9: slot #3: No cape found
> [    0.689417] omap_hsmmc mmc.5: of_parse_phandle_with_args of 'reset'
> failed
> [    0.751741] pinctrl-single 44e10800.pinmux: pin 44e10854 already
> requested by 44e10800.pinmux; cannot claim for gpio-leds.8
> [    0.763488] pinctrl-single 44e10800.pinmux: pin-21 (gpio-leds.8) status
> -22
> [    0.770796] pinctrl-single 44e10800.pinmux: could not request pin 21 on
> device pinctrl-single
> Loading, please wait...
> systemd-fsck[210]: rootfs: clean, 21580/111104 files, 121672/444160 blocks
> systemd-fsck[326]: dosfsck 3.0.13, 30 Jun 2012, FAT32, LFN
> systemd-fsck[326]: /dev/mmcblk0p1: 138 files, 31622/49047 clusters
> [    6.224809] libphy: PHY 4a101000.mdio:01 not found
> [    6.229881] net eth0: phy 4a101000.mdio:01 not found on slave 1
> [   10.703450] dummy 1-0034: Error -121 writing to cec:0xff
> [   10.740063] tda998x 1-0070: Error -121 reading from 0xa
> [   10.781054] tda998x 1-0070: Error -121 writing to 0xa
> [   10.837748] tda998x 1-0070: Error -121 reading from 0xa
> [   10.861162] tda998x 1-0070: Error -121 writing to 0xa
> [   10.917824] tda998x 1-0070: Error -121 reading from 0x1
> [   10.941245] tda998x 1-0070: Error -121 writing to 0x1
> [   10.972464] tda998x 1-0070: Error -121 reading from 0x1
> [   11.003772] tda998x 1-0070: Error -121 writing to 0x1
> [   11.029803] tda998x 1-0070: Error -121 writing to REG_CURPAGE
> [   11.065182] tda998x 1-0070: Error -121 writing to 0x200
> [   11.095575] tda998x 1-0070: Error -121 writing to 0x201
> [   11.128734] tda998x 1-0070: Error -121 writing to 0x202
> [   11.165874] tda998x 1-0070: Error -121 writing to 0x203
> [   11.189995] tda998x 1-0070: Error -121 writing to 0x204
> [   11.217379] tda998x 1-0070: Error -121 writing to 0x205
> [   11.230326] tda998x 1-0070: Error -121 writing to 0x20e
> [   11.242030] tda998x 1-0070: Error -121 writing to 0x211
> [   11.253725] tda998x 1-0070: Error -121 writing to 0x207
> [   11.260694] tda998x 1-0070: Error -121 writing to 0x208
> [   11.271538] tda998x 1-0070: Error -121 writing to 0x209
> [   11.284844] tda998x 1-0070: Error -121 writing to 0x20a
> [   11.294595] tda998x 1-0070: Error -121 writing to 0x206
> [   11.305084] tda998x 1-0070: Error -121 writing to REG_CURPAGE
> [   11.313653] tda998x 1-0070: Error -121 reading from 0x0
> [   11.319751] tda998x 1-0070: Error -121 reading from 0x2

why are you still pointing to the "tda998x" driver?

https://github.com/beagleboard/linux/blob/3.8/Documentation/devicetree/bindings/drm/tilcdc/tfp410.txt#L16

Regards,

-- 
Robert Nelson
http://www.rcn-ee.com/

-- 
For more options, visit http://beagleboard.org/discuss
--- 
You received this message because you are subscribed to the Google Groups 
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to