BBB and LCD7 under Ubuntu in my own applications: is it practical?

I finally got BBB and LCD7 running with the radiumboard HD Camera Cape, using the Angstrom image on the camera CDROM, BB-BONE-CAM-VVDN_CR4.img

Also I read the LCD7 reference manual and looked here http://elinux.org/CircuitCo:BeagleBone_LCD7

radium boards provides a source folder on CDROM but it is an entire Linux 3.8.13 kernel with no documents… I just would like the camera support files.

The Angstrom image and the Cheese camera app (why is it called Cheese? “say cheese” before you take a photo?) has several bugs: trying to take a video locks up Cheese.

I can’t run the screen calibration again. It starts to load then nothing.

The touchscreen (used with stylus) is so jittery it’s almost useless.

If I try to set the time with the clock widget it crashes.

Is there any support for using the camera in Ubuntu or in any way other than with Cheese? Not that I can find unless I want to write all my own support from scratch. Section 2.9 of the camera reference manual has this:
Software/Hardware Interface/Ports Software Interface: SW interface is via Linux-V4L2 layer. Cape board driver is compactable to V4l2

That’s it. One sentence. Nothing else about a provided driver or how to use the camera with my own application. Nothing about even where to start with some sample camera driver code. I am trying to contact radiumboards about this: there is no support forum at their web site.

LCD7 appears also to have only support on Angstrom?

If I try to run Ubuntu (from eMMC, instead of the uSD card needed for Angstrom with LCD7 and camera) now all I get is errors in the serial monitor:
U-Boot SPL 2015.07-rc3-00001-g2c9c20a (Jun 30 2015 - 09:02:07) spl_register_fat_device: fat register err - -1 spl_register_fat_device: fat register err - -1 spl_load_image_fat: error reading image u-boot.img, err - -1 spl: ext4fs_open failed spl: ext4fs_open failed spl_load_image_ext: error reading image uImage, err - -1 spl: ext4fs_open failed spl_load_image_ext: error reading image u-boot.img, err - -1 spl: mmc: no boot mode left to try ### ERROR ### Please RESET the board ###

resetting the board just gets the same thing. So booting from the uSD has apparently killed the Ubuntu eMMC image, or at least some of its files?

I’m googling around and found this: https://groups.google.com/forum/#!topic/beagleboard/xyT84cDwEsQ where the author spent 10 hours figuring out how to get LCD7 to work with Ubuntu. I’ll try this next. There seems not to be any LCD7-specific support channel.

My hope was to be able to use LCD7 as a local screen and write a simple GUI with some custom buttons to start and stop some attached equipment, read I2C sensors, etc. I don’t want a whole desktop GUI and the overhead of that. I was hoping to write a Python app to build some screens (I think there are some python UI toolkits out there) and expecting the LCD7 and camera would have something like a driver template which I could use as a starting point. But so far I don’t see anything like that.

Am I looking in the wrong place? Wishing for something not there? Are LCD7 and the HD camera cape meant to be just demo items not intended for use in my own applications? Should I be asking these questions elsewhere?

Thanks in advance for anything helpful,

Bruce

I finally got BBB and LCD7 running with the radiumboard HD Camera Cape,
using the Angstrom image on the camera CDROM, BB-BONE-CAM-VVDN_CR4.img

Also I read the LCD7 reference manual and looked here
http://elinux.org/CircuitCo:BeagleBone_LCD7

radium boards provides a source folder on CDROM but it is an entire Linux
3.8.13 kernel with no documents... I just would like the camera support
files.

