Ник:
Пароль:

Контакты

E-mail: info@starterkit.ru
тел.: +7 922 680-21-73
тел.: +7 922 680-21-74
Телеграм: t.me/starterkit_ru
Партнеры:
otladka.com.ua - г.Киев

Способы оплаты

User Info


Добро пожаловать,
Guest

Регистрация или входРегистрация или вход
Потеряли пароль?Потеряли пароль?

Ник:
Пароль:

ПользователейПользователей:2
Поисковых ботовПоисковых ботов:3
ГостейГостей:1

ОбновитьПодробнееВсегоВсего:6
Форум » starterkit.ru » Отладочные платы » SK-DM8148
dm8148+SK-MI0430FT-Plug
danilsl
Добавлено 22.04.2013 09:44
0
Сообщение: 1
danilsl
1

Пункты: 4194
Регистрация: 08.12.2010
Пол: Мужчина
Здравствуйте
подключил к плате экранчик SK-MI0430FT-Plug. Загрузился с нанда (в нём ничего не менял), ввёл config_lcd 480x272, перезагрузился. Экран просто светится белым цветом, никакой картинки не выдаёт. В /etc/inittab запущен getty на tty1, так что я думаю что хотябы голый курсор моргать должен был бы. Соответственно в моей rootfs, загружаемой с флешки такая же ситуация.
Вот лог загрузки:


U-Boot 2010.06 (Apr 19 2013 - 11:51:59)

TI8148-GP rev 3.0

ARM clk: 1000MHz
DDR clk: 400MHz

DRAM: 1 GiB
MMC: OMAP SD/MMC: 0
Using default environment

The 2nd stage U-Boot will now be auto-loaded
Please do not interrupt the countdown till TI8148_EVM prompt if 2nd stage is already flashed
Hit any key to stop autoboot: 0
reading u-boot.bin

212064 bytes read
## Starting application at 0x80800000 ...


U-Boot 2010.06 (Apr 19 2013 - 11:53:02)

TI8148-GP rev 3.0

ARM clk: 1000MHz
DDR clk: 400MHz

I2C: ready
DRAM: 1 GiB
NAND: HW ECC BCH8 Selected
256 MiB
MMC: OMAP SD/MMC: 0
.:;rrr;;.
,5#@@@@#####@@@@@@#2,
,A@@@hi;;;r5;;;;r;rrSG@@@A,
r@@#i;:;s222hG;rrsrrrrrr;ri#@@r
:@@hr:r;SG3ssrr2r;rrsrsrsrsrr;rh@@:
B@H;;rr;3Hs;rrr;sr;;rrsrsrsrsrsr;;H@B
@@s:rrs;5#;;rrrr;r#@H:;;rrsrsrsrsrr:s@@
@@;;srs&X#9;r;r;;,2@@@rrr:;;rrsrsrsrr;;@@
@@;;rrsrrs@MB#@@@@@###@@@@@@#rsrsrsrsrr;;@@
G@r;rrsrsr;#X;SX25Ss#@@#M@#9H9rrsrsrsrsrs;r@G
@9:srsrsrs;2@;:;;:.X@@@@@H::;rrsrsrsrsrsrr:3@
X@;rrsrsrsrr;XAi;;:&@@#@Bs:rrsrsrsrsrsrsrsrr;@X
@#;rsrsrsrsrr;r2ir@@@###::rrsrsrsrsrsrsrsrsr:@@
@A:rrsrsrsrr;:2@29@@M@@@;:;rrrrsrsrsrsrsrsrs;H@
@&;rsrsrsrr;A@@@@@@###@@@s::;:;;rrsrsrsrsrsr;G@
@#:rrsrsrsr;G@5Hr25@@@#@@@#9XG9s:rrrrsrsrsrs:#@
M@;rsrsrsrs;r@&#;::S@@@@@@@M@@@@Grr:;rsrsrsr;@#
:@s;rsrsrsrr:M#Msrr;;&#@@@@@@@@@@H@@5;rsrsr;s@,
@@:rrsrsrsr;S@rrrsr;:;r3MH@@#@M5,S@@irrsrr:@@
@A:rrsrsrsrrrrrsrsrrr;::;@##@r:;rH@h;srr:H@
;@9:rrsrsrsrrrsrsrsrsr;,S@Hi@i:;s;MX;rr:h@;
r@B:rrrrsrsrsrsrsrr;;sA@#i,i@h;r;S5;r:H@r
,@@r;rrrsrsrsrsrr;2BM3r:;r:G@:rrr;;r@@,
B@Mr;rrrrsrsrsr@@S;;;rrr:5M;rr;rM@H
.@@@i;;rrrrsrs2i;rrrrr;r@M:;i@@@.
.A@@#5r;;;r;;;rrr;r:r#AsM@@H.
;&@@@@MhXS5i5SX9B@@@@G;
:ihM#@@@@@##hs,

