tilcdc 4830e000.fb: no encoders/connectors found ---- 4.14LTS

[sos0...@gmail.com]

I'm trying to get a custom cape with LCD up & running with the 4.14LTS LXQT image "http://debian.beagleboard.org/images/bone-debian-9.5-lxqt-armhf-2018-10-07-4gb.img.xz"

The dtbo I'm using works fine on an old image, 3.8.13 but not on the newer 4.14 - are there changes I need to make?

It seems it doesn't find the the LCD port?

Why? How can I get it to see the LCD?

Regards, 

James

The log from the serial port is:

U-Boot 2018.09-00002-g0b54a51eee (Sep 10 2018 - 19:41:39 -0500), Build: jenkins-github_Bootloader-Builder-65

CPU  : AM335X-GP rev 2.1

I2C:   ready

DRAM:  512 MiB

No match for driver 'omap_hsmmc'

No match for driver 'omap_hsmmc'

Some drivers were not found

Reset Source: Power-on reset has occurred.

RTC 32KCLK Source: External.

MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1

Loading Environment from EXT4... ** File not found /boot/uboot.env **

** Unable to read "/boot/uboot.env" from mmc0:1 **

Board: BeagleBone Black

<ethaddr> not set. Validating first E-fuse MAC

BeagleBone Black:

debug: process_cape_part_number:[BB-BONE-Mita-00.]

debug: fixup, extra . in eeprom field

debug: process_cape_part_number:[42422D424F4E452D4D6974612D3030]

BeagleBone: cape eeprom: i2c_probe: 0x54: /lib/firmware/BB-BONE-Mita-00-00A0.dtbo [0xfe4416f]

BeagleBone: cape eeprom: i2c_probe: 0x55:

BeagleBone: cape eeprom: i2c_probe: 0x56:

BeagleBone: cape eeprom: i2c_probe: 0x57:

Net:   eth0: MII MODE

cpsw, usb_ether

Press SPACE to abort autoboot in 2 seconds

board_name=[A335BNLT] ...

board_rev=[00C0] ...

switch to partitions #0, OK

mmc0 is current device

SD/MMC found on device 0

switch to partitions #0, OK

mmc0 is current device

Scanning mmc 0:1...

gpio: pin 56 (gpio 56) value is 0

gpio: pin 55 (gpio 55) value is 0

gpio: pin 54 (gpio 54) value is 0

gpio: pin 53 (gpio 53) value is 1

switch to partitions #0, OK

mmc0 is current device

gpio: pin 54 (gpio 54) value is 1

Checking for: /uEnv.txt ...

Checking for: /boot.scr ...

Checking for: /boot/boot.scr ...

Checking for: /boot/uEnv.txt ...

gpio: pin 55 (gpio 55) value is 1

2405 bytes read in 45 ms (51.8 KiB/s)

Loaded environment from /boot/uEnv.txt

Checking if uname_r is set in /boot/uEnv.txt...

gpio: pin 56 (gpio 56) value is 1

Running uname_boot ...

loading /boot/vmlinuz-4.14.71-ti-r80 ...

10416640 bytes read in 869 ms (11.4 MiB/s)

debug: [enable_uboot_overlays=1] ...

debug: [enable_uboot_cape_universal=] ...

debug: [uboot_base_dtb_univ=am335x-boneblack-uboot.dtb] ...

uboot_overlays: [uboot_base_dtb=am335x-boneblack-uboot.dtb] ...

uboot_overlays: Switching too: dtb=am335x-boneblack-uboot.dtb ...

loading /boot/dtbs/4.14.71-ti-r80/am335x-boneblack-uboot.dtb ...

58048 bytes read in 45 ms (1.2 MiB/s)

uboot_overlays: [fdt_buffer=0x60000] ...

uboot_overlays: loading /lib/firmware/BB-UART1-00A0.dtbo ...

1075 bytes read in 497 ms (2 KiB/s)

uboot_overlays: loading /lib/firmware/BB-UART2-00A0.dtbo ...

1075 bytes read in 628 ms (1000 Bytes/s)

uboot_overlays: loading /lib/firmware/BB-UART4-00A0.dtbo ...

1075 bytes read in 744 ms (1000 Bytes/s)

uboot_overlays: loading /lib/firmware/BB-BONE-Mita-00-00A0.dtbo ...

6211 bytes read in 476 ms (12.7 KiB/s)

uboot_overlays: loading /lib/firmware/BB-BONE-eMMC1-01-00A0.dtbo ...

1440 bytes read in 622 ms (2 KiB/s)

