How to use lvgl on pc386 BSP.

[Karel Gardas]

On 9/18/20 11:51 PM, Karel Gardas wrote:
> Whole demo output looks:
> 
> i386: isr=0 irr=1
> i386: isr=0 irr=1
> FB_VESA_RM frame buffer -- driver initializing..
> 
> 
> RTEMS LVGL HELLO WORLD
> 
> nexus0: <RTEMS Nexus device>
> pcib0 pcibus 0
> pci0: <PCI bus> on pcib0
> pci0: <bridge, HOST-PCI> at device 0.0 (no driver attached)
> pci0: <bridge, PCI-ISA> at device 1.0 (no driver attached)
> pci0: <mass storage, ATA> at device 1.1 (no driver attached)
> pci0: <bridge> at device 1.3 (no driver attached)
> pci0: <display, VGA> at device 2.0 (no driver attached)
> pci0: <network, ethernet> at device 3.0 (no driver attached)
> cpu0
> FB_VESA_RM open device
> The framebuffer device was opened successfully.
> FB_VESA_RM ioctl called, cmd=4602
> fbxres 1024, fbyres 768
> fbbpp 32
> FB_VESA_RM ioctl called, cmd=4600
> fbxres 1024, fbyres 768
> fbbpp 32
> 1024x768, 32bpp
> 3145728 screen size.
> Error: failed to map framebuffer device to memory: Not supported
> 
>

^ that was form Qemu, from my testing hw box it looks as follows. Sorry
for the dead Reaktek. Also it looks like VBE bios is kind of limited
since EDID recommended resolution is monitors native: 2560x1440, but
BIOS does not support it hence offers 1920x1440 as most close.

i386: isr=0 irr=1
FB_VESA_RM frame buffer -- driver initializing..

RTEMS LVGL HELLO WORLD

nexus0: <RTEMS Nexus device>
pcib0 pcibus 0
pci0: <PCI bus> on pcib0
pci0: <bridge, HOST-PCI> at device 0.0 (no driver attached)
pcib1: <PCI-PCI bridge> at device 1.0 on pci0
pci1: <PCI bus> on pcib1
pci1: <display, VGA> at device 5.0 (no driver attached)
pci1: <multimedia, HDA> at device 5.1 (no driver attached)
pcib2: <PCI-PCI bridge> irq 10 at device 10.0 on pci0
pci2: <PCI bus> on pcib2
re0: <RealTek 8168/8111 B/C/CP/D/DP/E/F/G PCIe Gigabit Ethernet> port
0xd800-0xd8ff mem 0xfdfff000-0xfdffffff,0xfdff8000-0xfdffbfff irq 10 at
device 0.0 on pci2
re0: Chip rev. 0x2c000000
re0: MAC rev. 0x00200000
re0: PHY write failed
re0: PHY write failed
re0: PHY read failed
re0: attaching PHYs failed
device_attach: re0 attach returned 6
pci0: <mass storage, SATA> at device 17.0 (no driver attached)
pci0: <serial bus, USB> at device 18.0 (no driver attached)
pci0: <serial bus, USB> at device 18.2 (no driver attached)
pci0: <serial bus, USB> at device 19.0 (no driver attached)
pci0: <serial bus, USB> at device 19.2 (no driver attached)
pci0: <multimedia, HDA> at device 20.2 (no driver attached)
pci0: <bridge, PCI-ISA> at device 20.3 (no driver attached)
pcib3: <PCI-PCI bridge> at device 20.4 on pci0
pci3: <PCI bus> on pcib3
re0: <RealTek 8169/8169S/8169SB(L)/8110S/8110SB(L) Gigabit Ethernet>
port 0xe800-0xe8ff mem 0xfebffc00-0xfebffcff irq 3 at device 5.0 on pci3
re0: Chip rev. 0x04000000
re0: MAC rev. 0x00000000
miibus0: <MII bus> on re0
rgephy0: <RTL8169S/8110S/8211 1000BASE-T media interface> PHY 1 on miibus0
rgephy0:  none, 10baseT, 10baseT-FDX, 10baseT-FDX-flow, 100baseTX,
100baseTX-FDX, 100baseTX-FDX-flow, 1000baseT, 1000baseT-master,
1000baseT-FDX, 1000baseT-FDX-master, 1000baseT-FDX-flow, 1w
info: re0: Using defaults for TSO: 65518/35/2048
info: re0: Ethernet address: 00:0e:2e:7b:da:0b
pci0: <serial bus, USB> at device 20.5 (no driver attached)
pci0: <serial bus, USB> at device 22.0 (no driver attached)
pci0: <serial bus, USB> at device 22.2 (no driver attached)
pci0: <bridge, HOST-PCI> at device 24.0 (no driver attached)
pci0: <bridge, HOST-PCI> at device 24.1 (no driver attached)
pci0: <bridge, HOST-PCI> at device 24.2 (no driver attached)
pci0: <bridge, HOST-PCI> at device 24.3 (no driver attached)
pci0: <bridge, HOST-PCIFB_VESA_RM open device
> at device 24.4 (no driver attached)
cpu0
TheFB_VESA_RM ioctl called, cmd=4602
fbxres 1920, fbyres 1440
fbbpp 32
FB_VESA_RM ioctl called, cmd=4600
fbxres 1920, fbyres 1440
fbbpp 32
 framebuffer device was opened successfully.
1920x1440, 32bpp
11059200 screen size.
Error: failed to map framebuffer device to memory: Not supported

*** FATAL ***
fatal source: 9 (RTEMS_FATAL_SOURCE_EXCEPTION)
----------------------------------------------------------
Exception 13 caught at PC ffffffff by thread 167837697
----------------------------------------------------------
Processor execution context at time of the fault was  :
----------------------------------------------------------
 EAX = 0        EBX = 0 ECX = 3662e4    EDX = 0
 ESI = 0        EDI = 3662bc    EBP = ff        ESP = 3af0a8
----------------------------------------------------------
Error code pushed by processor itself (if not 0) = 0
----------------------------------------------------------
Call Stack Trace of EIP:
0xef7eef7e 0xffffffff
*** FATAL ***
fatal source: 9 (RTEMS_FATAL_SOURCE_EXCEPTION)
----------------------------------------------------------
Exception 13 caught at PC 2ae863 by thread 167837697
----------------------------------------------------------
Processor execution context at time of the fault was  :
----------------------------------------------------------
 EAX = b        EBX = ffffffff  ECX = 339fee    EDX = 0
 ESI = 3        EDI = 2adc40    EBP = 3aef58    ESP = 3aef1c
----------------------------------------------------------
Error code pushed by processor itself (if not 0) = 0
----------------------------------------------------------
Call Stack Trace of EIP:
0x002906f8 0x002add03 0x002a7a4e 0x002ae4d9
0x002ae2f8
RTEMS version: 6.0.0.97559a7077ee0996012bcbc6952bbfb96923d6ae
RTEMS tools: 10.2.1 20200904 (RTEMS 6, RSB
a81a237f3e2318d88a16b31aadb82333498e06fd, Newlib a0d7982)
executing thread ID: 0x08a010001
executing thread name: UI1