Hi,
I am working on DM814x EVM board, and software is based on EZSDK-5.04.00.11. After enabling display splash logo on u-boot, Linux cannot boot up. But Linux can boot up if disabling display logo on -u-boot.
Following is linux booting log when failed:
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 : 0xcc79e369
AW Phy Addr : 0x58088000 Data : 0xeafffffe
BW Phy Addr : 0x58098000 Data : 0x9325a280
AW Phy Addr : 0x58098000 Data : 0xeafffffe
BW Phy Addr : 0x[ 3.030000] smsc95xx 1-1.1:1.0: eth2: register 'smsc95xx' at usb-musb-hdrc.0-1.1, smsc95xx USB 2.0 Ethernet, 00:0d:5d:00:00:12
48180c10 Data : 0x00000003
AW Phy Addr : 0x48180c10 Data : 0x00000000
Phy Addr : 0x48180c14 Data : 0x00000007
PRCM for IVHD0 is Done Successfully
PRCM Initialization completed
[ 3.500000] SysLink version : 2.20.02.20
[ 3.500000] SysLink module created on Date:May 2 2013 Time:16:44:29
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
[ 9.350000] VPSS_FVID2: contrl event 0x10040019 timeout
[ 9.360000] VPSS_DCTRL: failed to set venc mdoe.
[ 9.360000] VPSS_DCTRL: Failed to set venc mode.
[ 11.370000] VPSS_FVID2: delete time out
[ 11.370000] VPSS_DCTRL: failed to delete DC fvid2 handle.
[ 11.380000] VPSS_CORE : failed to init display controller.
[ 13.380000] VPSS_FVID2: delete time out
[ 13.390000] VPSS_SYSTEM: failed to delete handle
[ 13.390000] vpss: probe of vpss failed with error -110
[ 13.400000] VPSS_CORE : failed to register ti81xx-vpss driver
modprobe: can't load module vpss (kernel/drivers/video/ti81xx/vpss/vpss.ko): No such device
Can anyone help on this issue?
Regards,
Yong Zou