The Angstrom image and the Cheese camera app (why is it called Cheese? "say
cheese" before you take a photo?) has several bugs: trying to take a video
locks up Cheese.

It's been called Cheese since 2007 GSOC:
https://wiki.gnome.org/Apps/Cheese

I can't run the screen calibration again. It starts to load then nothing.

The touchscreen (used with stylus) is so jittery it's almost useless.

If I try to set the time with the clock widget it crashes.

Is there any support for using the camera in Ubuntu or in any way other than
with Cheese? Not that I can find unless I want to write all my own support
from scratch. Section 2.9 of the camera reference manual has this:
Software/Hardware Interface/Ports Software Interface: SW interface is via
Linux-V4L2 layer. Cape board driver is compactable to V4l2
That's it. One sentence. Nothing else about a provided driver or how to use
the camera with my own application. Nothing about even where to start with
some sample camera driver code. I am trying to contact radiumboards about
this: there is no support forum at their web site.

LCD7 appears also to have only support on Angstrom?

Exactly which lcd is this?

dmesg | grep cape

If I try to run Ubuntu (from eMMC, instead of the uSD card needed for
Angstrom with LCD7 and camera) now all I get is errors in the serial
monitor:
U-Boot SPL 2015.07-rc3-00001-g2c9c20a (Jun 30 2015 - 09:02:07)
spl_register_fat_device: fat register err - -1 spl_register_fat_device: fat
register err - -1 spl_load_image_fat: error reading image u-boot.img, err -
-1 spl: ext4fs_open failed spl: ext4fs_open failed spl_load_image_ext: error
reading image uImage, err - -1 spl: ext4fs_open failed spl_load_image_ext:
error reading image u-boot.img, err - -1 spl: mmc: no boot mode left to try
### ERROR ### Please RESET the board ###

Early lcd7's shared a few lines on the eMMC....

resetting the board just gets the same thing. So booting from the uSD has
apparently killed the Ubuntu eMMC image, or at least some of its files?

I'm googling around and found this:
Redirecting to Google Groups where the
author spent 10 hours figuring out how to get LCD7 to work with Ubuntu. I'll
try this next. There seems not to be any LCD7-specific support channel.

My hope was to be able to use LCD7 as a local screen and write a simple GUI
with some custom buttons to start and stop some attached equipment, read I2C
sensors, etc. I don't want a whole desktop GUI and the overhead of that. I
was hoping to write a Python app to build some screens (I think there are
some python UI toolkits out there) and expecting the LCD7 and camera would
have something like a driver template which I could use as a starting point.
But so far I don't see anything like that.

Am I looking in the wrong place? Wishing for something not there? Are LCD7
and the HD camera cape meant to be just demo items not intended for use in
my own applications? Should I be asking these questions elsewhere?

BB-BONE-LCD7-01-00A3 is working with v4.1.x

Regards,

It's the LCD7 A3.

>
> LCD7 appears also to have only support on Angstrom?

Exactly which lcd is this?

dmesg | grep cape

[ 0.246668] bone-capemgr bone_capemgr.8: Baseboard:
'A335BNLT,000C,3514BBBK0653'
[ 0.246707] bone-capemgr bone_capemgr.8:
compatible-baseboard=ti,beaglebone-black
[ 0.270913] bone-capemgr bone_capemgr.8: slot #0: 'BeagleBone LCD7
CAPE,00A3,Beagleboardtoys,BB-BONE-LCD7-01'
[ 0.298532] bone-capemgr bone_capemgr.8: slot #1: No cape found
[ 0.328800] bone-capemgr bone_capemgr.8: slot #2: 'BeagleBone 1.2MP
CAMERA CAPE,00A0,RadiumBoards,BB-BONE-CAM-VVDN'
[ 0.359076] bone-capemgr bone_capemgr.8: slot #3: No cape found
[ 0.365326] bone-capemgr bone_capemgr.8: slot #4: specific override
[ 0.365366] bone-capemgr bone_capemgr.8: bone: Using override eeprom
data at slot 4
[ 0.365393] bone-capemgr bone_capemgr.8: slot #4:
'Bone-LT-eMMC-2G,00A0,Texas Instrument,BB-BONE-EMMC-2G'
[ 0.365525] bone-capemgr bone_capemgr.8: slot #5: specific override
[ 0.365560] bone-capemgr bone_capemgr.8: bone: Using override eeprom
data at slot 5
[ 0.365587] bone-capemgr bone_capemgr.8: slot #5:
'Bone-Black-HDMI,00A0,Texas Instrument,BB-BONELT-HDMI'
[ 0.365721] bone-capemgr bone_capemgr.8: slot #6: specific override
[ 0.365755] bone-capemgr bone_capemgr.8: bone: Using override eeprom
data at slot 6
[ 0.365783] bone-capemgr bone_capemgr.8: slot #6:
'Bone-Black-HDMIN,00A0,Texas Instrument,BB-BONELT-HDMIN'
[ 0.366591] bone-capemgr bone_capemgr.8: initialized OK.
[ 0.368984] bone-capemgr bone_capemgr.8: slot #0: Requesting part
number/version based 'BB-BONE-LCD7-01-00A3.dtbo
[ 0.369019] bone-capemgr bone_capemgr.8: slot #0: Requesting firmware
'BB-BONE-LCD7-01-00A3.dtbo' for board-name 'BeagleBone LCD7 CAPE', version
'00A3'
[ 0.369052] bone-capemgr bone_capemgr.8: slot #0: dtbo
'BB-BONE-LCD7-01-00A3.dtbo' loaded; converting to live tree
[ 0.369863] bone-capemgr bone_capemgr.8: slot #0: #4 overlays
[ 0.370987] bone-capemgr bone_capemgr.8: slot #2: Requesting part
number/version based 'BB-BONE-CAM-VVDN-00A0.dtbo
[ 0.371024] bone-capemgr bone_capemgr.8: slot #2: Requesting firmware
'BB-BONE-CAM-VVDN-00A0.dtbo' for board-name 'BeagleBone 1.2MP CAMERA CAPE',
version '00A0'
[ 0.371062] bone-capemgr bone_capemgr.8: slot #2: dtbo
'BB-BONE-CAM-VVDN-00A0.dtbo' loaded; converting to live tree
[ 0.378705] bone-capemgr bone_capemgr.8: slot #2: #2 overlays
[ 0.382458] bone-capemgr bone_capemgr.8: slot #2: Applied #2 overlays.

>
> If I try to run Ubuntu (from eMMC, instead of the uSD card needed for
> Angstrom with LCD7 and camera) now all I get is errors in the serial
> monitor:
> U-Boot SPL 2015.07-rc3-00001-g2c9c20a (Jun 30 2015 - 09:02:07)
> spl_register_fat_device: fat register err - -1 spl_register_fat_device:
fat
> register err - -1 spl_load_image_fat: error reading image u-boot.img,
err -
> -1 spl: ext4fs_open failed spl: ext4fs_open failed spl_load_image_ext:
error
> reading image uImage, err - -1 spl: ext4fs_open failed
spl_load_image_ext:
> error reading image u-boot.img, err - -1 spl: mmc: no boot mode left to
try
> ### ERROR ### Please RESET the board ###

Early lcd7's shared a few lines on the eMMC....

Oh yeah now I remember that, so that's why Angstrom has to boot from uSD.

You could install a set of header and clip off the offending pins between
BBB and LCD7.

BB-BONE-LCD7-01-00A3 is working with v4.1.x

OK I can try that. Been testing another Jul 08 Ubuntu 14.04.2 with Kernel
4.1.2-ti-r3.

So if I get a BBB with this kernel installed and THEN plug that into LCD7
it might work?

This is no longer needed:
Basically, */etc/modules *must be edited but you must have root privileges.

Add to the end of the file :

*fbcon*
*ti_tscadc*

Thanks!

Bruce

OK, loaded a BBB Rev C with Kernel 4.1 per previous posting, now on boot I
get

Starting kernel ...

[ 0.000455] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[ 0.000464] This ensures that you still see kernel messages. Please
[ 0.000472] update your kernel commandline.
[ 3.279071] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 3.310764] slave hdmi: could not get i2c
[ 3.628588] omap_voltage_late_init: Voltage driver support not added
[ 4.017363] bone_capemgr bone_capemgr: slot #1: No cape found
[ 4.077366] bone_capemgr bone_capemgr: slot #2: No cape found
[ 4.137349] bone_capemgr bone_capemgr: slot #3: No cape found
[ 5.147673] bone_capemgr bone_capemgr: loader: failed to load slot-0
BB-BONE-LCD7-01:00A3 (prio 0)

