[Vizio M60-D1] stuck at logo and rebooting. Serial dump is attached. NNo ENV device f

[oscarchentwn]

Hi There,

Does anyone know what part is broken? Is that the kernel image (mmc) broken?

Here is the serial dump from UART.

Start Soc Driver load
160+0 records in
160+0 records out
160 bytes transferred in 0.002 secs (80000 bytes/sec)
This is NOT 2UMAC DDR 088 board.
This is 2.5G DDR board, can support EDR.
This board can support HDR.
mipsflag in uBoot is same: 0x80000005
This is SX7+FRCX board.
Load 2.5G Driver setting
[ 3.247647] PLF-CPU[914]: (File:/common/hudson_slaves/sith/workspace/P111_TV103_Sprint6_SX7A_Build/DCP_SYS/HAL_SX6/Kernel_Driver/cpu_comm/cpu_comm.c Line:1613 Routine:cpu_comm_init) - smp axi bus cpu_comm_init() - Enter. PhyMemAddr=ea00000, ShMemAddrBase=0, ShMemSize=23068672
[ 3.272941] phy:0x1001404c
[ 3.276818] phy:0x10014034
[ 3.279544] phy:0x10014038
[ 3.282246] phy:0x100140e0
[ 3.284945] phy:0x100140e4
[ 3.287642] phy:0x10014044
[ 3.290422] phy:0x10014048
[ 3.293123] phy:0x100140f0
[ 3.295821] phy:0x100140f4
[ 3.298909] PLF-CPU[914]: (File:/common/hudson_slaves/sith/workspace/P111_TV103_Sprint6_SX7A_Build/DCP_SYS/HAL_SX6/Kernel_Driver/cpu_comm/comm_request.c Line:943 Routine:InitCommMem) - ShMemAddrBase:cd000000, ShMemSize:1600000, pComm->pSharMem:cd0298b0, size:15d674f, ShMemAddr:ea00000, pAddr:cd0298b0
[ 3.325782] PLF-CPU[914]: (File:/common/hudson_slaves/sith/workspace/P111_TV103_Sprint6_SX7A_Build/DCP_SYS/HAL_SX6/Kernel_Driver/cpu_comm/trid_smm.c Line:739 Routine:Trid_SMM_Init) - Add heap:0ea2a000, pWholeBlock:cd0298b0, size:15d674f, heapAddr:0ea2a000
[ 3.368484] ************svp_init: Kmalloc size: ge2ddev: 216
[ 3.374140] <1> hidtvPro_check_chip_type, data_word 9700
[ 3.379460] ge2d: HiDTVPRO_SX7 chip found
[ 3.383465] ge2d:====== svp var (xres 1920, yres 1080, primary size: 0xfd2000 linelength 7680)======
[ 3.392591] ge2d:====== Allocate Memory for ge2d Driver from 0x29900000 to 0x338fefff ======
[ 3.403179] ge2d.drv ge2d: init done Ver: 2.0
[ 3.403358] ge2d.drv It successfully create GE2D DISP CHANNEL!
[ 3.418294] <1> FBinit avail 0x9fff000
[ 3.423052] ge2d.drv ge2d is ready now!
[ 3.448913] Mali: Mali memory settings (dedicated: 0x0B700000@0x33900000)
[ 3.477887] Mali: Mali device driver loaded
[ 3.498152] PMan protection driver init, print_limits: 5000.
[ 3.503845] <1> register PMan HUB0 IRQ (0).
[ 3.508049] <1> register PMan HUB1 IRQ (0).
[ 3.512238] <1> register PMan HUB1 IRQ (0).
[ 3.532150] i2chtv_init enter pi2c_dev_class bf08e150
[ 3.537674] i2chtv_init enter pi2c_dev_class bf08e244
[ 3.543239] i2chtv_init enter pi2c_dev_class bf08e338
[ 3.548706] i2chtv_init enter pi2c_dev_class bf08e42c
[ 3.601297] [TRACE UNINITIALZED]: demux_module_init success
[ 3.653671] karmorgate: armorgate_init
[ 3.672941] hidtvreg: init done Ver: 2.0
Finish Soc Driver load
[ 3.703938] EXT4-fs (mmcblk0p8): mounted filesystem with ordered data mode. Opts: barrier=1
[ 13.758045] mmc0: Timeout waiting for hardware interrupt.
[ 13.767825] mmcblk0: error -110 transferring data, sector 994984, nr 32, cmd response 0x900, card status 0x900
[ 13.777833] mmcblk0: retrying using single block read
[ 13.786683]
[ 13.786683] ==========pmandrv: Here comes PMan Hub interrupt (53).
[ 13.794329] pman-hub: Group[18] Invalid Access Count:1
[ 13.799458] pman-hub: BLOCKED_CMD 0xa700: (Data/Write cmd)
[ 13.804933] pman-hub: BLOCKED_CMD_ID 0x7
[ 13.808845] pman-hub: BLOCKED_CMD_BS 0x3
[ 13.812759] pman-hub: BLOCKED_CMD_LINES 0x0
[ 13.816931] pman-hub: BLOCKED_CMD_STRIDE 0x0
[ 13.821190] pman-hub: BLOCKED_CMD_ADDR 0x987fd000
[ 13.825883] pman-hub: BLOCKED_SEC_GROUP 0x12
[ 13.830139] pman-hub: BLOCKED_REGION 0x8
[ 13.834052] pman-hub: INT_STATUS 0x40000
[ 13.837966] pman-hub: INT_ENABLE 0xffe7ffff
[ 13.842143] pman-hub: (!)PMAN error for group[18: SDIO_1/2/SPI] tries to access address [0x987fd000] -- transaction volatile in region [3 ](-1 means default region), DDR[1]!
[ 13.857583] pman-hub: (*)You can check regions from "/proc/pman_hub".
[ 13.857583]
[ 17.918115] No ENV device found!
[ 17.921339] Enumerate ENV device failed!!
[ 23.798021] mmc0: Timeout waiting for hardware interrupt.
[ 23.805695] mmcblk0: error -110 transferring data, sector 995008, nr 8, cmd response 0x900, card status 0x0
[ 23.815440] end_request: I/O error, dev mmcblk0, sector 995008
[ 23.821808]
[ 23.821808] ==========pmandrv: Here comes PMan Hub interrupt (53).
[ 23.829453] pman-hub: Group[18] Invalid Access Count:2
[ 23.834580] pman-hub: BLOCKED_CMD 0xa700: (Data/Write cmd)
[ 23.840053] pman-hub: BLOCKED_CMD_ID 0x7
[ 23.843965] pman-hub: BLOCKED_CMD_BS 0x3
[ 23.847879] pman-hub: BLOCKED_CMD_LINES 0x0
[ 23.852051] pman-hub: BLOCKED_CMD_STRIDE 0x0
[ 23.856309] pman-hub: BLOCKED_CMD_ADDR 0x987fd200
[ 23.861001] pman-hub: BLOCKED_SEC_GROUP 0x12
[ 23.865261] pman-hub: BLOCKED_REGION 0x8
[ 23.869174] pman-hub: INT_STATUS 0x40000
[ 23.873088] pman-hub: INT_ENABLE 0xffe7ffff
[ 23.877264] pman-hub: (!)PMAN error for group[18: SDIO_1/2/SPI] tries to access address [0x987fd200] -- transaction volatile in region [3 ](-1 means default region), DDR[1]!
[ 23.892704] pman-hub: (*)You can check regions from "/proc/pman_hub".
[ 23.892704]
[ 33.838041] mmc0: Timeout waiting for hardware interrupt.
[ 33.845697] mmcblk0: error -110 transferring data, sector 995009, nr 7, cmd response 0x900, card status 0x0
[ 33.855440] end_request: I/O error, dev mmcblk0, sector 995009

