Tm-2T OE Won't Boot After Deep Sleep?

[gatster]

Only had my receiver since Friday and haven't had much opportunity to play with it since initial setup. This evening I found a 'deep sleep' option in the Web UI which I enabled, however now the box won't start, just shows the OPENVIX screen then displays "Booting...." on the display, but doesn't do anything. Any suggestions?

[judge]

How long has it been sitting like that? does it show any % booted?
Try power switch on back & let us know if it boots then.

[gatster]

How long has it been sitting like that? does it show any % booted?
Try power switch on back & let us know if it boots then.

It was like that for about an hour, it never got off the "OPENVIX: all your support needs at world-of-satellite.com" screen, it never proceeeded to the % loading sceen. I powered off and unplugged, waited a while and the same thing happened.

I decided to flash it with the latest image from here, which seemed to complete successfully but very quickly, but it's now back to the same issue.

[judge]

are you sure it flashed correctly so? my TM2T takes 3 to 4 minutes to flash.
Did you hit the OK button on the box when it asked you to?

[Larry-G]

also make certain you have no other USB devices plugged in while flashing the receiver that the one with the image on.

[gatster]

Further update - tried reflashing (reformatted USB, only one usb device plugged in, followed all instructions) and it just sits on 'Updating' (36 minutes on the last attempt).

[judge]

36 minutes & still showing updating on your TV screen?
What image version are you trying to flash & what's the latest bootloader you used?

[gatster]

Used the following:

TM2T-CFE-20121031.zip
openvix-3.0.574-tmtwin_usb.zip

Just trying it again now.

[gatster]