Net: Detected MACID:84:7e:40:87:82:8
cpsw
Hit any key to stop autoboot: 0
SK-DM8148#run nand_boot

NAND read: device 0 offset 0xa0000, size 0x440000
4456448 bytes read: OK
## Booting kernel from Legacy Image at 81000000 ...
Image Name: Linux-2.6.37
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2945372 Bytes = 2.8 MiB
Load Address: 80008000
Entry Point: 80008000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.
Linux version 2.6.37 (user@DM8148-bld) (gcc version 4.3.3 (Sourcery G++ Lite 2009q1-203) ) #104 Mon Apr 8 21:48:15 UTC 3
CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=10c53c7f
CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
Machine: ti8148evm
reserved size = 52428800 at 0x0
FB: Reserving 52428800 bytes SDRAM for VRAM
Memory policy: ECC disabled, Data cache writeback
OMAP chip is TI8148 3.0
SRAM: Mapped pa 0x402f1000 to va 0xfe400000 size: 0xf000
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 79656
Kernel command line: console=ttyO0,115200n8 ubi.mtd=5 root=ubi0:nandfs rw rootfstype=ubifs mem=364M@0x80000000 324M@0x9d
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: 314MB = 314MB total
Memory: 311948k/311948k available, 60788k reserved, 0K highmem
Virtual kernel memory layout:
vector : 0xffff0000 - 0xffff1000 ( 4 kB)
fixmap : 0xfff00000 - 0xfffe0000 ( 896 kB)
DMA : 0xffc00000 - 0xffe00000 ( 2 MB)
vmalloc : 0xd7000000 - 0xf8000000 ( 528 MB)
lowmem : 0xc0000000 - 0xd6c00000 ( 364 MB)
pkmap : 0xbfe00000 - 0xc0000000 ( 2 MB)
modules : 0xbf000000 - 0xbfe00000 ( 14 MB)
.init : 0xc0008000 - 0xc0039000 ( 196 kB)
.text : 0xc0039000 - 0xc058c000 (5452 kB)
.data : 0xc058c000 - 0xc05d8400 ( 305 kB)
SLUB: Genslabs=11, HWalign=64, Order=0-3, MinObjects=0, CPUs=1, Nodes=1
NR_IRQS:407
IRQ: Found an INTC at 0xfa200000 (revision 5.0) with 128 interrupts
Total of 128 interrupts on 1 active controller
GPMC revision 6.0
Trying to install interrupt handler for IRQ400
Trying to install interrupt handler for IRQ401
Trying to install interrupt handler for IRQ402
Trying to install interrupt handler for IRQ403
Trying to install interrupt handler for IRQ404
Trying to install interrupt handler for IRQ405
Trying to install interrupt handler for IRQ406
Trying to install type control for IRQ407
Trying to set irq flags for IRQ407
OMAP clockevent source: GPTIMER1 at 20000000 Hz
Console: colour dummy device 80x30
Calibrating delay loop... 999.42 BogoMIPS (lpj=4997120)
pid_max: default: 32768 minimum: 301
Security Framework initialized
Mount-cache hash table entries: 512
CPU: Testing write buffer coherency: ok
devtmpfs: initialized
omap_voltage_early_init: voltage driver support not added
regulator: core version 0.5
regulator: dummy:
NET: Registered protocol family 16
omap_voltage_domain_lookup: Voltage driver init not yet happened.Faulting!
omap_voltage_add_dev: VDD specified does not exist!
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
OMAP GPIO hardware version 0.1
omap_mux_init: Add partition: #1: core, flags: 4
Debugfs: Only enabling/disabling deep sleep and wakeup timer is supported now
registered ti81xx_vpss device
registered ti81xx_vidout device
registered ti81xx on-chip HDMI device
registered ti81xx_fb device
registered ti81xx_vin device
ti81xx_pcie: Invoking PCI BIOS...
ti81xx_pcie: Setting up Host Controller...
ti81xx_pcie: Register base mapped @0xd7020000
ti81xx_pcie: Starting PCI scan...
PCI: bus0: Fast back to back transfers enabled
bio: create slab <bio-0> at 0
vgaarb: loaded
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
USBSS revision 4ea2080b
registerd cppi-dma Intr @ IRQ 17
Cppi41 Init Done
omap_i2c omap_i2c.1: bus 1 rev4.0 at 100 kHz
Advanced Linux Sound Architecture Driver Version 1.0.23.
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource gp timer
musb-hdrc: version 6.0, host, debug=0
musb-hdrc musb-hdrc.0: dma type: dma-cppi41
MUSB controller-0 revision 4ea20800
musb-hdrc musb-hdrc.0: MUSB HDRC host driver
musb-hdrc musb-hdrc.0: new USB bus registered, assigned bus number 1
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: MUSB HDRC host driver
usb usb1: Manufacturer: Linux 2.6.37 musb-hcd
usb usb1: SerialNumber: musb-hdrc.0
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 1 port detected
musb-hdrc musb-hdrc.0: USB Host mode controller at d701e000 using DMA, IRQ 18
musb-hdrc musb-hdrc.1: dma type: dma-cppi41
MUSB controller-1 revision 4ea20800
musb-hdrc musb-hdrc.1: MUSB HDRC host driver
musb-hdrc musb-hdrc.1: new USB bus registered, assigned bus number 2
usb usb2: New USB device found, idVendor=1d6b, idProduct=0002
usb usb2: New USB device strings: Mfr=3, Product=2, SerialNumber=1
usb usb2: Product: MUSB HDRC host driver
usb usb2: Manufacturer: Linux 2.6.37 musb-hcd
usb usb2: SerialNumber: musb-hdrc.1
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 1 port detected
musb-hdrc musb-hdrc.1: USB Host mode controller at d7026800 using DMA, IRQ 19
NET: Registered protocol family 2
IP route cache hash table entries: 4096 (order: 2, 16384 bytes)
TCP established hash table entries: 16384 (order: 5, 131072 bytes)
TCP bind hash table entries: 16384 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 16384 bind 16384)
TCP reno registered
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 udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NetWinder Floating Point Emulator V0.97 (double precision)
PMU: registered new PMU device of type 0
omap-iommu omap-iommu.0: ducati registered
omap-iommu omap-iommu.1: sys registered
JFFS2 version 2.2. (NAND) &#65533;© 2001-2006 Red Hat, Inc.
msgmni has been set to 609
io scheduler noop registered
io scheduler deadline registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing enabled
omap_uart.0: ttyO0 at MMIO 0x48020000 (irq = 72) is a OMAP UART0
console [ttyO0] enabled
omap_uart.1: ttyO1 at MMIO 0x48022000 (irq = 73) is a OMAP UART1
omap_uart.2: ttyO2 at MMIO 0x48024000 (irq = 74) is a OMAP UART2
omap_uart.3: ttyO3 at MMIO 0x481a6000 (irq = 44) is a OMAP UART3
omap_uart.4: ttyO4 at MMIO 0x481a8000 (irq = 45) is a OMAP UART4
omap_uart.5: ttyO5 at MMIO 0x481aa000 (irq = 46) is a OMAP UART5
brd: module loaded
loop: module loaded
ahci ahci.0: forcing PORTS_IMPL to 0x1
ahci ahci.0: AHCI 0001.0300 32 slots 1 ports 3 Gbps 0x1 impl platform mode
ahci ahci.0: flags: ncq sntf pm led clo only pmp pio slum part ccc apst
scsi0 : ahci_platform
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a150fff] port 0x100 irq 16
omap2-nand driver initializing
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung )
Creating 6 MTD partitions on "omap2-nand.0":
0x000000000000-0x000000020000 : "U-Boot-min"
0x000000020000-0x000000080000 : "U-Boot"
0x000000080000-0x0000000a0000 : "U-Boot Env"
0x0000000a0000-0x0000004e0000 : "Kernel"
0x0000004e0000-0x000001000000 : "Safe kernel (initramfs)"
0x000001000000-0x000010000000 : "File System"
UBI: attaching mtd5 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 129024 bytes
UBI: smallest flash I/O unit: 2048
UBI: sub-page size: 512
UBI: VID header offset: 512 (aligned 512)
UBI: data offset: 2048
usb 1-1: new high speed USB device using musb-hdrc and address 2
ata1: SATA link down (SStatus 0 SControl 300)
usb 1-1: New USB device found, idVendor=046d, idProduct=09c1
usb 1-1: New USB device strings: Mfr=0, Product=0, SerialNumber=0
UBI: max. sequence number: 861
UBI: attached mtd5 to ubi0
UBI: MTD device name: "File System"
UBI: MTD device size: 240 MiB
UBI: number of good PEBs: 1916
UBI: number of bad PEBs: 4
UBI: number of corrupted PEBs: 0
UBI: max. allowed volumes: 128
UBI: wear-leveling threshold: 4096
UBI: number of internal volumes: 1
UBI: number of user volumes: 1
UBI: available PEBs: 267
UBI: total number of reserved PEBs: 1649
UBI: number of PEBs reserved for bad PEB handling: 19
UBI: max/mean erase counter: 1/0
UBI: image sequence number: 1411589531
UBI: background thread "ubi_bgt0d" started, PID 47
davinci_mdio davinci_mdio.0: davinci mdio revision 1.6
davinci_mdio davinci_mdio.0: detected phy mask fffffff5
davinci_mdio.0: probed
davinci_mdio davinci_mdio.0: phy[1]: device 0:01, driver RTL821x Gigabit Ethernet
davinci_mdio davinci_mdio.0: phy[3]: device 0:03, driver RTL821x Gigabit Ethernet
CAN device driver interface
CAN bus driver for Bosch D_CAN controller 1.0
d_can d_can.0: d_can device registered (irq=52, irq_obj=53)
usbcore: registered new interface driver cdc_ether
usbcore: registered new interface driver dm9601
usbcore: registered new interface driver cdc_acm
cdc_acm: v0.26:USB Abstract Control Model driver for USB modems and ISDN adapters
usbcore: registered new interface driver uas
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mice: PS/2 mouse device common for all mice
ads7846 spi1.0: touchscreen, irq 207
input: ADS7846 Touchscreen as /devices/platform/omap2_mcspi.1/spi1.0/input/input0
qt602240_ts 1-004a: __qt602240_read_reg: i2c transfer failed
qt602240_ts: probe of 1-004a failed with error -5
omap_rtc omap_rtc: rtc core: registered omap_rtc as rtc0
rtc-pcf8563 1-0051: chip found, driver version 0.4.3
rtc-pcf8563 1-0051: rtc core: registered rtc-pcf8563 as rtc1
i2c /dev entries driver
Linux video capture interface: v2.00
uvcvideo: Found UVC 1.00 device <unnamed> (046d:09c1)
input: UVC Camera (046d:09c1) as /devices/platform/omap/ti81xx-usbss/musb-hdrc.0/usb1/1-1/1-1:1.0/input/input1
usbcore: registered new interface driver uvcvideo
USB Video Class driver (v1.0.0)
OMAP Watchdog Timer Rev 0x00: initial timeout 60 sec
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
notify_init : notify drivercreated for remote proc id 2 at physical Address 0xbf900000
usbcore: registered new interface driver snd-usb-audio
AIC23 Audio Codec 0.1
asoc: tlv320aic23-hifi <-> davinci-mcasp.0 mapping ok
asoc: HDMI-DAI-CODEC <-> hdmi-dai mapping ok
ALSA device list:
#0: USB Device 0x46d:0x9c1 at usb-musb-hdrc.0-1, high speed
#1: TI81XX EVM
TCP cubic registered
NET: Registered protocol family 17
can: controller area network core (rev 20090105 abi 8)
NET: Registered protocol family 29
can: raw protocol (rev 20090105)
can: broadcast manager protocol (rev 20090105 t)
lib80211: common routines for IEEE802.11 drivers
Registering the dns_resolver key type
VFP support v0.3: implementor 41 architecture 3 part 30 variant c rev 3
omap_voltage_late_init: Voltage driver support not added
Power Management for TI81XX.
Detected MACID=84:7e:40:87:82:8
Detected MACID=84:7e:40:87:82:9
mmc1: host does not support reading read-only switch. assuming write-enable.
rtc-pcf8563 1-0051: low voltage detected, date/time is not reliable.
rtc-pcf8563 1-0051: setting system clock to 2000-01-01 00:03:32 UTC (946685012)
mmc1: new high speed SDHC card at address b368
mmcblk0: mmc1:b368 USD 3.75 GiB
mmcblk0: p1 p2
UBIFS: mounted UBI device 0, volume 0, name "nandfs"
UBIFS: file system size: 208373760 bytes (203490 KiB, 198 MiB, 1615 LEBs)
UBIFS: journal size: 10450944 bytes (10206 KiB, 9 MiB, 81 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 4952683 bytes (4836 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:14.
devtmpfs: mounted
Freeing init memory: 196K
Init: mkdir: can't create directory '/mnt/mmcblk0p1': File exists
mkdir: can't create directory '/mnt/mmcblk0p2': File exists
EXT3-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)
EXT3-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)
EXT2-fs (mmcblk0p2): error: couldn't mount because of unsupported optional features (240)
mount: mounting /dev/mmcblk0p2 on /mnt/mmcblk0p2 failed: Invalid argument
rm: can't remove '/bin/ip': No such file or directory
Starting logging: OK
Initializing random number generator... done.
Starting network...