and
ubuntu@arm:~$ dmesg | grep cape
[ 3.924132] bone_capemgr bone_capemgr: Baseboard:
'A335BNLT,0A5A,1513BBBK1601'
[ 3.924168] bone_capemgr bone_capemgr:
compatible-baseboard=ti,beaglebone-black - #slots=4
[ 3.961456] bone_capemgr bone_capemgr: slot #0: 'BeagleBone LCD7
CAPE,00A3,Beagleboardtoys,BB-BONE-LCD7-01'
[ 4.017363] bone_capemgr bone_capemgr: slot #1: No cape found
[ 4.077366] bone_capemgr bone_capemgr: slot #2: No cape found
[ 4.137349] bone_capemgr bone_capemgr: slot #3: No cape found
[ 4.143443] bone_capemgr bone_capemgr: initialized OK.
[ 5.147673] bone_capemgr bone_capemgr: loader: failed to load slot-0
BB-BONE-LCD7-01:00A3 (prio 0)

So at least it booted from eMMC while plugged into LCD7. But is it happy?
The LCD is blank. It should be the default display I would hope.

I did this:
# /etc/modules: kernel modules to load at boot time.

OK, loaded a BBB Rev C with Kernel 4.1 per previous posting, now on boot I
get

make sure to set:

/boot/uEnv.txt

