Home Live Radio Podcast Live TV Vodcast Forum Files Login Register :     Contact : 
 
Forum index Forum: Device: SkyTC - KMP510 (Envivo Otek Xenta Arnova) Topic: Otek IPTV510 stalling at boot screen, 1.52 firmware Last replied to: January 30, 2017, 11:19 am Back to post view
AuthorPostOptions
Posted by 6J6A Message # 1     Posted at October 18, 2016, 2:51 am,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 32 posts
Registration date: June 24, 2012
Status: Offline

Hi William,

One of my Otek IPTV510's (SKYTC) is suddenly crashing on boot and I hope you might be able to help.

It has had LL 1.52 firmware installed for some time. It was unplugged for about 6 months and now when I turn it on, it attempts to boot past the OTEK screen, but halts on the blue loading screen with all the SKYTC icons.

I have tried inserting an SD card with the llfirstaid package and it still does not boot past the intro screens. Ive also tried reloading the firmware on sdcard but it still does not boot past the intro screens and into the listenlive loader.

Is there any buttons I need to hold down on boot or should the card just be recognised and boot?

Any help would be appreciated.

Regards,
Matthew.
 
Posted by penbex Message # 2     Posted at October 18, 2016, 10:33 am,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 2216 posts
Registration date: May 21, 2009
Status: Offline

If it hangs at the boot logo it usually means that the OS is damaged. The memory management on the SkyTC systems is pretty poor. 

Try to boot in recovery mode by holding the two outer buttons and inserting the power cable.

The first aid kit can only be used if the recovery had been installed when the system was working. 
The kit just installs a recovery image and makes it possible to reflash the regular OS.

The normal firmware update method is just replacing some selected files and needs a working device.


 
Posted by 6J6A Message # 3     Posted at October 18, 2016, 11:11 am,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 32 posts
Registration date: June 24, 2012
Status: Offline

I've tried the two outer buttons and power cable in but it still does not make it past the blue icons boot screen.

Tried this with both the recovery on an sd and the firmware on another sd but it just wont load the loader and stalls.

Is there anyway you know of to fix this? Perhaps a console cable flash or something? Anything would be a help.

Cheers,
Matthew.
 
Posted by 6J6A Message # 4     Posted at October 20, 2016, 10:57 am,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 32 posts
Registration date: June 24, 2012
Status: Offline

So i'm gussing there isnt much I can do then.... bricked unit.
 
Posted by penbex Message # 5     Posted at October 20, 2016, 10:50 pm,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 2216 posts
Registration date: May 21, 2009
Status: Offline

Open the device and check the PCB.. 
 
Posted by 6J6A Message # 6     Posted at October 20, 2016, 11:27 pm,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 32 posts
Registration date: June 24, 2012
Status: Offline

What am I checking for exactly?
 
Posted by penbex Message # 7     Posted at October 21, 2016, 10:14 am,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 2216 posts
Registration date: May 21, 2009
Status: Offline

there is a serial interface.. some minor issues can be solved there.
When it comes to a crash of the OS partition it will be hard because there are hardly any images available

Note that this port works on the otek.. 
Owners of an Arnova are in bad luck.. most of the firmwares have the serial port disabled.

 
Posted by 6J6A Message # 8     Posted at October 24, 2016, 7:26 am,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 32 posts
Registration date: June 24, 2012
Status: Offline

Here are some pics of the mainboard and suspected serial port J4

https://postimg.org/image/6coa28rsj
https://postimg.org/image/y1fini46r
https://postimg.org/image/62lcwn2k3
https://postimg.org/image/4otq1c3ar

The board is marked as KMP510 MAIN VER 1.1

So it looks like J4 is the serial port that I need to hook up to. Do you happen to know which pins are which (txd, rxd, 3.3v, gnd) ??

So once I get it hooked up to serial, What exactly do you need? copy and paste of bootup etc?

Really appreciate your help William
 
Posted by 6J6A Message # 9     Posted at November 7, 2016, 7:12 am,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 32 posts
Registration date: June 24, 2012
Status: Offline

Done a serial console dump, email sent.
 
Posted by 6J6A Message # 10     Posted at November 20, 2016, 12:32 pm,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 32 posts
Registration date: June 24, 2012
Status: Offline

Hi William,

Just wonderng if you have had a chance to look over the otek console dump I emailed you?

Cheers.
 