uboot_overlays: uboot loading of [/lib/firmware/BB-HDMI-TDA998x-00A0.dtbo] disabled by /boot/uEnv.txt [disable_uboot_overlay_video=1]...

uboot_overlays: loading /lib/firmware/BB-ADC-00A0.dtbo ...

711 bytes read in 519 ms (1000 Bytes/s)

uboot_overlays: [uboot_detected_capes=BB-BONE-Mita-00,] ...

uboot_overlays: add [enable_uboot_cape_universal=1] to /boot/uEnv.txt to enable...

loading /boot/initrd.img-4.14.71-ti-r80 ...

5006883 bytes read in 426 ms (11.2 MiB/s)

debug: [console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait uboot_detected_capes=BB-BONE-Mita-00, coherent_pool=1M net.ifnames=0 quiet] ...

debug: [bootz 0x82000000 0x88080000:4c6623 88000000] ...

## Flattened Device Tree blob at 88000000

   Booting using the fdt blob at 0x88000000

   Loading Ramdisk to 8fb39000, end 8ffff623 ... OK

   reserving fdt memory region: addr=88000000 size=70000

   Loading Device Tree to 8fac6000, end 8fb38fff ... OK

Starting kernel ...

[    0.000804] timer_probe: no matching timers found

[    1.069985] wkup_m3_ipc 44e11324.wkup_m3_ipc: could not get rproc handle

[    1.096154] OF: graph: no port node found in /ocp/fb

[    1.101450] OF: graph: no port node found in /ocp/fb

[    1.107453] OF: graph: no port node found in /ocp/fb

[    1.112489] tilcdc 4830e000.fb: no encoders/connectors found

[    1.366722] omap_voltage_late_init: Voltage driver support not added

[    1.373815] PM: Cannot get wkup_m3_ipc handle

rootfs: recovering journal

rootfs: clean, 160158/483840 files, 941509/1939456 blocks

Debian GNU/Linux 9 beaglebone ttyS0

BeagleBoard.org Debian Image 2018-10-07

Support/FAQ: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian

The  /boot/uEnv.txt is as follows:

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

uname_r=4.14.71-ti-r80

#uuid=

#dtb=

###U-Boot Overlays###

###Documentation: http://elinux.org/Beagleboard:BeagleBoneBlack_Debian#U-Boot_Overlays

###Master Enable

enable_uboot_overlays=1

###

###Overide capes with eeprom

uboot_overlay_addr0=/lib/firmware/BB-UART1-00A0.dtbo

uboot_overlay_addr1=/lib/firmware/BB-UART2-00A0.dtbo

uboot_overlay_addr2=/lib/firmware/BB-UART4-00A0.dtbo

#uboot_overlay_addr3=/lib/firmware/BB-BONE-Mita-00-00A0.dtbo

#uboot_overlay_addr0=/lib/firmware/<file0>.dtbo

#uboot_overlay_addr1=/lib/firmware/<file1>.dtbo

#uboot_overlay_addr2=/lib/firmware/<file2>.dtbo

#uboot_overlay_addr3=/lib/firmware/<file3>.dtbo

###

###Additional custom capes

uboot_overlay_addr4=/lib/firmware/BB-BONE-Mita-00-00A0.dtbo

#uboot_overlay_addr4=/lib/firmware/<file4>.dtbo

#uboot_overlay_addr5=/lib/firmware/<file5>.dtbo

#uboot_overlay_addr6=/lib/firmware/<file6>.dtbo

#uboot_overlay_addr7=/lib/firmware/<file7>.dtbo

###

###Custom Cape

#dtb_overlay=/lib/firmware//lib/firmware/BB-BONE-Mita-00-00A0.dtbo

###

###Disable auto loading of virtual capes (emmc/video/wireless/adc)

#disable_uboot_overlay_emmc=1

disable_uboot_overlay_video=1

disable_uboot_overlay_audio=1

disable_uboot_overlay_wireless=1

#disable_uboot_overlay_adc=1

###

###PRUSS OPTIONS

###pru_rproc (4.4.x-ti kernel)

#uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-4-TI-00A0.dtbo

###pru_rproc (4.14.x-ti kernel)

#uboot_overlay_pru=/lib/firmware/AM335X-PRU-RPROC-4-14-TI-00A0.dtbo

###pru_uio (4.4.x-ti, 4.14.x-ti & mainline/bone kernel)

#uboot_overlay_pru=/lib/firmware/AM335X-PRU-UIO-00A0.dtbo

###

###Cape Universal Enable

#enable_uboot_cape_universal=1

###

###Debug: disable uboot autoload of Cape

#disable_uboot_overlay_addr0=1