dtb=am335x-boneblack-overlay.dtb

as we don't have hdmi/emmc setup for removal yet..

Starting kernel ...

[ 0.000455] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[ 0.000464] This ensures that you still see kernel messages. Please
[ 0.000472] update your kernel commandline.
[ 3.279071] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 3.310764] slave hdmi: could not get i2c
[ 3.628588] omap_voltage_late_init: Voltage driver support not added
[ 4.017363] bone_capemgr bone_capemgr: slot #1: No cape found
[ 4.077366] bone_capemgr bone_capemgr: slot #2: No cape found
[ 4.137349] bone_capemgr bone_capemgr: slot #3: No cape found
[ 5.147673] bone_capemgr bone_capemgr: loader: failed to load slot-0
BB-BONE-LCD7-01:00A3 (prio 0)

and
ubuntu@arm:~$ dmesg | grep cape
[ 3.924132] bone_capemgr bone_capemgr: Baseboard:
'A335BNLT,0A5A,1513BBBK1601'
[ 3.924168] bone_capemgr bone_capemgr:
compatible-baseboard=ti,beaglebone-black - #slots=4
[ 3.961456] bone_capemgr bone_capemgr: slot #0: 'BeagleBone LCD7
CAPE,00A3,Beagleboardtoys,BB-BONE-LCD7-01'
[ 4.017363] bone_capemgr bone_capemgr: slot #1: No cape found
[ 4.077366] bone_capemgr bone_capemgr: slot #2: No cape found
[ 4.137349] bone_capemgr bone_capemgr: slot #3: No cape found
[ 4.143443] bone_capemgr bone_capemgr: initialized OK.
[ 5.147673] bone_capemgr bone_capemgr: loader: failed to load slot-0
BB-BONE-LCD7-01:00A3 (prio 0)

So at least it booted from eMMC while plugged into LCD7. But is it happy?
The LCD is blank. It should be the default display I would hope.

I did this:
# /etc/modules: kernel modules to load at boot time.
#
# This file contains the names of kernel modules that should be loaded
# at boot time, one per line. Lines beginning with "#" are ignored.
# Parameters can be specified after the module name.
fbcon
ti_tscadc
and reboot.

Still on serial monitor
Starting kernel ...

[ 0.000462] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[ 0.000472] This ensures that you still see kernel messages. Please
[ 0.000480] update your kernel commandline.
[ 3.278997] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 3.310713] slave hdmi: could not get i2c
[ 3.628588] omap_voltage_late_init: Voltage driver support not added
[ 4.017394] bone_capemgr bone_capemgr: slot #1: No cape found
[ 4.077399] bone_capemgr bone_capemgr: slot #2: No cape found
[ 4.137382] bone_capemgr bone_capemgr: slot #3: No cape found
[ 5.147697] bone_capemgr bone_capemgr: loader: failed to load slot-0
BB-BONE-LCD7-01:00A3 (prio 0)

nothing on LCD

and