Posted by 6J6A Message # 11     Posted at December 29, 2016, 5:45 am,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 32 posts
Registration date: June 24, 2012
Status: Offline

Hi William,
Still have not heard back from you via email, so here is another copy of the otek bootloader dump from the failed IPTV510. Can you please let me know if this is fixable?

Thanks.
Matthew.

¦57600

NAND Secondary Program Loader

Starting U-Boot ...


U-Boot 1.1.6 (Jul  7 2010 - 10:39:48)

Board: Ingenic CETUS (CPU Speed 378 MHz)
DRAM:  64 MB
Flash:  0 kB
NAND:1024 MiB
Build: 100707-0, based on patch-090903
Support custom u-boot logo in NAND
*** Warning - bad CRC or NAND, using default environment

MAC address = 00:0A:EB:AA:74:34
System enter standby mode


NAND Secondary Program Loader

Starting U-Boot ...


U-Boot 1.1.6 (Jul  7 2010 - 10:39:48)

Board: Ingenic CETUS (CPU Speed 378 MHz)
DRAM:  64 MB
Flash:  0 kB
NAND:1024 MiB
Build: 100707-0, based on patch-090903
Support custom u-boot logo in NAND
*** Warning - bad CRC or NAND, using default environment

MAC address = 00:0A:EB:AA:74:34
Powwer on by on/off key
png = 0x4000, size = 0x10D4
Show custom logo...
In:    serial
Out:   lcd
Err:   lcd
Hit any key to stop autoboot:  0
Select noraml kernel and rootfs...

NAND read: device 0 offset 0x400000, size 0x300000
 3145728 bytes read: OK
## Booting image at 80600000 ...
   Image Name:   Linux-2.6.24.3
   Image Type:   MIPS Linux Kernel Image (gzip compressed)
   Data Size:    2249150 Bytes =  2.1 MB
   Load Address: 80010000
   Entry Point:  8028f290
   Verifying Checksum ... OK
   Uncompressing Kernel Image ... OK

Starting kernel ...

Linux version 2.6.24.3 (colman@colinux) (gcc version 4.1.2) #1251 PREEMPT Tue Au                            g 17 02:02:05 UTC 2010
SDRAM: Bus Width = 32, CAS Width = 9, RAS Width = 13, # of Bank = 4, Total Size                             = 64 Mbyte
CPU revision is: 2ed0024f (Ingenic JZRISC)
CPU clock: 378MHz, System clock: 126MHz, Peripheral clock: 126MHz, Memory clock:                             126MHz
JZ4750D CETUS board setup
Determined physical RAM map:
 memory: 04000000 @ 00000000 (usable)
Zone PFN ranges:
  Normal          0 ->    16384
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
    0:        0 ->    16384