CPSW phy found : id is : 0x1cc912
udhcpc (v1.21.0) started
Sending discover...
PHY: 0:03 - Link is Up - 100/Full
Sending discover...
Sending select for 192.168.30.17...
Lease of 192.168.30.17 obtained, lease time 600
deleting routers
route: SIOCDELRT: No such process
adding dns 192.168.10.254

CPSW phy found : id is : 0x1cc912
RTNETLINK answers: Network is unreachable
d_can d_can.0: can0: setting CAN BT = 0x1c09
Starting dropbear sshd: NET: Registered protocol family 10
ADDRCONF(NETDEV_UP): eth1: link is not ready
OK
Starting sshd: OK
Starting wi-fi network ...
Error for wireless request "Set Mode" (8B06) :
SET failed on device wlan0 ; No such device.
Error for wireless request "Set ESSID" (8B1A) :
SET failed on device wlan0 ; No such device.
ifconfig: SIOCSIFADDR: No such device
Loading HDVICP2 Firmware
DM814X prcm_config_app version: 2.0.0.1
Doing PRCM settings...
PRCM for IVHD0 is in Progress, Please wait.....
BW Phy Addr : 0x48180600 Data : 0x00000001
AW Phy Addr : 0x48180600 Data : 0x00000002
Phy Addr : 0x48180c04 Data : 0x00000037
BW Phy Addr : 0x48180620 Data : 0x00070000
AW Phy Addr : 0x48180620 Data : 0x00050002
BW Phy Addr : 0x48180624 Data : 0x00030000
AW Phy Addr : 0x48180624 Data : 0x00010002
Phy Addr : 0x48180600 Data : 0x00000102
BW Phy Addr : 0x48180c10 Data : 0x00000007
AW Phy Addr : 0x48180c10 Data : 0x00000003
Phy Addr : 0x48180c14 Data : 0x00000004
BW Phy Addr : 0x58088000 Data : 0xeafffffe
AW Phy Addr : 0x58088000 Data : 0xeafffffe
BW Phy Addr : 0x58098000 Data : 0xeafffffe
AW Phy Addr : 0x58098000 Data : 0xeafffffe
BW Phy Addr : 0x48180c10 Data : 0x00000003
AW Phy Addr : 0x48180c10 Data : 0x00000000
Phy Addr : 0x48180c14 Data : 0x00000007
PRCM for IVHD0 is Done Successfully
PRCM Initialization completed
SysLink version : 2.20.02.20
SysLink module created on Date:Mar 29 2013 Time:15:54:10
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments===
<Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop> to start/stop the firmware
===Optional arguments===
-mmap input memory map bin file name
-i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
Firmware Loader debugging not configured
Default FL_DEBUG: warning
Allowed FL_DEBUG levels: error, warning, info, debug, log
MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
FIRMWARE: 1 start Successful
Loading HDVPSS Firmware
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments===
<Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop> to start/stop the firmware
===Optional arguments===
-mmap input memory map bin file name
-i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
Firmware Loader debugging not configured
Default FL_DEBUG: warning
Allowed FL_DEBUG levels: error, warning, info, debug, log
MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
FIRMWARE: 2 start Successful
VPSS_FVID2: M3 firmware version 0x1000145 is newer,driver may not work properly.
Configuring fb0 to LCD
HDMI W1 rev 4.0
HDMI CEC Spec version 1.2
I2C No Ack