ubuntu@arm:~$ dmesg | grep cape
[ 3.924167] bone_capemgr bone_capemgr: Baseboard:
'A335BNLT,0A5A,1513BBBK1601'
[ 3.924202] bone_capemgr bone_capemgr:
compatible-baseboard=ti,beaglebone-black - #slots=4
[ 3.961489] bone_capemgr bone_capemgr: slot #0: 'BeagleBone LCD7
CAPE,00A3,Beagleboardtoys,BB-BONE-LCD7-01'
[ 4.017394] bone_capemgr bone_capemgr: slot #1: No cape found
[ 4.077399] bone_capemgr bone_capemgr: slot #2: No cape found
[ 4.137382] bone_capemgr bone_capemgr: slot #3: No cape found
[ 4.143479] bone_capemgr bone_capemgr: initialized OK.
[ 5.147697] bone_capemgr bone_capemgr: loader: failed to load slot-0
BB-BONE-LCD7-01:00A3 (prio 0)

It seems to be "finding" the LCD7 but not loading a driver?

Regards,

OK I did that.

But this would seem to disable HDMI and eMMC? All I am trying to do is get
LCD7 to be the default display. If I disable eMMC then I can't boot from
that, and I don't have a complete ubuntu 14.04.2 July 08 with kernel 4.1
runtime image on a uSD. I don't know how to do that. Is there a performance
hit using uSD as the runtime vs eMMC?

Before adding this line I was able to boot (with kernel 4.1) from eMMC
while BBB was plugged into LCD7 A3. Is there a way to just disable HDMI and
leave eMMC enabled?

If I cut those pins between BBB and LCD7 is there a way to make LCD7 the
BBB display under ubuntu? Or does kernel 4.1 accomplish the same thing by
changing how those pins get used?

I hope those questions were clear.

Thanks
Bruce

Here is /boot/uEnv.txt

sudo nano /boot/uEnv.txt

#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0

uname_r=4.1.2-ti-r3

#dtb=

dtb=am335x-boneblack-overlay.dtb

##BeagleBone Black dtb's for v4.1.x (BeagleBone White just works..)

##HDMI/eMMC disabled:

#dtb=am335x-boneblack-overlay.dtb

##cape-universal

#dtb=am335x-boneblack-universal.dtb

##wl1835

#dtb=am335x-boneblack-wl1835mod.dtb

##replicape

#dtb=am335x-boneblack-replicape.dtb

Now on boot, with BBB plugged into LCD7 A3:
Starting kernel ...

[ 0.000460] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[ 0.000469] This ensures that you still see kernel messages. Please
[ 0.000478] update your kernel commandline.
[ 3.278009] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 3.466616] omap_voltage_late_init: Voltage driver support not added
[ 3.626976] bone_capemgr bone_capemgr: slot #1: No cape found
[ 3.686969] bone_capemgr bone_capemgr: slot #2: No cape found
[ 3.746968] bone_capemgr bone_capemgr: slot #3: No cape found
[ 4.757309] bone_capemgr bone_capemgr: loader: failed to load slot-0
BB-BONE-LCD7-01:00A3 (prio 0)
Gave up waiting for root device. Common problems:
- Boot args (cat /proc/cmdline)
   - Check rootdelay= (did the system wait long enough?)
   - Check root= (did the system wait for the right device?)
- Missing modules (cat /proc/modules; ls /dev)
ALERT! /dev/disk/by-uuid/f87df525-214f-4530-8506-dcc9bedb720a does not
exist. Dropping to a shell!

BusyBox v1.21.1 (Ubuntu 1:1.21.0-1ubuntu1) built-in shell (ash)
Enter 'help' for a list of built-in commands.

(initramfs)

Sorry, i don't have the eMMC working as an overlay yet..

My lcd's are at home, so i'll try and setup an
(am335x-boneblack-emmc-overlay.dtb) tonight, for lcd + eMMC
conditions..

Regards,

okay with: linux-image-4.1.2-ti-r4 use:
dtb=am335x-boneblack-emmc-overlay.dtb

it'll take a few hours to finish building...

Regards,

Awesome, let me know when it's ready to use and I can try right away.

Bruce

*okay with: linux-image-4.1.2-ti-r4
use:dtb=am335x-boneblack-emmc-overlay.dtbit'll take a few hours to finish
building...*

Bruce