Built 1 zonelists in Zone order, mobility grouping off.  Total pages: 16256
Kernel command line: console=ttyS1,57600n8 ip=off rootfstype=yaffs2 root=/dev/mt                            dblock5 rw build=100707-0
Primary instruction cache 16kB, VIPT, 4-way, linesize 32 bytes.
Primary data cache 16kB, 4-way, VIPT, no aliases, linesize 32 bytes
Synthesized clear page handler (25 instructions).
Synthesized copy page handler (44 instructions).
Synthesized TLB refill handler (20 instructions).
Synthesized TLB load handler fastpath (32 instructions).
Synthesized TLB store handler fastpath (32 instructions).
Synthesized TLB modify handler fastpath (31 instructions).
PID hash table entries: 256 (order: 8, 1024 bytes)
Console: colour dummy device 80x25
console [ttyS1] enabled
Dentry cache hash table entries: 8192 (order: 3, 32768 bytes)
Inode-cache hash table entries: 4096 (order: 2, 16384 bytes)
Memory: 60628k/65536k available (2577k kernel code, 4852k reserved, 1406k data,                             140k init, 0k highmem)
Mount-cache hash table entries: 512
net_namespace: 64 bytes
NET: Registered protocol family 16
Linux Plug and Play Support v0.97 (c) Adam Belay
SCSI subsystem initialized
NET: Registered protocol family 2
Time: jz_clocksource clocksource has been installed.
IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
TCP established hash table entries: 2048 (order: 2, 16384 bytes)
TCP bind hash table entries: 2048 (order: 1, 8192 bytes)
TCP: Hash tables configured (established 2048 bind 2048)
TCP reno registered
Total 16MB memory at 0x3000000 was reserved for IPU
Total 0MB memory1 at 0x467000 was reserved for IPU
Power Management for JZ
yaffs Aug 16 2010 09:51:23 Installing.
io scheduler noop registered
io scheduler anticipatory registered (default)
io scheduler deadline registered
io scheduler cfq registered
LCDC: PixClock:6406779
LCDC: PixClock:6406779
fb0: jz-lcd frame buffer device, using 2048K of video memory
JzSOC onchip RTC installed !!!
JzSOC: char device family.
Jz generic touch screen driver registered
JZ4740 SAR-ADC driver registered
JZ UDC hotplug driver registered
Virtual Driver of TCSM registered
Serial: 8250/16550 driver $Revision: 1.5 $ 4 ports, IRQ sharing disabled
serial8250: ttyS0 at MMIO 0x0 (irq = 9) is a 16550A
¦¦?¦¦¦250: ttyS1 at MMIO 0x0 (irq = 8) is a 16550A
serial8250: ttyS2 at MMIO 0x0 (irq = 7) is a 16550A
loop: module loaded
SKY_IO: driver ver 1.0.0
SKY_IO: misc dev got minor 63
Driver 'sd' needs updating - please use bus_type methods
JZ NAND init: DMA mode, using DMA buffer in upper layer,  4bit BCH.
NAND device: master_id: 0xecd3
NAND device: writesize: 0x800, erasesize: 0x40000, oobsize: 64, busw: 0
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)
NAND device: Manufacturer ID: 0xec, Chip ID: 0xd3 (Samsung NAND 1GiB 3,3V 8-bit)                             planenum:2
nand_scan_ident(): Bad block flag page in block: 127.
Nand using two-plane mode, and resized to writesize:4096 oobsize:128 blocksize:0                            x80000
Scanning device for bad blocks
Allocate 0x40000 bytes for jz_mtdblock9 at address:0x804c0000.
Creating 10 MTD partitions on "NAND 1GiB 3,3V 8-bit":
0x000000000-0x000400000 : "NAND BOOT partition" "dma_mode" "jz_mtdblock_invalid"
0x000400000-0x000800000 : "NAND KERNEL partition" "dma_mode" "jz_mtdblock_invali                            d"
0x000800000-0x000c00000 : "Failsafe KERNEL partition" "dma_mode" "jz_mtdblock_in                            valid"
0x000c00000-0x001000000 : "System DATA partition" "dma_mode" "jz_mtdblock_invali                            d"
0x001000000-0x009000000 : "ALT FS partition" "dma_mode" "jz_mtdblock_invalid"
0x009000000-0x019000000 : "NAND ROOTFS partition" "dma_mode" "jz_mtdblock_invali                            d"
0x019000000-0x019c00000 : "NAND DATA1 partition" "dma_mode" "jz_mtdblock_invalid                            "
JZ4750_LCD: Show custom animated logo
0x019c00000-0x01bc00000 : "NAND DATA2 partition" "dma_mode" "jz_mtdblock_invalid                            "
0x01bc00000-0x01dc00000 : "NAND DATA3 partition" "dma_mode" "jz_mtdblock_invalid                            "
0x01dc00000-0x040000000 : "NAND VFAT partition" "dma_mode" "jz_mtdblock_valid"
jz_i2c jz_i2c.0: Soft i2c bus driver.
EzI2CKEY: driver ver 3.0.4
EzI2CKEY: Push button keyboard detected
EzI2CKEY: misc dev got minor 62
power cable insert!
FM_RDA580X: driver ver 1.0.0
FM_RDA580X: fm attached at 0x10
FM_RDA580X: misc dev got minor 61
FM_RDA580X: volume = 30
JzSOC Watchdog Timer: timer margin 60 sec
JZ SD/MMC card driver registered
register codec 801fa710
JZ I2S OSS audio driver initialized
TCP cubic registered
NET: Registered protocol family 1
NET: Registered protocol family 17
ieee80211: 802.11 data/management/control stack, git-1.1.13
ieee80211: Copyright (C) 2004-2005 Intel Corporation <jketreno@linux.intel.com>
yaffs: dev is 32505861 name is "mtdblock5"
yaffs: Attempting MTD mount on 31.5, "mtdblock5"
VFS: Mounted root (yaffs2 filesystem).
Freeing unused kernel memory: 140k freed
Algorithmics/MIPS FPU Emulator v1.5
init started: BusyBox v1.8.2 (2008-01-09 19:22:01 CST)
starting pid 153, tty '': '/etc/init.d/rcS'
Segmentation fault
Starting udevd ...
Segmentation fault
rtc_wjpk: module license 'unspecified' taints kernel.
rtc_wjpk installed
athspi_jz4755_hcd version: 2.2.0.78-110104, DMA Mode
Colman: op_clock = 33000000
Ar6k SPI use TX/RX DMA channel: 6/7
Youli::HcdInitialize: set starup clock [24000000]
AR6k spi clk request = 24000000 Hz, actual = 23625000 Hz
AR6k spi clk request = 33000000 Hz, actual = 31500000 Hz
ar6000: no version for "stack_force_interrupt_clear" found: kernel tainted.
ar6000 version: 2.2.0.78-101112
Normal WIFI mode.
Device: c00b5a28
ar6000_available
Firmware mode set
 BMI enabled