Ok. TBH I think it's buggered. It just sits on 'Updating for as long as you let it. I tried following this suggestion (http://www.world-of-satellite.com/showthread.php?24308-Tm-2t&p=180832&viewfull=1#post180832) as well but no joy.

I then tried installing 4D with the same 'Updating' result, so no joy there either. Back to trying the latest VIX image. I've also tried numerous different USB keys to rule that out. I noticed that irrespective of the USB key used, on the two that have activity indicator lights, they only indicate activity for a very brief time after the update process starts, but I thought this may be down to the small image sizes?

Going to bed now so will probably power it off and unplug it for the night before having one more go in the morning.

[Larry-G]

one thing you could try tomorrow is try putting it into none linux mode and see if it boots up then, if it does you can try flashing again and try putting it back into linux mode.

It's not as complicated as it sounds but i'm not near a receiver at present to be able to talk you through the process.

[gatster]

I found this on another forum, doesn't seem to work though:

Closed source to Linux
To exit closed source mode and into Linux mode. Switch off at the rear and then you power it up, repeatedly press the EXIT button on the receiver for about 15 seconds.

Linux to Closed source
To get 'out' of linux mode and see original menus. Switch off at the rear and then you power it up, repeatedly press the MENU button on the receiver for about 15 seconds.

[abu baniaz]

Have you tried the following?

Flash the bootloader separately
Switch off. Do not restart.
Delete bootloader file on USB and add image.
Power on and flash the image.
Restart
Press EXIT continuoulsy for approx 15 seconds.

[gatster]

Have you tried the following?

Flash the bootloader separately
Switch off. Do not restart.
Delete bootloader file on USB and add image.
Power on and flash the image.
Restart
Press EXIT continuoulsy for approx 15 seconds.

Tried that exactly as described - just hangs on 'Updating...' again (8 minutes so far). Same as last night :mad: To me this looks like a H/W flash problem caused by the unit not being able to handle deep standby for whatever reason.

[abu baniaz]

Unless one of the the more knowledgeable people have a better suggestion, the only thing I can suggest is to flash the bootloader using the serial method and go from there. Might be an idea to contact your retailer first though.

You could also ring TM and seek their advice.

[gatster]

All attempts failed so contacted WoS who put me in contact with TM direct. Fantastically helpful, they were even onto the developers in Korea but we still couldn't get it to boot. New box is on it's way to me as it seems to be a bug, so for now I can strongly recommend that anyone who has one, don't put it into deep standby from the Web UI!!! :eek:

[manicscrewdriver]

Now thats the sort of customer service i remember from Technomate when my old TMS-1500CI failed. Sorted very quickly. Hopefully TM will be able to identify the issue quite quickly :D

[Larry-G]

Now thats the sort of customer service i remember from Technomate when my old TMS-1500CI failed. Sorted very quickly. Hopefully TM will be able to identify the issue quite quickly :D

yup, and i know TM get a lot of flack from certain sections of the interweb but they always go above and beyond when a user gets in contact with a problem unit, same as WoS always does when a user has a problem and contacts him. Cant get any better customer service than that if you ask me.

[Sicilian]

All attempts failed so contacted WoS who put me in contact with TM direct. Fantastically helpful, they were even onto the developers in Korea but we still couldn't get it to boot. New box is on it's way to me as it seems to be a bug, so for now I can strongly recommend that anyone who has one, don't put it into deep standby from the Web UI!!! :eek:

Think you may have been unlucky, I've just tested a number of times deep standby using WEBIF and Remote, had zero issues waking up the unit.

[manicscrewdriver]

WOS deliverd my VU+ in person to the hotel i was staying at when i was working in London . If that isn't customer service i don't know what is :D

I also forgot to mention that TM replaced the remote on my old TM500 free of charge after they decided to change the remote code. Rang them up and emailed a copy of the receipt, and the new remote arrived the next day.

Saying that though it was a pre production run TM500 unit as it only had the one scart connector, when they went into production they had two :cool:

I've never had any issues with Technomate, i have had a lot of their boxes in the past and think they are OK, if i'm totally honest.

Nano

[Larry-G]

Think you may have been unlucky, I've just tested a number of times deep standby using WEBIF and Remote, had zero issues waking up the unit.

I can confirm that i use deepstandby on both my TM Twin and TM 2T on a almost daily basis and have never had a issue with it.

[Stanman]

Same here on the tm2t, goes in to DS every night and never had an issue

[judge]

Just tested mine here, using WEBIF to set Deep StandBy.
Box came out of it no problem.

[mbull2012]

Guys, How do you set the Box to go into DS every night Auto, i just press the power button every night, but leaves the light on at the front, am sure thats not meant to be on when it's in DS
Cheers

[Stanman]

menu>timers>powertimers

You can set them to wake up, standby and deepstandy.

Can add a one off timer or repeat

[preetkk]

Having same problem!

Box has problems is if i power mains off and power back on!

[preetkk]

Here's my telnet log on bootup


I2C_4397_Init : Done
************************************************** *
Found splash image - Width = 720 Height = 576
************************************************** *

searching images on "usbdisk0:update/tm2toe/cfe/" ...
I2C_4397_Init : Done
************************************************** *
Found splash image - Width = 720 Height = 576
************************************************** *
Loader:elf Filesys:raw Dev:nandflash0.nkernel File: Options:rootfstype=jffs2 root=/dev/mtdblock4 rw panic=1
Loading: 0x80001000/7759232 0x80767580/145024 Entry address is 0x805d4090
TP1 Entry Address at 0x80000ffc = 805d4090
Starting program at 0x805d4090

Linux version 3.5.3 (vix@buildpc) (gcc version 4.6.4 20120303 (prerelease) (GCC) ) #1 SMP Sun Jul 7 22:02:34 BST 2013
Fetching vars from bootloader... found 7 vars.
Options: sata=1 enet=1 emac_1=1 no_mdio=0 docsis=0 pci=1 smp=1 moca=0 usb=1
Using 256 MB + 128 MB RAM (from CFE)
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Determined physical RAM map:
memory: 10000000 @ 00000000 (usable)
Not Found hwtypes
bmem: adding 112 MB RESERVED region at 144 MB (0x07000000@0x09000000)
Zone ranges:
Normal [mem 0x00000000-0x0fffffff]
Movable zone start for each node
Early memory node ranges
node 0: [mem 0x00000000-0x0fffffff]
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
PERCPU: Embedded 7 pages/cpu @81203000 s5504 r8192 d14976 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: bmem=112M ubi.mtd=4 root=ubi0:rootfs rootfstype=ubifs rw console=ttyS0,115200n8 rootflags=sync slab_max_order=0 hwtypenum=0
PID hash table entries: 1024 (order: 0, 4096 bytes)
Dentry cache hash table entries: 32768 (order: 5, 131072 bytes)
Inode-cache hash table entries: 16384 (order: 4, 65536 bytes)
__ex_table already sorted, skipping sort
Memory: 137408k/262144k available (6030k kernel code, 124736k reserved, 1303k data, 244k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Detected MIPS clock frequency: 404 MHz (202.499 MHz counter)
Console: colour dummy device 80x25
Calibrating delay loop... 403.45 BogoMIPS (lpj=201728)
pid_max: default: 32768 minimum: 301
Mount-cache hash table entries: 512
SMP: Booting CPU1...
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
SMP: CPU1 is running
Brought up 2 CPUs
devtmpfs: initialized
NET: Registered protocol family 16
PCI2.3->SDRAM window: 512 MB
bio: create slab <bio-0> at 0
SCSI subsystem initialized
usbcore: registered new interface driver usbfs
usbcore: registered new interface driver hub
usbcore: registered new device driver usb
Advanced Linux Sound Architecture Driver Version 1.0.25.
PCI host bridge to bus 0000:00
pci_bus 0000:00: root bus resource [mem 0xd0000000-0xefffffff]
pci_bus 0000:00: root bus resource [io 0x0400-0x83ff]
PCI host bridge to bus 0000:01
pci_bus 0000:01: root bus resource [mem 0x10510000-0x1051ffff]
pci_bus 0000:01: root bus resource [io 0x8400-0x87ff]
PCI: found device 14e4:8602 on SATA bus, slot 0 (irq 42)
pci 0000:01:00.0: BAR 5: assigned [mem 0x10510000-0x10510fff]
pci 0000:01:00.0: BAR 6: assigned [mem 0x10511000-0x105117ff pref]
Bluetooth: Core ver 2.16
NET: Registered protocol family 31
Bluetooth: HCI device and connection manager initialized
Bluetooth: HCI socket layer initialized
Bluetooth: L2CAP socket layer initialized
Bluetooth: SCO socket layer initialized
cfg80211: Calling CRDA to update world regulatory domain
Switching to clocksource upg
NET: Registered protocol family 2
IP route cache hash table entries: 2048 (order: 1, 8192 bytes)
TCP established hash table entries: 8192 (order: 4, 65536 bytes)
TCP bind hash table entries: 8192 (order: 4, 65536 bytes)
TCP: Hash tables configured (established 8192 bind 8192)
TCP: reno registered
UDP hash table entries: 256 (order: 1, 8192 bytes)
UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
NET: Registered protocol family 1
RPC: Registered named UNIX socket transport module.
RPC: Registered udp transport module.
RPC: Registered tcp transport module.
RPC: Registered tcp NFSv4.1 backchannel transport module.
NFS: Registering the id_resolver key type
Key type id_resolver registered
Key type id_legacy registered
Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
fuse init (API version 7.19)
msgmni has been set to 268
io scheduler noop registered
io scheduler cfq registered (default)
Serial: 8250/16550 driver, 4 ports, IRQ sharing disabled
serial8250.0: ttyS0 at MMIO 0x10400b00 (irq = 22) is a 16550A
console [ttyS0] enabled
serial8250.0: ttyS1 at MMIO 0x10400b40 (irq = 66) is a 16550A
serial8250.0: ttyS2 at MMIO 0x10400b80 (irq = 67) is a 16550A
loop: module loaded
brcm-pm: enabling sata clocks
PCI: Enabling device 0000:01:00.0 (0000 -> 0003)
scsi0 : sata_brcmstb
scsi1 : sata_brcmstb
ata1: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510000 irq 42
ata2: SATA max UDMA7 mmio m4096@0x10510000 port 0x10510100 irq 42
Broadcom 9xxxx mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x001000
NOR chip too large to fit in mapping. Attempting to cope...
Amd/Fujitsu Extended Query Table at 0x0040
Amd/Fujitsu Extended Query version 1.3.
number of CFI chips: 1
Reducing visibility of 8192KiB chip to 2048KiB
###### BCM97XXX NOR flash device: 0x88e22abc bytes @ 0x00800000
Broadcom 9xxxx mapped flash: Found 1 x16 devices at 0x0 in 16-bit bank. Manufacturer ID 0x000001 Chip ID 0x001000
Amd/Fujitsu Extended Query Table at 0x0040
Amd/Fujitsu Extended Query version 1.3.
number of CFI chips: 1
Creating 3 MTD partitions on "Broadcom 9xxxx mapped flash":
0x000000000000-0x000000300000 : "vmlinux"
0x000000300000-0x000000400000 : "splash"
0x000000400000-0x000000480000 : "cfe"
Broadcom STB NAND controller (BrcmNand Controller)
bcmemac: Broadcom STB 10/100 EMAC driver v3.0
bcmemac: registered interface #0 at 0x10080000 as 'eth0' (0c:c6:ac:00:c0:92)
bcmemac: not registering interface #1 at 0x10090000 (no PHY detected)
usbcore: registered new interface driver zd1201
ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
brcm-pm: enabling usb clocks
ehci-brcm ehci-brcm.0: Broadcom STB EHCI
ehci-brcm ehci-brcm.0: new USB bus registered, assigned bus number 1
ehci-brcm ehci-brcm.0: irq 62, io mem 0x10480300
ehci-brcm ehci-brcm.0: USB 0.0 started, EHCI 1.00
hub 1-0:1.0: USB hub found
hub 1-0:1.0: 2 ports detected
ehci-brcm ehci-brcm.1: Broadcom STB EHCI
ehci-brcm ehci-brcm.1: new USB bus registered, assigned bus number 2
ehci-brcm ehci-brcm.1: irq 57, io mem 0x10480500
ehci-brcm ehci-brcm.1: USB 0.0 started, EHCI 1.00
hub 2-0:1.0: USB hub found
hub 2-0:1.0: 2 ports detected
ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
ohci-brcm ohci-brcm.0: Broadcom STB OHCI
ohci-brcm ohci-brcm.0: new USB bus registered, assigned bus number 3
ohci-brcm ohci-brcm.0: irq 63, io mem 0x10480400
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 2 ports detected
ata1: SATA link down (SStatus 4 SControl 300)
ohci-brcm ohci-brcm.1: Broadcom STB OHCI
ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 4
ohci-brcm ohci-brcm.1: irq 64, io mem 0x10480600
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 2 ports detected
Initializing USB Mass Storage driver...
usbcore: registered new interface driver usb-storage
USB Mass Storage support registered.
mousedev: PS/2 mouse device common for all mice
i2c /dev entries driver
lirc_dev: IR Remote Control driver registered, major 254
IR NEC protocol handler initialized
IR RC5(x) protocol handler initialized
IR RC6 protocol handler initialized
IR JVC protocol handler initialized
IR Sony protocol handler initialized
IR RC5 (streamzap) protocol handler initialized
IR SANYO protocol handler initialized
IR MCE Keyboard/mouse protocol handler initialized
IR LIRC bridge handler initialized
usbcore: registered new interface driver btusb
usbcore: registered new interface driver usbkbd
usbcore: registered new interface driver usbmouse
TCP: cubic registered
NET: Registered protocol family 17
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
Key type dns_resolver registered
EBI CS1: setting up NAND flash (primary)
mtd->oobsize=0, mtd->eccOobSize=0
NAND_CS_NAND_XOR=00000000
B4: NandSelect=50000200, nandConfig=58052300, chipSelect=1
brcmnand_read_id: CS1: dev_id=ecd35195
After: NandSelect=50000200, nandConfig=58052300
Block size=00020000, erase shift=17
NAND Config: Reg=58052300, chipSize=1024 MB, blockSize=128K, erase_shift=11
busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
BrcmNAND mfg ec d3 Samsung K9F8G08U0M 1024MB on CS1

Found NAND on CS1: ACC=d3000000, cfg=58052300, flashId=ecd35195, tim1=4232222d, tim2=00000d94
BrcmNAND version = 0x0201 1024MB @00000000
B4: NandSelect=50000200, nandConfig=58052300, chipSelect=1
brcmnand_read_id: CS1: dev_id=ecd35195
After: NandSelect=50000200, nandConfig=58052300
Found NAND flash on Chip Select 1, chipSize=1024MB, usable size=1024MB, base=0
brcmnand_scan: B4 nand_select = 50000200
brcmnand_scan: After nand_select = 50000200
page_shift=11, bbt_erase_shift=17, chip_shift=30, phys_erase_shift=17
Brcm NAND controller version = 2.1 NAND flash size 1024MB @00000000
ECC layout=brcmnand_oob_bch4_4k
brcmnand_scan: mtd->oobsize=64
brcmnand_scan: oobavail=50, eccsize=512, writesize=2048
brcmnand_scan, eccsize=512, writesize=2048, eccsteps=4, ecclevel=15, eccbytes=3
-->brcmnand_default_bbt
brcmnand_default_bbt: bbt_td = bbt_main_descr
Creating 4 MTD partitions on "brcmnand.0":
0x000000000000-0x000002d00000 : "tmtwin"
0x000002d00000-0x00003eb00000 : "rootfs"
0x00003eb00000-0x00003f600000 : "bcmdrv"
0x00003f600000-0x00003ff00000 : "nkernel"
PM: CP0 COUNT/COMPARE frequency depends on divisor
UBI: attaching mtd4 to ubi0
UBI: physical eraseblock size: 131072 bytes (128 KiB)
UBI: logical eraseblock size: 126976 bytes
UBI: smallest flash I/O unit: 2048
UBI: VID header offset: 2048 (aligned 2048)
UBI: data offset: 4096
ata2: SATA link down (SStatus 4 SControl 300)
UBI: max. sequence number: 370
UBI: attached mtd4 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 958 MiB
UBI: number of good PEBs: 7655
UBI: number of bad PEBs: 9
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: 0
UBI: total number of reserved PEBs: 7655
UBI: number of PEBs reserved for bad PEB handling: 76
UBI: max/mean erase counter: 2/0
UBI: image sequence number: 1825136278
ALSA device list:
UBI: background thread "ubi_bgt0d" started, PID 48
No soundcards found.
UBIFS: parse sync
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 518696960 bytes (506540 KiB, 494 MiB, 4085 LEBs)
UBIFS: journal size: 9023488 bytes (8812 KiB, 8 MiB, 72 LEBs)
UBIFS: media format: w4/r0 (latest is w4/r0)
UBIFS: default compressor: lzo
UBIFS: reserved for root: 0 bytes (0 KiB)
VFS: Mounted root (ubifs filesystem) on device 0:10.
devtmpfs: mounted
Freeing unused kernel memory: 244k freed
INIT: version 2.88 booting