Console: switching to colour frame buffer device 240x67


Welcome to SK-DM8148 development board!

SK-DM8148 login:


На самом экране несколько моделей написано, так что фотку прикрепляю. И да, подключен к X4
Спуститься к концу Подняться к началу
Персональная информация
Pavel Ivanchenko
Добавлено 22.04.2013 10:11 Редактировалось 22.04.2013 10:11 Сообщение: 2
Pavel Ivanchenko
Admin
4.39

Пункты: 91424
Регистрация: 24.03.2009
Пол: Мужчина
Цитата
Видеосистема штатного ядра настроена:
/dev/fb0 – HDMI выход, разрешение 1920х1080, консоль tty1
/dev/fb1 – LCD выход (X4), разрешение 800х480, сенсорный ввод
1) убедитесь, что файл загрузки фирмварей действительно был заменен работой скрипта config_lcd, экран должен стать "черным" именно после запуска скрипта загрузки фирмвари (практически перед самым логином)
2) никакой консоли (или "картинки") на LCD не будет, ts_lib в штатной корневой ФС настроен на fb1
Спуститься к концу Подняться к началу
Персональная информация
danilsl
Добавлено 22.04.2013 10:23 Сообщение: 3
danilsl
1

Пункты: 4194
Регистрация: 08.12.2010
Пол: Мужчина
# cat /etc/init.d/S70load-hd-firmware
#!/bin/sh
#
# manage HDVICP2 and HDVPSS Engine firmware