ar6000_avail: name=eth0 hifdevice=0xc00c98b8, dev=0x81790000 (0), ar=0x81790360
old options [0] old sleep [29]
use internal clock
AR6000: download fake eeprom
enable_SI
eeprom_type_detect: ERROR : address type was wrongly set
eeprom_ar6000_transfer file offset opsition: 0h
eeprom_ar6000_transfer: length=768
eeprom_ar6000_transfer try to open file /system/wifi/softmac
eeprom_ar6000_transfer: file /system/wifi/softmac filp_open error
disable_SI
AR6000: BMISetAppStart
AR6000: enable HI_OPTION_TIMER_WAR
AR6000: firmware_transfer
firmware_transfer: Enter, filename=/system/wifi/athwlan.bin.z77
firmware_transfer file offset opsition: 0h
firmware_transfer: length=98324, address=0x502070
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=8192, org_len=8192
firmware_transfer: BMILZData: len=20, org_len=20
firmware_transfer: Enter, filename=/system/wifi/data.patch.hw2_0.bin
firmware_transfer file offset opsition: 0h
firmware_transfer: length=1336, address=0x52d6c8
ar6000_init() Got WMI @ 0x817f1000.
Colman: Re-enable IRQ
Youli::ar6000_init: wait wmi_ready event to trigger host app area

Youli::ar6000_ready_event: use wmi_ready event trigger setting host app
mac address = 00:0a:eb:aa:74:34
AR6000 Reg Code = 0x80000024
starting pid 199, tty '': '/bin/sh'
# Segmentation fault
killall: udhcpc: no process killed
Segmentation fault
Segmentation fault
Segmentation fault
e2fsck 1.41.14 (22-Dec-2010)
Segmentation fault
e2fsck 1.41.14 (22-Dec-2010)
Segmentation fault
mke2fs 1.40.4 (31-Dec-2007)
Could not stat /dev/mmcblk0p7 --- No such file or directory

The device apparently does not exist; did you specify it correctly?
mke2fs 1.40.4 (31-Dec-2007)
Could not stat /dev/mmcblk0p8 --- No such file or directory

The device apparently does not exist; did you specify it correctly?
mkfs.vfat 2.2 (06 Jul 1999)
/dev/mmcblk0p1: No such file or directory
fbset: can't open '/dev/fb0': No such file or directory
Model 1 detected
./fail


 
Posted by 6J6A Message # 12     Posted at January 25, 2017, 9:12 am,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 32 posts
Registration date: June 24, 2012
Status: Offline

William are you still active on these forums?
 
Posted by penbex Message # 13     Posted at January 30, 2017, 11:19 am,     subject: Otek IPTV510 stalling at boot screen, 1.52 firmware  
Messages: 2216 posts
Registration date: May 21, 2009
Status: Offline

Yes, but device rescue is not something I actively do anymore. 
It usually costs days to fix a single device.. 
I rather spend time on things like development..

Anyway.. 
The log is fairly clear, 2 issues:
>nand_scan_ident(): Bad block flag page in block: 127.
The flash memory is damaged as bad blocks have been detected.
In some cases it works if you mark the bad blocks and rewrite a proper image (as far as these are actually available) to the flash.
BUT....

># Segmentation fault
This is usually a sign of bad RAM chips and often means: throw away the device.
If this issue persists then it is game over. 
If you have the tools to replace the ram chips you still would have issues to find the Elpida chips that are no longer produced..
Although Elpida was taken over by Micron after a bankruptcy, the actual chips have not been produced anymore.