Well it just finished on the build farm..

http://builds.beagleboard.org/builders/build-kernel/builds/61

wget http://builds.beagleboard.org/linux/4.1/f4ce60f0b74d04db24b7b0fd8fb574ead7ceb16c/linux-image-4.1.2-gitf4ce60f0b74d04db24b7b0fd8fb574ead7ceb16c_1cross_armhf.deb

sudo dpkg -i linux-image-4.1.2-gitf4ce60f0b74d04db24b7b0fd8fb574ead7ceb16c_1cross_armhf.deb

sudo reboot

Regards,

OK, thanks. Followed your instructions for wget. It's amazing to me that
BBB can do this sort of major update "in place" with only 4 GB of flash.

Then I edited /boot/uEnv.txt so now the first lines of that are:
*#Docs: http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0
<http://elinux.org/Beagleboard:U-boot_partitioning_layout_2.0>*

*uname_r=4.1.2-gitf4ce60f0b74d04db24b7b0fd8fb574ead7ceb16c*
*## HDMI disabled but emmc enabled, I think/hope*
*dtb=am335x-boneblack-emmc-overlay.dtb*

*##BeagleBone Black dtb's for v4.1.x (BeagleBone White just works..)*

*##HDMI/eMMC disabled:*
*#dtb=am335x-boneblack-overlay.dtb*

*##cape-universal*
*#dtb=am335x-boneblack-universal.dtb*

*Do I also need the dtb for this cape-universal? Is that a specific cape or
something used by all capes?*

Then reboot. It still boots from eMMC with the new uEnv.txt.

*ubuntu@arm:~$ uname -a*
*Linux arm 4.1.2-gitf4ce60f0b74d04db24b7b0fd8fb574ead7ceb16c #108 SMP
PREEMPT Thu Jul 16 19:06:39 UTC 2015 armv7l armv7l armv7l GNU/Linux*

so it has the new kernel.

Time to plug into LCD7 and see what happens. First shutdown cleanly.
*When I hold the power button for several seconds, then release, no
shutdown initiates. ???* so instead
sudo shutdown now
hmm.. there seem to be new options in the serial monitor... which seems to
prevent shutdown. When I try to enter the "temppwd" the system just boots
up again, same as Control-D
*The system is going down for maintenance NOW!*
*ubuntu@arm:~$ wait-for-state stop/waiting*
* * *
* * Stopping rsync daemon rsync [
OK ] *
* * Stopping DNS forwarder and DHCP server dnsmasq [
OK ] *
* [
OK ]*
* * Killing all remaining processes...
[fail] *
* * Will now switch to single-user mode*
*Give root password for maintenance*
*(or type Control-D to continue): *
*rc-sysinit start/running, process 2809*
* * Loading cpufreq kernel modules... [
OK ] *
* * Starting DNS forwarder and DHCP server dnsmasq [
OK ] *
* * CPUFreq Utilities: Setting ondemand CPUFreq governor... [
OK ] * CPU0... *
* * Starting web server apache2
      * *

*Ubuntu 14.04.2 LTS arm ttyO0*

So I don't know how to do a clean shutdown...

Anyway on to try LCD3 Rev A. Plug in BBB and it boots from eMMC
Starting kernel ...

[ 0.000446] WARNING: Your 'console=ttyO0' has been replaced by 'ttyS0'
[ 0.000456] This ensures that you still see kernel messages. Please
[ 0.000464] update your kernel commandline.
[ 3.263692] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle
[ 3.558075] omap_voltage_late_init: Voltage driver support not added
[ 3.726897] bone_capemgr bone_capemgr: slot #1: No cape found
[ 3.786892] bone_capemgr bone_capemgr: slot #2: No cape found
[ 3.846896] bone_capemgr bone_capemgr: slot #3: No cape found
[ 4.857253] bone_capemgr bone_capemgr: loader: failed to load slot-0
BB-BONE-LCD7-01:00A3 (prio 0)

