Sama5d3xek - Morty 2.2.2 Build - display fails

This forum is for users of Microchip MPUs and who are interested in using Linux OS.

Moderator: nferre

Kerberosity
Posts: 2
Joined: Fri Oct 27, 2017 2:07 am

Sama5d3xek - Morty 2.2.2 Build - display fails

Thu Nov 02, 2017 1:53 am

Greetings,


I'll get right to it.

My tools:
- I have a SAMA5D3xEK evaluation board (with the D34) - this is the big one with all the bells and whistles that they don't sell anymore.
- I've been using Yocto (Morty 2.2.2 Branch) via command line.
- I've also been using meta-atmel, meta-openembedded, meta-qt5, etc. (again Morty version).

My problem:
I've built the "atmel-qt5-demo-image" multiple times. Each time, I can get the kernel, rootfs, etc. to boot and load but the screen always winds up with some weird line pattern, random popcorn static, or completely blank. There is absolutely no meaningful display data.

Here's what I've done:
- I've validated my hardware (and revalidated a couple times throughout) by loading the stock demo image (linux4sam/bin/view/Linux4SAM/Sama5d3xekMainPage). Aside from some poor touchscreen calibration it worked each time.
- Using the "How To" on Linux4Sam as a template, I built my own atmel demo image (as I mentioned above, a couple times).
- I addressed version compatibility issues and any fatal errors until I could get a successful build.
- Once I could build to completion I worked to eliminate any warnings that looked like they led to display problems (mesa, weston, wayland, related warnings).

With an image that builds without warnings but does not show anything on the display, I went a little deeper:

- I used putty to log into the SAMA5 and navigate it's file structure. I navigated to /usr/bin where weston is stored and tried to force it to execute. I got the following errors:

Code: Select all

root@sama5d3xek:/usr/bin# weston
Date: 2017-10-31 UTC
[22:37:24.511] weston 2.0.0
               http://wayland.freedesktop.org
               Bug reports to: https://bugs.freedesktop.org/enter_bug.cgi?product=Wayland&component=weston&version=2.0.0
               Build: 1.99.94-2-g4c4f13d configure.ac: bump to version 2.0.0 for the official release (2017-02-24 16:19:03 -0800)
[22:37:24.512] Command line: weston
[22:37:24.512] OS: Linux, 4.9.52-linux4sam_5.7, #1 Mon Oct 30 16:43:35 MDT 2017, armv7l
[22:37:24.512] warning: XDG_RUNTIME_DIR "/tmp" is not configured
correctly.  Unix access mode must be 0700 (current mode is 777),
and must be owned by the user (current owner is UID 0).
Refer to your distribution on how to get it, or
http://www.freedesktop.org/wiki/Specifications/basedir-spec
on how to implement it.
[22:37:24.513] Starting with no config file.
[22:37:24.515] Output repaint window is 7 ms maximum.
[22:37:24.515] Loading module '/usr/lib/libweston-2/drm-backend.so'
[22:37:24.537] initializing drm backend
[22:37:24.538] logind: not running in a systemd session
[22:37:24.538] logind: cannot setup systemd-logind helper (-123), using legacy fallback
[22:37:24.538] failed to get VT mode: Inappropriate ioctl for device
[22:37:24.539] fatal: drm backend should be run using weston-launch binary or as root
[22:37:24.539] fatal: failed to create compositor backend

Now, I note that there looks to be multiple issues in the error output but I think the root cause is the fact that systemd does not seem to be running (I got "command not found" when I typed in "systemd --test"), nor does it seem to exist in the image. I know that it is included in the Morty 2.2.2 variant of Yocto.

- I've searched on this site (and others) for topics related to weston, systemd, sama5d3xek, display, etc.

I've included the bootup output of the atmel demo image.

Finally, my questions:
- Can anyone tell me where to go from here?
- Am I chasing the right problem or is lack of systemd a non-issue?
- Is there something that can exclude systemd from the build?
- Have I misunderstood how this demo runs it's interface (i.e., weston)?
- Does anyone see any additional messages that should I should start investigating deeper as potential root causes to my overall problem (the screen is not coming up)?