PATH=$PATH:/usr/share/ti/ti-media-controller-utils
HDVICP2_ID=1
HDVPSS_ID=2

configure_lcd()
{
echo "Configuring fb0 to LCD"

#invert of LCD clock
echo 40 > /sys/class/gpio/export
echo out > /sys/class/gpio/gpio40/direction
echo 1 > /sys/class/gpio/gpio40/value

# echo 1:dvo2 > /sys/devices/platform/vpss/graphics0/nodes
# echo 0 > /sys/devices/platform/vpss/display1/enabled
# echo 33500,800/164/89/10,480/10/23/10,1 > /sys/devices/platform/vpss/display1/timings
# echo triplediscrete,rgb888 > /sys/devices/platform/vpss/display1/output
# echo 1 > /sys/devices/platform/vpss/display1/enabled
# fbset -xres 800 -yres 480 -vxres 800 -vyres 480

}


case "$1" in
start)
echo "Loading HDVICP2 Firmware"
prcm_config_app s

# modprobe syslink
insmod /lib/modules/2.6.37/kernel/drivers/dsp/syslink.ko

until [[ -e /dev/syslinkipc_ProcMgr && -e /dev/syslinkipc_ClientNotifyMgr ]]
do
sleep 1
done
firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvicp.xem3 start
echo "Loading HDVPSS Firmware"
firmware_loader $HDVPSS_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvpss.xem3 start
modprobe vpss sbufaddr=0xBFB00000 mode=hdmi:1080p-60 mode=dvo2:480x272@60 i2c_mode=1
modprobe ti81xxfb vram=0:24M,1:16M,2:6M
configure_lcd
modprobe ti81xxhdmi
modprobe fbcon
;;
stop)
echo "Unloading HDVICP2 Firmware"
firmware_loader $HDVICP2_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvicp.xem3 stop
echo "Unloading HDVPSS Firmware"
rmmod fbcon
rmmod ti81xxhdmi
rmmod ti81xxfb
rmmod vpss
firmware_loader $HDVPSS_ID /usr/share/ti/ti-media-controller-utils/dm814x_hdvpss.xem3 stop
rm /tmp/firmware.$HDVPSS_ID
rmmod syslink
;;
*)
echo "Usage: /etc/init.d/load-hd-firmware.sh {start|stop}"
exit 1
;;
esac