#disable_uboot_overlay_addr1=1

#disable_uboot_overlay_addr2=1

#disable_uboot_overlay_addr3=1

###

###U-Boot fdt tweaks... (60000 = 384KB)

#uboot_fdt_buffer=0x60000

###U-Boot Overlays###

cmdline=coherent_pool=1M net.ifnames=0 quiet

#In the event of edid real failures, uncomment this next line:

#cmdline=coherent_pool=1M net.ifnames=0 quiet video=HDMI-A-1:1024x768@60e

#Use an overlayfs on top of a read-only root filesystem:

#cmdline=coherent_pool=1M net.ifnames=0 quiet overlayroot=tmpfs

##enable Generic eMMC Flasher:

##make sure, these tools are installed: dosfstools rsync

version.sh output:

git:/opt/scripts/:[e9bcff232834702c1c810710706ee815d77b080b]

eeprom:[A335BNLT00C05315BBBK0A5E]

model:[TI_AM335x_BeagleBone_Black]

dogtag:[BeagleBoard.org Debian Image 2018-10-07]

bootloader:[microSD-(push-button)]:[/dev/mmcblk0]:[U-Boot 2018.09-00002-g0b54a51eee]:[location: dd MBR]

kernel:[4.14.71-ti-r80]

nodejs:[v6.14.4]

uboot_overlay_options:[enable_uboot_overlays=1]

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

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

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

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

uboot_overlay_options:[disable_uboot_overlay_video=1]

uboot_overlay_options:[disable_uboot_overlay_audio=1]

uboot_overlay_options:[disable_uboot_overlay_wireless=1]

pkg check: to individually upgrade run: [sudo apt install --only-upgrade <pkg>]

pkg:[bb-cape-overlays]:[4.4.20181019.0-0rcnee0~stretch+20181019]

pkg:[bb-wl18xx-firmware]:[1.20180517-0rcnee0~stretch+20180517]

pkg:[kmod]:[23-2rcnee1~stretch+20171005]

pkg:[librobotcontrol]:[1.0.3-git20181009.0-0rcnee0~stretch+20181010]

pkg:[firmware-ti-connectivity]:[20170823-1rcnee1~stretch+20180328]

groups:[debian : debian adm kmem dialout cdrom floppy audio dip video plugdev users systemd-journal i2c bluetooth netdev cloud9ide gpio pwm eqep admin spi tisdk weston-launch xenomai]

cmdline:[console=ttyO0,115200n8 bone_capemgr.uboot_capemgr_enabled=1 root=/dev/mmcblk0p1 ro rootfstype=ext4 rootwait uboot_detected_capes=BB-BONE-Mita-00, coherent_pool=1M net.ifnames=0 quiet]

dmesg | grep pinctrl-single

[    1.064022] pinctrl-single 44e10800.pinmux: 142 pins at pa f9e10800 size 568

dmesg | grep gpio-of-helper

[    1.065283] gpio-of-helper ocp:cape-universal: ready

END

[Robert Nelson]

On Mon, Oct 22, 2018 at 12:27 PM <sos0...@gmail.com> wrote:
>
> I'm trying to get a custom cape with LCD up & running with the 4.14LTS LXQT image "http://debian.beagleboard.org/images/bone-debian-9.5-lxqt-armhf-2018-10-07-4gb.img.xz"
> The dtbo I'm using works fine on an old image, 3.8.13 but not on the newer 4.14 - are there changes I need to make?

Yeapers..

> It seems it doesn't find the the LCD port?
> Why? How can I get it to see the LCD?

Lots of examples to compare with:

https://github.com/beagleboard/bb.org-overlays/tree/master/src/arm

Regards,

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

[sos0...@gmail.com]

Yeah, I've been doing that for a few days and I can't see anything wrong.

Specifically, I'd like to know should an old device tree (from 3.8) work on the newer image?

Has anyone seen that error message before & what does it refer to?

Thanks.

[Robert Nelson]

On Mon, Oct 22, 2018 at 4:13 PM <sos0...@gmail.com> wrote:
>
> Yeah, I've been doing that for a few days and I can't see anything wrong.
> Specifically, I'd like to know should an old device tree (from 3.8) work on the newer image?
> Has anyone seen that error message before & what does it refer to?

Now you switched to "device tree"

In either case, a '3.8.x' device tree or an overlay from the '3.8.x'
era will not work on a newer image.

If you have and want 3.8.x, just install the un-supported 3.8.13 based kernel..

cd /opt/scripts/tools/
git pull
sudo ./update_kernel.sh --bone-channel --stable

and by "un-supported" i mean all emails about 3.8.13 will be ignored..