Any nudge in the right direction would be appreciated. I know I have a lot more to read and learn but I feel like I'm missing something and my learning process has been stagnating.


Thanks!




Bootup Log:

Code: Select all

=~=~=~=~=~=~=~=~=~=~=~= PuTTY log 2017.10.31 17:17:33 =~=~=~=~=~=~=~=~=~=~=~=
RomBOOT



AT91Bootstrap 3.8.9 (Mon Oct 30 19:29:35 MDT 2017)

1-Wire: Loading 1-Wire information ...
1-Wire: ROM Searching ... Done, 3 1-Wire chips found

1-Wire: BoardName | [Revid] | VendorName
  #0  SAMA5D34-CM [DD4]      EMBEST
  #1  SAMA5D3x-MB [CC3]      FLEX
  #2  SAMA5D3x-DM [BB2]      FLEX

1-Wire: Board sn: 0x481242c revision: 0x6a0823

NAND: ONFI flash detected
NAND: Manufacturer ID: 0x2c Chip ID: 0xda
NAND: Page Bytes: 2048, Spare Bytes: 64
NAND: ECC Correctability Bits: 4, ECC Sector Bytes: 512
NAND: Disable On-Die ECC
NAND: Initialize PMECC params, cap: 4, sector: 512
NAND: Image: Copy 0xa0000 bytes from 0x40000 to 0x26f00000
NAND: Done to load image
<debug_uart> 

U-Boot 2017.03-linux4sam_5.7 (Oct 30 2017 - 19:29:32 -0600)

CPU: SAMA5D34
Crystal frequency:       12 MHz
CPU clock        :      528 MHz
Master clock     :      132 MHz
DRAM:  512 MiB
Flash: 16 MiB
NAND:  256 MiB
MMC:   Atmel mci: 0, Atmel mci: 1
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
Net:   
Error: ethernet@f0028000 address not set.
No ethernet found.
Hit any key to stop autoboot:  3  2  1  0 

NAND read: device 0 offset 0x180000, size 0x80000
 524288 bytes read: OK

NAND read: device 0 offset 0x200000, size 0x600000
 6291456 bytes read: OK
## Flattened Device Tree blob at 21000000
   Booting using the fdt blob at 0x21000000
   Loading Device Tree to 3fb3f000, end 3fb4a68e ... OK

Starting kernel ...

Booting Linux on physical CPU 0x0
Linux version 4.9.52-linux4sam_5.7 (jschmeiser@josh-ubuntu) (gcc version 6.2.0 (GCC) ) #1 Mon Oct 30 16:43:35 MDT 2017
CPU: ARMv7 Processor [410fc051] revision 1 (ARMv7), cr=10c53c7d
CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
OF: fdt:Machine model: Atmel SAMA5D34-EK
cma: Reserved 16 MiB at 0x3e800000
Memory policy: Data cache writeback
CPU: All CPU(s) started in SVC mode.
Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 129920
Kernel command line: console=ttyS0,115200 earlyprintk mtdparts=atmel_nand:256k(bootstrap)ro,768k(uboot)ro,256K(env_redundant),256k(env),512k(dtb),6M(kernel)ro,-(rootfs) rootfstype=ubifs ubi.mtd=6 root=ubi0:rootfs
PID hash table entries: 2048 (order: 1, 8192 bytes)
Dentry cache hash table entries: 65536 (order: 6, 262144 bytes)
Inode-cache hash table entries: 32768 (order: 5, 131072 bytes)
Memory: 493036K/524288K available (6144K kernel code, 197K rwdata, 984K rodata, 1024K init, 195K bss, 14868K reserved, 16384K cma-reserved)
Virtual kernel memory layout:
    vector  : 0xffff0000 - 0xffff1000   (   4 kB)
    fixmap  : 0xffc00000 - 0xfff00000   (3072 kB)
    vmalloc : 0xe0800000 - 0xff800000   ( 496 MB)
    lowmem  : 0xc0000000 - 0xe0000000   ( 512 MB)
    modules : 0xbf000000 - 0xc0000000   (  16 MB)
      .text : 0xc0008000 - 0xc0700000   (7136 kB)
      .init : 0xc0900000 - 0xc0a00000   (1024 kB)
      .data : 0xc0a00000 - 0xc0a31600   ( 198 kB)
       .bss : 0xc0a31600 - 0xc0a623f8   ( 196 kB)