[oscarchentwn]

Re: [Vizio M60-D1] stuck at logo and rebooting. Serial dump is attached. NNo ENV devi

Before above step to get serial dump, I checked EEPROM, U202 which is able to be read/write. So EEPROM should be good and working.

[CapLeaker]

Re: [Vizio M60-D1] stuck at logo and rebooting. Serial dump is attached. NNo ENV devi

try flashing the firmware.

[Nick's Tvs]

Re: [Vizio M60-D1] stuck at logo and rebooting. Serial dump is attached. NNo ENV devi

Always worth a shot as well is to heat up the large BGA chips under the big heatsink with hot air and see if that allows the cycling to stop.
We often see BGA issues with these boards.

[oscarchentwn]

Re: [Vizio M60-D1] stuck at logo and rebooting. Serial dump is attached. NNo ENV devi

try flashing the firmware.

I am still trying to figure out how to flash it. 9.0.5.2.utv is the current firmware what I download from Vizio website. I am not sure if I can just flash this file to or there is something I have to extract from *.utv.

I haven't find information how to read or extract *.utv file.

[oscarchentwn]

Re: [Vizio M60-D1] stuck at logo and rebooting. Serial dump is attached. NNo ENV devi

Always worth a shot as well is to heat up the large BGA chips under the big heatsink with hot air and see if that allows the cycling to stop.
We often see BGA issues with these boards.

Thanks for sharing. I can try this with heatgun.