and
ubuntu@arm:~$ dmesg | grep cape
[ 3.636512] bone_capemgr bone_capemgr: Baseboard:
'A335BNLT,0A5A,1513BBBK1601'
[ 3.636545] bone_capemgr bone_capemgr:
compatible-baseboard=ti,beaglebone-black - #slots=4
[ 3.670921] bone_capemgr bone_capemgr: slot #0: 'BeagleBone LCD7
CAPE,00A3,Beagleboardtoys,BB-BONE-LCD7-01'
[ 3.726897] bone_capemgr bone_capemgr: slot #1: No cape found
[ 3.786892] bone_capemgr bone_capemgr: slot #2: No cape found
[ 3.846896] bone_capemgr bone_capemgr: slot #3: No cape found
[ 3.852928] bone_capemgr bone_capemgr: initialized OK.
[ 4.857253] bone_capemgr bone_capemgr: loader: failed to load slot-0
BB-BONE-LCD7-01:00A3 (prio 0)

LCD7 is blank. No HDMI output (as expected, thought I would try to verify).

Something else I should configure?

Thanks
Bruce

Just for fun tried with LCD3 Rev A2, with similar results
ubuntu@arm:~$ dmesg | grep cape
[ 3.636512] bone_capemgr bone_capemgr: Baseboard:
'A335BNLT,0A5A,1513BBBK1601'
[ 3.636545] bone_capemgr bone_capemgr:
compatible-baseboard=ti,beaglebone-black - #slots=4
[ 3.670968] bone_capemgr bone_capemgr: slot #0: 'BeagleBone LCD3
CAPE,00A2,Beagleboardtoys,BB-BONE-LCD3-01'
[ 3.726940] bone_capemgr bone_capemgr: slot #1: No cape found
[ 3.786936] bone_capemgr bone_capemgr: slot #2: No cape found
[ 3.846939] bone_capemgr bone_capemgr: slot #3: No cape found
[ 3.852964] bone_capemgr bone_capemgr: initialized OK.
[ 4.857269] bone_capemgr bone_capemgr: loader: failed to load slot-0
BB-BONE-LCD3-01:00A2 (prio 0)

Bruce

Are you able to get this kernel to treat LCD7 as the display? I’m still not seeing that result here. Angstrom kernel 3.8.13 does drive the LCD OK, booting from eMMC, using the 2013-09-04 eMMC-Flasher image (pretty old but the most recent Angstrom I could find). But I prefer to use ubuntu and the more up to date kernels you are building.

Bruce

On the other hand, Angstrom goes off in the weeds quite easily, leaving
selected menus on the screen with these errrors:
beaglebone login: [ 504.326720] mmcblk0: error -84 transferring data,
sector 2571625, nr 128, cmd response 0x900, card status 0xb00
[ 504.408042] mmcblk0: error -84 transferring data, sector 2589489, nr
128, cmd response 0x900, card status 0xb00
[ 504.496869] mmcblk0: error -84 transferring data, sector 2589617, nr
128, cmd response 0x900, card status 0xb00
[ 504.645162] mmcblk0: error -84 transferring data, sector 2560001, nr
128, cmd response 0x900, card status 0x0
I'm not sure why it would be writing to eMMC as part of a menu/window
selection routine... maybe coincidence and better put into another thread
since this one is about ubuntu accessing LCD7.

Bruce

Hi Bruce, Robert

Have you been able to have the LCD output working ?

On my side I have install opensuse 13.2 on µSD and update the kernel to the latest version 4.1.6
The HDMI outpout is working.

When I plugge the LCD 4DCAPE-70T the capemgr found the LCD but it failed to load the slot same issue as Bruce.

On my side I do not have any uEnv.txt in my boot folder it seems opensuse is using the boot.scr
I create it and add only the line below and of course I copied the file am335x-boneblack-emmc-overlay.dtb in /boot/dtb
dtb=am335x-boneblack-emmc-overlay.dtb

But it still have the same issue.

Best regards,

Matthieu

No, not really. The touch screen is so jittery (holding a stylus in one
place has the pointer bouncing around about +/- 4 pixels no matter what)
that it is almost impossible to select small items on screen.

I never got Ubuntu to work.

But given the issue with the touchscreen (can it be fixed? I don't know),
and the sharing of pins problem with the LCD Cape, I have decided to stick
with HDMI-input touchscreens. I have a few which have none of those
problems. Prices are much better, too.

Bruce