NR_IRQS:16 nr_irqs:16 16
clocksource: pit: mask: 0xfffffff max_cycles: 0xfffffff, max_idle_ns: 14479245754 ns
sched_clock: 32 bits at 100 Hz, resolution 10000000ns, wraps every 21474836475000000ns
Console: colour dummy device 80x30
Calibrating delay loop... 351.43 BogoMIPS (lpj=1757184)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
CPU: Testing write buffer coherency: ok
Setting up static identity map for 0x20100000 - 0x20100058
devtmpfs: initialized
VFP support v0.3: implementor 41 architecture 2 part 30 variant 5 rev 1
clocksource: jiffies: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 19112604462750000 ns
futex hash table entries: 256 (order: -1, 3072 bytes)
pinctrl core: initialized pinctrl subsystem
NET: Registered protocol family 16
DMA: preallocated 256 KiB pool for atomic coherent allocations
cpuidle: using governor menu
AT91: PM: standby: standby, suspend: ulp0
gpio-at91 fffff200.gpio: at address e0814200
gpio-at91 fffff400.gpio: at address e0816400
gpio-at91 fffff600.gpio: at address e0818600
gpio-at91 fffff800.gpio: at address e081a800
gpio-at91 fffffa00.gpio: at address e081ca00
pinctrl-at91 ahb:apb:pinctrl@fffff200: initialized AT91 pinctrl driver
clocksource: tcb_clksrc: mask: 0xffffffff max_cycles: 0xffffffff, max_idle_ns: 115833966437 ns
at_hdmac ffffe600.dma-controller: Atmel AHB DMA Controller ( cpy set slave sg-cpy ), 8 channels
at_hdmac ffffe800.dma-controller: Atmel AHB DMA Controller ( cpy set slave sg-cpy ), 8 channels
AT91: Detected SoC family: sama5d3
AT91: Detected SoC: sama5d34, revision 2
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
at91_i2c f0014000.i2c: using dma0chan0 (tx) and dma0chan1 (rx) for DMA transfers
at91_i2c f0014000.i2c: AT91 i2c bus driver (hw version: 0x402).
at91_i2c f0018000.i2c: using dma0chan2 (tx) and dma0chan3 (rx) for DMA transfers
at91_i2c f0018000.i2c: AT91 i2c bus driver (hw version: 0x402).
media: Linux media interface: v0.10
Linux video capture interface: v2.00
Advanced Linux Sound Architecture Driver Initialized.
clocksource: Switched to clocksource tcb_clksrc
NET: Registered protocol family 2
TCP established hash table entries: 4096 (order: 2, 16384 bytes)
TCP bind hash table entries: 4096 (order: 2, 16384 bytes)
TCP: Hash tables configured (established 4096 bind 4096)
UDP hash table entries: 256 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 256 (order: 0, 4096 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
workingset: timestamp_bits=14 max_order=17 bucket_order=3
io scheduler noop registered (default)
f0020000.serial: ttyS2 at MMIO 0xf0020000 (irq = 24, base_baud = 4125000) is a ATMEL_SERIAL
ffffee00.serial: ttyS0 at MMIO 0xffffee00 (irq = 33, base_baud = 8250000) is a ATMEL_SERIAL
console [ttyS0] enabled
[drm] Initialized
brd: module loaded
loop: module loaded
ssc f0008000.ssc: Atmel SSC device at 0xe0880000 (irq 20)
atmel_nand_nfc 70000000.nfc: NFC is probed.
atmel_nand 60000000.nand: Using dma0chan4 for DMA transfers.
nand: device found, Manufacturer ID: 0x2c, Chip ID: 0xda
nand: Micron MT29F2G08ABAEAWP
nand: 256 MiB, SLC, erase size: 128 KiB, page size: 2048, OOB size: 64
atmel_nand 60000000.nand: Use On Flash BBT
atmel_nand 60000000.nand: minimum ECC: 4 bits in 512 bytes
atmel_nand 60000000.nand: Initialize PMECC params, cap: 4, sector: 512
atmel_nand 60000000.nand: Using NFC Sram read 
Bad block table found at page 131008, version 0x01
Bad block table found at page 130944, version 0x01
7 cmdlinepart partitions found on MTD device atmel_nand
Creating 7 MTD partitions on "atmel_nand":
0x000000000000-0x000000040000 : "bootstrap"
0x000000040000-0x000000100000 : "uboot"
0x000000100000-0x000000140000 : "env_redundant"
0x000000140000-0x000000180000 : "env"
0x000000180000-0x000000200000 : "dtb"
0x000000200000-0x000000800000 : "kernel"
0x000000800000-0x000010000000 : "rootfs"
atmel_spi f0004000.spi: DMA TX channel not available, SPI unable to use DMA
atmel_spi f0004000.spi: Atmel SPI Controller using PIO only
m25p80 spi32766.0: unrecognized JEDEC id bytes: ff, ff, ff
atmel_spi f0004000.spi: Atmel SPI Controller version 0x213 at 0xf0004000 (irq 19)
libphy: Fixed MDIO Bus: probed
CAN device driver interface
at91_can f000c000.can: device registered (reg_base=e088d000, irq=42)
macb f0028000.ethernet: invalid hw address, using random
libphy: MACB_mii_bus: probed
Micrel KSZ9021 Gigabit PHY f0028000.etherne:07: attached PHY driver [Micrel KSZ9021 Gigabit PHY] (mii_bus:phy_addr=f0028000.etherne:07, irq=103)
macb f0028000.ethernet eth0: Cadence GEM rev 0x00020119 at 0xf0028000 irq 41 (06:84:d4:af:0c:ba)
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
ehci-atmel: EHCI Atmel driver
atmel-ehci 700000.ehci: EHCI Host Controller
atmel-ehci 700000.ehci: new USB bus registered, assigned bus number 1
atmel-ehci 700000.ehci: irq 44, io mem 0x00700000
atmel-ehci 700000.ehci: USB 2.0 started, EHCI 1.00
usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb1: Product: EHCI Host Controller
usb usb1: Manufacturer: Linux 4.9.52-linux4sam_5.7 ehci_hcd
usb usb1: SerialNumber: 700000.ehci
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 3 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-atmel: OHCI Atmel driver
at91_ohci 600000.ohci: failed to find sfr node
at91_ohci 600000.ohci: USB Host Controller
at91_ohci 600000.ohci: new USB bus registered, assigned bus number 2
at91_ohci 600000.ohci: irq 44, io mem 0x00600000
usb usb2: New USB device found, idVendor=1d6b, idProduct=0001
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: USB Host Controller
usb usb2: Manufacturer: Linux 4.9.52-linux4sam_5.7 ohci_hcd
usb usb2: SerialNumber: at91
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 3 ports detected
usbcore: registered new interface driver usb-storage
qt1070 1-001b: AT42QT1070 firmware version 15
input: AT42QT1070 QTouch Sensor as /devices/platform/ahb/ahb:apb/f0018000.i2c/i2c-1/1-001b/input/input0
rtc rtc0: alarm rollover not handled
rtc rtc0: invalid alarm value: 1900-1-1 0:0:0
at91_rtc fffffeb0.rtc: rtc core: registered fffffeb0.rtc as rtc0
at91_rtc fffffeb0.rtc: AT91 Real Time Clock driver.
i2c /dev entries driver
AT91: Starting after user reset
at91_wdt fffffe40.watchdog: watchdog is disabled
at91_wdt: probe of fffffe40.watchdog failed with error -22
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
atmel_mci f0000000.mmc: version: 0x505
atmel_mci f0000000.mmc: using dma0chan5 for DMA transfers
atmel_mci f0000000.mmc: Atmel MCI controller at 0xf0000000 irq 18, 1 slots
atmel_mci f8000000.mmc: version: 0x505
atmel_mci f8000000.mmc: using dma1chan0 for DMA transfers
atmel_mci f8000000.mmc: Atmel MCI controller at 0xf8000000 irq 25, 1 slots
sdhci-pltfm: SDHCI platform and OF driver helper
ledtrig-cpu: registered to indicate activity on CPUs
atmel_aes f8038000.aes: version: 0x135
atmel_aes f8038000.aes: Atmel AES - Using dma1chan1, dma1chan2 for DMA transfers
atmel_sha f8034000.sha: version: 0x410
atmel_sha f8034000.sha: using dma1chan3 for DMA transfers
atmel_sha f8034000.sha: Atmel SHA1/SHA256/SHA224/SHA384/SHA512
atmel_tdes f803c000.tdes: version: 0x701
atmel_tdes f803c000.tdes: using dma1chan4, dma1chan5 for DMA transfers
atmel_tdes f803c000.tdes: Atmel DES/TDES
iio iio:device0: Resolution used: 12 bits
input: at91_adc as /devices/platform/ahb/ahb:apb/f8018000.adc/input/input1
NET: Registered protocol family 10
sit: IPv6, IPv4 and MPLS over IPv4 tunneling driver
NET: Registered protocol family 17
can: controller area network core (rev 20120528 abi 9)
NET: Registered protocol family 29
can: raw protocol (rev 20120528)
can: broadcast manager protocol (rev 20161123 t)
can: netlink gateway (rev 20130117) max_hops=1
ubi0: default fastmap pool size: 95
ubi0: default fastmap WL pool size: 47
ubi0: attaching mtd6
random: fast init done
ubi0: scanning is finished
ubi0: attached mtd6 (name "rootfs", size 248 MiB)
ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
ubi0: good PEBs: 1980, bad PEBs: 4, corrupted PEBs: 0
ubi0: user volume: 1, internal volumes: 1, max. volumes count: 128
ubi0: max/mean erase counter: 1/0, WL threshold: 4096, image sequence number: 1541025795
ubi0: available PEBs: 0, total reserved PEBs: 1980, PEBs reserved for bad PEB handling: 36
at91_rtc fffffeb0.rtc: setting system clock to 2017-10-31 22:36:44 UTC (1509489404)
ALSA device list:
  No soundcards found.
ubi0: background thread "ubi_bgt0d" started, PID 99
UBIFS (ubi0:0): recovery needed
UBIFS (ubi0:0): recovery deferred
UBIFS (ubi0:0): UBIFS: mounted UBI device 0, volume 0, name "rootfs", R/O mode
UBIFS (ubi0:0): LEB size: 126976 bytes (124 KiB), min./max. I/O unit sizes: 2048 bytes/2048 bytes
UBIFS (ubi0:0): FS size: 244682752 bytes (233 MiB, 1927 LEBs), journal size 9023488 bytes (8 MiB, 72 LEBs)
UBIFS (ubi0:0): reserved for root: 0 bytes (0 KiB)
UBIFS (ubi0:0): media format: w4/r0 (latest is w4/r0), UUID 7A588A3E-5C95-4082-9C45-9A9465FEB9CB, small LPT model
VFS: Mounted root (ubifs filesystem) readonly on device 0:13.
devtmpfs: mounted
Freeing unused kernel memory: 1024K
random: crng init done

INIT: version 2.88 booting

Starting udev
/etc/rcS.d/S03systemd-udevd: line 76: /proc/sys/kernel/hotplug: No such file or directory
starting version 230
atmel_usba_udc 500000.gadget: MMIO registers at 0xf8030000 mapped at e0ac0000
atmel_usba_udc 500000.gadget: FIFO at 0x00500000 mapped at e2100000
0-001a supply DCVDD not found, using dummy regulator
0-001a supply DBVDD not found, using dummy regulator
0-001a supply AVDD not found, using dummy regulator
0-001a supply CPVDD not found, using dummy regulator
0-001a supply MICVDD not found, using dummy regulator
ov2640: probe of 1-0030 failed with error -16
wm8904 0-001a: revision A
atmel-wm8904-audio sound: wm8904-hifi <-> f0008000.ssc mapping ok
g_serial gadget: Gadget Serial v2.4
g_serial gadget: g_serial ready
UBIFS (ubi0:0): completing deferred recovery
UBIFS (ubi0:0): background thread "ubifs_bgt0_0" started, PID 182
UBIFS (ubi0:0): deferred recovery completed
ALSA: Restoring mixer settings...

No state is present for card SAMA5D3EK

/usr/sbin/alsactl: sysfs_init:48: sysfs path '/sys' is invalid



Found hardware: "wm8904___SAMA5D" "" "" "" ""

Hardware is initialized using a generic method

No state is present for card SAMA5D3EK


INIT: Entering runlevel: 5


Configuring network interfaces... IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
udhcpc (v1.24.1) started

Sending discover...

Sending discover...

Sending discover...

No lease, forking to background

done.

Starting system message bus: dbus.

Starting OpenBSD Secure Shell server: sshd

done.

cat: '/sys/class/drm/card0/*/modes': No such file or directory

Starting rpcbind daemon...done.

starting statd: done

Starting advanced power management daemon: No APM support in kernel

(failed.)

Starting atd: OK

Starting bluetooth

bluetoothd

exportfs: can't open /etc/exports for reading

NFS daemon support not enabled in kernel

Starting syslogd/klogd: done

 * Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon

[A[74G[ ok ]

Starting crond: OK

cat: '/sys/class/drm/card0/*/modes': No such file or directory



Starting Demo...



Poky (Yocto Project Reference Distro) 2.2.2 sama5d3xek /dev/ttyS0



sama5d3xek login: 
blue_z
Location: USA
Posts: 1564
Joined: Thu Apr 19, 2007 10:15 pm

Re: Sama5d3xek - Morty 2.2.2 Build - display fails

Thu Nov 02, 2017 9:27 pm

Kerberosity wrote:Each time, I can get the kernel, rootfs, etc. to boot and load but the screen always winds up with some weird line pattern, random popcorn static, or completely blank. There is absolutely no meaningful display data.
Sounds like the frame buffer memory (that was previously setup by U-Boot) is getting stepped on. Since that's not likely to happen with Linux, it usually means that there is no frame buffer device in your Linux kernel.

Kerberosity wrote:- Can anyone tell me where to go from here?
- Am I chasing the right problem or is lack of systemd a non-issue?
No, you're chasing the wrong problem(s).

Kerberosity wrote:- Have I misunderstood how this demo runs it's interface (i.e., weston)?
Yes, you misunderstand this demo software, since the name of the Atmel demo indicates it uses Qt5.
Weston is not involved at all.

Kerberosity wrote:- Does anyone see any additional messages that should I should start investigating deeper as potential root causes to my overall problem (the screen is not coming up)?
The kernel boot log has no output from the HLCDC driver, which is expected since the Linux4SAM maintainers for some reason removed the display driver from the Device Tree for the SAMA5D3x-EK boards after Linux version 4.1 or Linux4SAM release 5.2.
Without the HLCDC driver, there is no driver for the display hardware.
Consequently the DRM subsystem has no device for its output, and and DRM requests get rejected.

IOW you might have gotten closer to the root cause of the display issue if you had used a basic tool like modetest or simple utilities like fb-test and fbv instead trying to install an unnecessary display server .

Regards
Kerberosity
Posts: 2
Joined: Fri Oct 27, 2017 2:07 am

Re: Sama5d3xek - Morty 2.2.2 Build - display fails

Thu Nov 02, 2017 11:25 pm

blue_z,

Thanks! I needed some hints and you gave me a whole bunch of research topics. I found the display driver (weston) in the meta-atmel layer and assumed (erroneously, obviously) that that was how they were operating the display. In addition to working the problem, I will work on learning my diagnostic tools to avoid that in the future.

Cheers!

Return to “Linux”

Who is online

Users browsing this forum: No registered users and 1 guest