Re: [beagleboard] Change I2C bus for video communication

2014-11-21 Thread Robert Nelson
On Fri, Nov 21, 2014 at 2:14 AM, bremenpl wrote: > Hello there, > I have created a shield for BeagleBone Black on which I have a HDMI output > connected to a dataframer, which goes to the LCD pins of the BeagleBone > Black. Ive tried to copy the functionality of an onboard video circuit. For > th

Re: [beagleboard] Change I2C bus for video communication

2014-11-21 Thread Bremenpl
I am not very good at tree overlays, but from the one you have provided me i believe i would be abble to reduce it only to modify the LCD pins (I also need to disable mcasp, because I only use video and the pins for mcasp are used as other peripherals). I thing I tried to find the place in this

Re: [beagleboard] Change I2C bus for video communication

2014-11-21 Thread Robert Nelson
On Fri, Nov 21, 2014 at 10:04 AM, Bremenpl wrote: > I am not very good at tree overlays, but from the one you have provided me i > believe i would be abble to reduce it only to modify the LCD pins (I also > need to disable mcasp, because I only use video and the pins for mcasp are > used as other

Re: [beagleboard] Change I2C bus for video communication

2014-11-21 Thread Bremenpl
Thank you, i will try to use this overlay. You are probably in US, thats a pitty for me because there is a big time difference which brings longer help delay :P. W dniu 2014-11-21 o 17:06, Robert Nelson pisze: On Fri, Nov 21, 2014 at 10:04 AM, Bremenpl wrote: I am not very good at tree overl

Re: [beagleboard] Change I2C bus for video communication

2014-11-23 Thread Bremenpl
Hello again, I am just trying to export the compiled .dtbo file but I have to unexport the residing hdmi overlay. When I do that with echo i get kernel panic and my ssh session is lost. I would like to comment out the export at boot but I dont know where to find the place I should do it in con

Re: [beagleboard] Change I2C bus for video communication

2014-11-23 Thread Bremenpl
I have found the uEnv.txt file in boot directory but for a long time now I cannot find where are the .dtbo files stored in console image of debian. I am putting my .dtbo file in /lib/firmware but when trying to echo its name to slots it doesnt want to pick it up from there. W dniu 2014-11-21 o

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Bremenpl
Okay, I have managed to load the tree overlay by hand from /lib/firmware/. What was wrong was that I havent followed the naming style. I have changed the name of .dtbo file to BB-BONELT-HDMIN1-00A0.dtbo and I could load the tree overlay by hand. Although, the overlay didnt want to load automati

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Jason Lange
> > I am not sure if I turned off the standard HDMI overlay, I just commented > the enables lines in uEnv.txt, now my slots file looks like this: > > root@beaglebone:/sys/devices/bone_capemgr.9# cat slots > 0: 54:PF--- > 1: 55:PF--- > 2: 56:PF--- > 3: 57:PF--- > 4: ff:P-O-L Bone-LT-eMMC-2G,00A

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Jason Lange
If you want to load a custom cape at boot you need to follow these instructions: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#Loading_custom_capes On Mon, Nov 24, 2014 at 1:46 AM, Jason Lange wrote: > > >> I am not sure if I turned off the standard HDMI overlay, I just commented >> the

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Bremenpl
In that case after the disabling I have enabled my module by hand (BB-BONELT-HDMIN1): root@beaglebone:~# cat /sys/devices/bone_capemgr.9/slots 0: 54:PF--- 1: 55:PF--- 2: 56:PF--- 3: 57:PF--- 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G 5: ff:P-O-- Bone-Black-HDMI,00A0,

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Jason Lange
On Mon, Nov 24, 2014 at 1:52 AM, Bremenpl wrote: > In that case after the disabling I have enabled my module by hand > (BB-BONELT-HDMIN1): > > root@beaglebone:~# cat /sys/devices/bone_capemgr.9/slots > 0: 54:PF--- > 1: 55:PF--- > 2: 56:PF--- > 3: 57:PF--- > 4: ff:P-O-L Bone-LT-eMMC-2G,00A0,

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Bremenpl
Thanks for help with the boot loading of tree overlay, it works. But monitor still doesnt display anything :/. At least I know its not because of loading after boot. W dniu 2014-11-24 o 10:56, Jason Lange pisze: On Mon, Nov 24, 2014 at 1:52 AM, Bremenpl > wrote:

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Bremenpl
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

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread bremenpl
I wonder, Maybe there has to be more software changed than only tree overlay for i2c? I am using the chip that BeagleboneMx used. It doesnt use hotplug and CEC for example... -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to t

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Robert Nelson
On Mon, Nov 24, 2014 at 5:28 AM, Bremenpl 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 -

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Bremenpl
Do I have to place this part: dvicape { compatible = "ti,tilcdc,tfp410"; i2c = <&i2c2>; pinctrl-names = "default"; pinctrl-0 = <&bone_dvi_cape_dvi_00A1_pins>; powerdn-gpio = <&gpio2 31 0>; }; In the overlay file you have provided me erlier instead of HDMI part? Or do I have

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Robert Nelson
On Mon, Nov 24, 2014 at 2:13 PM, Bremenpl wrote: > Do I have to place this part: > > dvicape { > compatible = "ti,tilcdc,tfp410"; > i2c = <&i2c2>; > pinctrl-names = "default"; > pinctrl-0 = <&bone_dvi_cape_dvi_00A1_pins>; > powerdn-gpio = <&gpio2 31 0>; > }; > > In the overlay

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Bremenpl
This is the output on debug serial now: . . .Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.338981] omap2_mbox_probe: platform not supported [0.493971] tps65217-bl tps65217-bl: no platform data provided [0.558187] bone-capemgr bone_capemgr.9: slot #0: No cape

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Robert Nelson
On Mon, Nov 24, 2014 at 2:34 PM, Bremenpl wrote: > This is the output on debug serial now: > > . > . > .Starting kernel ... > > Uncompressing Linux... done, booting the kernel. > [0.338981] omap2_mbox_probe: platform not supported > [0.493971] tps65217-bl tps65217-bl: no platform data prov

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Bremenpl
I know those sheets. Even thought it says that pinumux is I2C2, in the software for i2ctools i reffer to nr 1 not nr 2. Thats why I am confused. W dniu 2014-11-24 o 21:36, Robert Nelson pisze: On Mon, Nov 24, 2014 at 2:34 PM, Bremenpl wrote: This is the output on debug serial now: . . .Start

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread Bremenpl
is the tilcdc part correct? W dniu 2014-11-24 o 21:36, Robert Nelson pisze: On Mon, Nov 24, 2014 at 2:34 PM, Bremenpl wrote: This is the output on debug serial now: . . .Starting kernel ... Uncompressing Linux... done, booting the kernel. [0.338981] omap2_mbox_probe: platform not support

Re: [beagleboard] Change I2C bus for video communication

2014-11-24 Thread bremenpl
This is my current overlay file: http://pastie.org/private/j91tplpqnhymvvig1pc0rw Can you please tell me either there is still anything wrong? I Still cant get the video to work :( W dniu poniedziałek, 24 listopada 2014 21:36:51 UTC+1 użytkownik RobertCNelson napisał: > > On Mon, Nov 24, 2014 a