exit 0
#


Вроде на месте всё.
Спуститься к концу Подняться к началу
Персональная информация
danilsl
Добавлено 22.04.2013 10:26 Сообщение: 4
danilsl
1

Пункты: 4194
Регистрация: 08.12.2010
Пол: Мужчина
Смущают вот эти надписи при старте


FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments===
<Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop> to start/stop the firmware
===Optional arguments===
-mmap input memory map bin file name
-i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
Firmware Loader debugging not configured
Default FL_DEBUG: warning
Allowed FL_DEBUG levels: error, warning, info, debug, log
MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
FIRMWARE: 1 start Successful
Loading HDVPSS Firmware
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Usage : firmware_loader <Processor Id> <Location of Firmware> <start|stop> [-mmap <memory_map_file>] [-i2c <0|1>]
===Mandatory arguments===
<Processor Id> 0: DSP, 1: Video-M3, 2: Vpss-M3
<Location of Firmware> firmware binary file
<start|stop> to start/stop the firmware
===Optional arguments===
-mmap input memory map bin file name
-i2c 0: i2c init not done by M3, 1(default): i2c init done by M3
FIRMWARE: isI2cInitRequiredOnM3: 1
FIRMWARE: Default memory configuration is used
Firmware Loader debugging not configured
Default FL_DEBUG: warning
Allowed FL_DEBUG levels: error, warning, info, debug, log
MemCfg: DCMM (Dynamically Configurable Memory Map) Version : 2.1.2.1
FIRMWARE: 2 start Successful
VPSS_FVID2: M3 firmware version 0x1000145 is newer,driver may not work properly.
Configuring fb0 to LCD
HDMI W1 rev 4.0
HDMI CEC Spec version 1.2
I2C No Ack

