[How-to] BB-View on latest Debian

Hello everybody,

and thank you Louis for this good tutorial.

I have two problems with my BB-view:

1) When I try to fix the color swap, I don't find the name of the screen in /var/log/Xorg.0.log

Did you know an other way to find this name?

2)When I try to calibrate the touchscreen, the TSLIB calibration utility (ts_calibrate) freezes. The screen displays "touch crosshair to calibrate", but I cant interact with (and no Ctrl-C  available)

There is someone here who solved this problem?

To build my OS I use this tutorial:

http://eewiki.net/display/linuxonarm/BeagleBone+Black

with the debian FS.

Regards,

arthur

Arthur,

Which kernel version are you using ?

Did you apply the patch Louis posted ?

Is the touch-screen driver loaded and did you set TSLIB_TSDEVICE to the appropriate device ?

If kernel 3.8.x check that the BB-VIEW-LCD7-01 overlay has been loaded.

If kernel 3.13 then you'll need to patch the touch screen into the main devicetree file as 3.13 doesn't have the capemanager and so can't load overlays.

You can ssh into the BBB and kill the ts_calibrate task to get local control back.

Hello selsinork,

"Which kernel version are you using ?"

I use the 3.8.

"Did you apply the patch Louis posted ?"

I rebuild the kernel with Louis' edits in the "4. Re:[How-to] BB-View on latest Debian" message, but it only inverts the axes, not the colors.

"Is the touch-screen driver loaded and did you set TSLIB_TSDEVICE to the appropriate device ?"

Yes

I used "cat /dev/input/eventX | hexdump" to find the good one.

"If kernel 3.8.x check that the BB-VIEW-LCD7-01 overlay has been loaded."

I'm new in the embedded world, and I'm not used to overlays.

What do you mean by "load" it?

"You can ssh into the BBB and kill the ts_calibrate task to get local control back."

Thanks for the tips.

Regards,

arthur calimet wrote:

"If kernel 3.8.x check that the BB-VIEW-LCD7-01 overlay has been loaded."

I'm new in the embedded world, and I'm not used to overlays.

What do you mean by "load" it?

Louis covered it back in his first post here:

We need to do one more thing before the LCD will work. Since the cape doesn't have an EEPROM, we need to black-list the HDMI drivers and force-load the BB-VIEW drivers in the boot command file:

    bbb>  sudo  nano  /boot/uboot/uEnv.txt

Find the "optargs" line and edit it to be:

    optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN  capemgr.enable_partno=BB-VIEW-LCD7-01

Notice that the preceding "#" has been removed. You don't want to disable BB-BONE-EMMC-2G, or you won't be able to boot from eMMC.

Now save and exit by doing CTRL-O, Enter, CTRL-X.

Alternatively you can look at which overlays are loaded and add/remove your own like this

cat /sys/devices/bone_capemgr.8/slots

(the 8 may be a 9 or some other number depending on kernel version and driver load order)

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-L Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI

0 to 3 are reserved for capes that capemgr can detect on it's own - it can't detect the BB-View as it doesn't have the required EEPROM

4 is a virtual cape for the on-board eMMC

5 is another virtual cape for the on-board HDMI

So you do something like this:

echo BB-VIEW-LCD7-01 > /sys/devices/bone_capemgr.8/slots

cat  /sys/devices/bone_capemgr.8/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-L Override Board Name,00A0,Override Manuf,BB-VIEW

the BB-VIEW-LCD7-01 in the echo line needs to be the filename of the overlay that you see in /lib/firmware after you strip off the version and extension from the end of the filename. So if you look in /lib/firmware and see BB-VIEW-LCD7-01-00A0.dtbo then you'd use the echo line above.

Note that the HDMI and LCD will conflict as they use the same set of pins, so you need the capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN piece in the optargs line of uEnv.txt (and a reboot to activate it) as Louis described before the BB-View overlay will load.

Sorry I can't help much with the colour swap problem as I'm not using Xorg and as you probably saw earlier in the discussion the plain framebuffer doesn't appear to have the problem.

Hello selsinork,

and thank you for the explanations.

The "optargs" line in the uEnv.txt file is the good one:

optargs=capemgr.disable_partno=BB-BONELT-HDMI,BB-BONELT-HDMIN  capemgr.enable_partno=BB-VIEW-LCD7-01

And the overlay seems to be loaded:

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,Texas Instrument,BB-BONELT-HDMI

6: ff:P-O-- Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN

7: ff:P-O-L Override Board Name,00A0,Override Manuf,BB-VIEW-LCD7-01

(the BB-VIEW-LCD7-01-00a0.dtb file is in /lib/firmware)

I probably have another problem.

Regards,

Ok, so with the overlay loaded then the touch screen driver should be able to work.

You can check the proper device using 'evtest' like this:

root@lcd:~/evtest# ./evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      ti-tsc
/dev/input/event1:      bb_view_gpio_keys.8
/dev/input/event2:      HID 04d9:1400
/dev/input/event3:      HID 04d9:1400
Select the device event number [0-3]: ^C
root@lcd:~/evtest#

The one you're looking for is the ti-tsc one.  You can get evtest from here http://cgit.freedesktop.org/evtest/

