DRA71XEVM: earlyboot visionSDK noting show on the screen

fanok

Expert 2400 points

Part Number: DRA71XEVM

hi all experts,

i early boot the visionSDK ipu2, and normally it can run successly.

but sometime the screen show noting, i guess it is the DSS bug, becasue i run kmscube , show noting on the screen too.

the screen backlight of lp8860 is normal and i can control brightness by I2C.

then i excute debug_dss_clockdumps to get registers and clock of DSS, i compare them with normal log. i found nothing is different.

what's more, i excute "reboot" command, it also can not recover, only turn off the power then turn on it can recover.

log as follwing:

[root@x home]# ./debug_dss_clockdumps.sh

=====================DSS clock script===================
Dumps internal clocks and muxes of DSS

CTRL_CORE_DSS_PLL_CONTROL (0x4a002538) = 0x000002AE
video1 PLL : Enabled
video2 PLL : Disabled
HDMI PLL : Disabled
DSI1_A_CLK mux : DPLL HDMI
DSI1_B_CLK mux : DPLL video2
DSI1_C_CLK mux : DPLL Video1

DSS_CTRL (0x58000040) = 0x00090000
2: LCD1 clk switch : DSS clk
3: LCD2 clk switch : DSS clk
10: LCD3 clk switch : DSI1_C_CLK
1: func clk switch : DSS clk
13: DPI1 output : LCD1

DSS_STATUS (0x5800005C) = 0x02408A81

DSI_CLK_CTRL (0x58004054) = 0x80004001

CM_DSS_CLKSTCTRL (0x4A009100) = 0x00021F03

CM_DSS_DSS_CLKCTRL (0x4A009120) = 0x00003D02

========================================================
Register dump for DPLL video1
Warning: chip not recognized, running in safe mode (only platform-generic functions allowed).

|----------------------------|
| Address (hex) | Data (hex) |
|----------------------------|
| 0x58004300    | 0x00000018 |
| 0x58004304    | 0x00002683 |
| 0x58004308    | 0x00000000 |
| 0x5800430C    | 0x00EF78FE |
| 0x58004310    | 0x00E16108 |
| 0x58004314    | 0x00000007 |
| 0x58004318    | 0x00000000 |
| 0x5800431C    | 0x00000000 |
| 0x58004320    | 0x00000000 |
|----------------------------|

Details for DPLL video1
PLL status : Locked
M4 hsdiv(1) : Active
M5 hsdiv(2) : inactive
M6 hsdiv(3) : Active
M7 hsdiv(4) : inactive

PLL_REGM   = 1980
PLL_REGN   = 127
M4 DIV     = 7
M6 DIV     = 7
M7 DIV     = 0

Clock calculations (DPLL video1)
sysclk = 20000000
DCO clk = sysclk * 2 * REGM / (REGN + 1) = 618750000
M4clk (clkcout1) = DCO clk / (M4 DIV + 1) = 77343750
M6clk (clkcout3) = DCO clk / (M6 DIV + 1) = 77343750
M7clk (clkcout4) = DCO clk / (M7 DIV + 1) = 0

========================================================
Clock O/P of MUXes
./debug_dss_clockdumps.sh: line 309: arithmetic syntax error

how can i debug this issue?

best regards!

over 5 years ago

0 Subhajit Paul over 5 years ago

TI__Expert 7015 points

Can you provide the complete log from IPU2? The log should say whether anything like clock setup, DSS setup etc failed

0 fanok over 5 years ago in reply to Subhajit Paul

Expert 2400 points

hi Subhajit P,

it can not recurrence now, if occured again i will attach the log.

best regards!

0 fanok over 5 years ago in reply to Subhajit Paul

Expert 2400 points

hi Subhajit P,

i catch the normal log and fail log, and i compare them, but noting is different.

ok.log

1072.fail.log

why do "reboot" command can not recover, can you give me some clues from this phenomenon?

0 Subhajit Paul over 5 years ago in reply to fanok

TI__Expert 7015 points

Reboot command has never been tested to work in TI SDKs. We only support Power cycle

0 fanok over 5 years ago in reply to Subhajit Paul

Expert 2400 points

i don't know what's your mean?

it can do reboot on my board.

[root@x ~]#
[root@x ~]#
[root@x ~]# reboot
[root@x ~]# umount: devtmpfs busy - remounted read-only
swapoff: can't stat '–a': No such file or directory
The system is going down NOW!
Sent SIGTERM to all processes
Sent SIGKILL to all processes[ 19.602894] reboot: Restarting system

U-Boot SPL 2018.01-00430-ga502eda-dirty (Aug 23 2019 - 09:31:21)
DRA722-GP ES2.1
[TICK 00020] spl_board_init: i2c begin
[TICK 00025] spl_board_init: i2c end
[TICK 00045] Trying to boot from MMC1
spl: loading remote core image dra7-ipu2-fw.xem4
no pinctrl state for default mode
i2c_write: error waiting for addr ACK (status=0x116)
tps65903x: could not set LDO1 voltage.
[TICK 00064] spl_mmc_find_device: mmc_initialize cost 11
[TICK 00322] spl_mmc_find_device: mmc_initialize cost 0
[TICK 00326] spl_mmc_load_image: mmc_init cost 0
spl: mmc boot mode: fs
[TICK 00358] spl_mmc_do_fs_boot: load u-boot.img err 0 cost 25
[TICK 00363] spl_mmc_load_resource begin
SPL Load resource IN....

this is not important, the log is the same to the normal log, why noting show on the screen.?

best regards!!

0 Subhajit Paul over 5 years ago in reply to fanok

TI__Expert 7015 points

Since this is a DPI output, can you connect oscilloscope to the output pins and verify that the signals are coming out of the board and the signals are correct?

0 Subhajit Paul over 5 years ago in reply to Subhajit Paul

TI__Expert 7015 points

Fanok,

Is the issue resolved? I am closing the thread due to inactivity.

- Subhajit

0 fanok over 5 years ago in reply to Subhajit Paul

Expert 2400 points

hi Subhajit,

it is not resolved yet.

best regards!

0 Subhajit Paul over 5 years ago in reply to fanok

TI__Expert 7015 points

Fanok,

Did you check the output using a oscilloscope? Are the output signals correct?

- Subhajit

Processors

Processors forum

DRA71XEVM: earlyboot visionSDK noting show on the screen