Спуститься к концу Подняться к началу
Персональная информация
Pavel Ivanchenko
Добавлено 22.04.2013 11:06 Редактировалось 22.04.2013 11:07 Сообщение: 5
Pavel Ivanchenko
Admin
4.39

Пункты: 91424
Регистрация: 24.03.2009
Пол: Мужчина
Цитата
FIRMWARE: I2cInit will be done by M3
FIRMWARE: Memory map bin file not passed
Ничего страшного.

Цитата
HDMI CEC Spec version 1.2
I2C No Ack
Дык подключите HDMI оно и исчезнет.

Цитата
... подключил к плате экранчик SK-MI0430FT-Plug ...
Я сейчас посмотрел по счетам, ваша организация не покупала SK-MI0430FT-Plug, покупали SK-WF43BTIBED0TP-Plug, естественно он работать не будет.
Откровенно говоря такое отношение к делу раздражает
Спуститься к концу Подняться к началу
Персональная информация
danilsl
Добавлено 22.04.2013 11:14 Сообщение: 6
danilsl
1

Пункты: 4194
Регистрация: 08.12.2010
Пол: Мужчина
В самом низу именно эта модель написана, однако вверху справа ещё список моделей, одна из которых SK-MI0430FT-Plug. Вот я и решил что это он. Зачем тогда писать на плате лишние названия?
Спуститься к концу Подняться к началу
Персональная информация
Pavel Ivanchenko
Добавлено 22.04.2013 11:18 Сообщение: 7
Pavel Ivanchenko
Admin
4.39

Пункты: 91424
Регистрация: 24.03.2009
Пол: Мужчина
Затем, что печатная плата одна на 4 изделия ...
Разбирайтесь сами, я более не участник.
Спуститься к концу Подняться к началу
Персональная информация
Jury093
Добавлено 10.05.2013 22:58 Сообщение: 8
Jury093
4.5

Пункты: 54233
Регистрация: 25.05.2009
Пол: Мужчина
Из: Санкт-Петербург
запустил графику на VOUT1..
так работает упоминавшийся MIO430FT(480х272):

title

а вот так 7"(800х480):

title

дебьян 6.0 - консоль, картинки, видео (без ускорителя) - все работает..
Код
root@dm8148:~# fbset
mode "480x272-49"
# D: 9.000 MHz, H: 15.254 kHz, V: 48.892 Hz
geometry 480 272 480 272 32
timings 111111 60 40 20 10 10 10
rgba 8/16,8/8,8/0,8/24
endmode


тач не проверял - должен работать и так..

На любой вопрос есть любой ответ.
Спуститься к концу Подняться к началу
Персональная информация
Форум » starterkit.ru » Отладочные платы » SK-DM8148