Or, alternatively if you do

root@lcd:~/evtest# cat /proc/bus/input/devices
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="ti-tsc"
P: Phys=
S: Sysfs=/devices/ocp.3/44e0d000.tscadc/TI-am335x-tsc/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=1000003

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="bb_view_gpio_keys.8"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/bb_view_gpio_keys.8/input/input1
U: Uniq=
H: Handlers=event1 
B: PROP=0
B: EV=3
B: KEY=f 0 0 0 0 0 0 0 0

you can get similar information..

Finally, if you've built the touchscreen driver as a loadable module make sure it's installed in the correct place under /lib/modules, that you've run depmod -a or equivalent and have actually loaded the one with Louis changes and not a stale version.

Ok, so with the overlay loaded then the touch screen driver should be able to work.

You can check the proper device using 'evtest' like this:

root@lcd:~/evtest# ./evtest
No device specified, trying to scan all of /dev/input/event*
Available devices:
/dev/input/event0:      ti-tsc
/dev/input/event1:      bb_view_gpio_keys.8
/dev/input/event2:      HID 04d9:1400
/dev/input/event3:      HID 04d9:1400
Select the device event number [0-3]: ^C
root@lcd:~/evtest#

The one you're looking for is the ti-tsc one.  You can get evtest from here http://cgit.freedesktop.org/evtest/

Or, alternatively if you do

root@lcd:~/evtest# cat /proc/bus/input/devices
I: Bus=0000 Vendor=0000 Product=0000 Version=0000
N: Name="ti-tsc"
P: Phys=
S: Sysfs=/devices/ocp.3/44e0d000.tscadc/TI-am335x-tsc/input/input0
U: Uniq=
H: Handlers=event0 
B: PROP=0
B: EV=b
B: KEY=400 0 0 0 0 0 0 0 0 0 0
B: ABS=1000003

I: Bus=0019 Vendor=0001 Product=0001 Version=0100
N: Name="bb_view_gpio_keys.8"
P: Phys=gpio-keys/input0
S: Sysfs=/devices/bb_view_gpio_keys.8/input/input1
U: Uniq=
H: Handlers=event1 
B: PROP=0
B: EV=3
B: KEY=f 0 0 0 0 0 0 0 0

you can get similar information..

Finally, if you've built the touchscreen driver as a loadable module make sure it's installed in the correct place under /lib/modules, that you've run depmod -a or equivalent and have actually loaded the one with Louis changes and not a stale version.

Hello selsinork,

and thank you for spending time helping me.

i export TSLIB_TSDEVICE=/dev/input/event1 (it is the ti-tsc one)

I think the module with Louis changes is loaded, because the axes are inverted.

But I don't understand how the axes inversion can fix the color swap, or the ts_calibrate freeze.

Did I miss something? or we are not speaking about the same patch...

Same patch.  The problem I found was that without the patch it was difficult/impossible to complete calibration. ts_calibrate seems to have no 'quit' option, so being unable to do what ts_calibrate asks looks very much like it's frozen when in reality it's just waiting for you to do something that you're not able to do.

As I said, the colour swap problem seems limited to Xorg and seems fixable with the options Louis described. I'm not using Xorg, so I don't see the problem and can't really help much further with that.

Hello,

Ultimately, I used xinput-calibrator, with no problem.

But I always have the color problem.

I am seeking for an other way to change color depth, or an other way to find the screen name.

Any idea?

You might try looking in /var/log/Xorg.0.log you'll often see something like this (amongst lots of other info)

[    37.033] (==) Using system config directory "/usr/share/X11/xorg.conf.d"
[    37.354] (==) ServerLayout "Simple Layout"
[    37.354] (**) |-->Screen "Screen0" (0)
[    37.354] (**) |   |-->Monitor "Monitor0"
[    37.354] (**) |   |-->Device "Device0"
[    37.354] (**) |-->Input Device "touchpad"
[    37.354] (**) |-->Input Device "Mouse1"
[    37.354] (**) |-->Input Device "Keyboard1"
[    37.354] (**) Option "Xinerama" "0"

which may give you some clues about what names the xserver thinks it's using.

arthur calimet wrote:

 

Ultimately, I used xinput-calibrator, with no problem.

Just a thought...

Were you trying to use ts_calibrate while X was running ?  That's very unlikely to work, ts_calibrate should only be ran from a framebuffer console, i.e. without X running.

I already look this file:

[   287.457] (==) Using system config directory "/usr/share/X11/xorg.conf.d"

[   287.458] (==) No Layout section.  Using the first Screen section.

[   287.459] (==) No screen section available. Using defaults.

[   287.459] (**) |-->Screen "Default Screen Section" (0)

[   287.459] (**) |   |-->Monitor "<default monitor>"

[   287.460] (==) No monitor specified for screen "Default Screen Section".

Using a default monitor configuration.

[   287.460] (==) Automatically adding devices

[   287.460] (==) Automatically enabling devices

and indeed, there is only "input class" section in /usr/share/X11/xorg.conf.d/10-evdev.conf

I tried to create a screen section using some Identifiers like "Default Screen Section", "Screen0", etc...

"Just a thought..."

I did this mistake when i post my first message

but I still have the freeze after stoping X.