PDA

View Full Version : vu+ Duo hangs at start



malacai
09-02-12, 12:53
hi. have a huge problem with my vu+ since i flashed from usb..
now my box dont want to "read usb" in the startup, i have tryed about 10 differnent pen drives and fat32 formated aswell. and the box refuses to scan usb. as shown in the video link below.
http://www.youtube.com/watch?v=_43-LW5sHSs&feature=related

so i hooked it up with serial cable and have tryed to flash alteast 20 different images.. all from org to pli.
tested both vuutil 1.0 and vu+util 2.01

vuutil says ok...
http://www.youtube.com/watch?v=g9lI_oIXFy0


vu+util 2.01 stops at 70% and the VFD on vu says continuing.... and no more..

here is a paste from my terminal

checking usb
Loader:elf Filesys:raw Dev:flash0.kernel File: Options:rootfstype=jffs2 root=/dev/mtdblock0 rw mem=0x8000000 bcmrac=3
Loading: 0x80001000/7078176 0x806c1120/122128 Entry address is 0x805594c0
TP1 Entry Address at 0x80000ffc = 805594c0
Starting program at 0x805594c0

Linux version 3.1.1 (amedeo@localhost.localdomain) (gcc version 4.4.3 (GCC) ) #1 SMP Sat Feb 4 21:29:53 CET 2012
Fetching vars from bootloader... found 11 vars.
Early serial console at MMIO32 0x10400b00 (options '115200n8')
bootconsole [uart0] enabled
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)
bootconsole [early0] enabled
CPU revision is: 0002a044 (Brcm4380)
FPU revision is: 00130001
Determined physical RAM map:
memory: 10000000 @ 00000000 (usable)
bmem: adding 112 MB RESERVED region at 144 MB (0x07000000@0x09000000)
Initrd not found or empty - disabling initrd
Zone PFN ranges:
Normal 0x00000000 -> 0x00010000
Movable zone start PFN for each node
early_node_map[1] active PFN ranges
0: 0x00000000 -> 0x00010000
PERCPU: Embedded 7 pages/cpu @81203000 s4384 r8192 d16096 u32768
Built 1 zonelists in Zone order, mobility grouping on. Total pages: 65024
Kernel command line: bmem=112M ubi.mtd=0 root=ubi0:rootfs rootfstype=ubifs rw rootflags=sync
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)
Primary instruction cache 32kB, VIPT, 2-way, linesize 64 bytes.
Primary data cache 64kB, 4-way, VIPT, cache aliases, linesize 64 bytes
Memory: 138096k/262144k available (5523k kernel code, 124048k reserved, 1145k data, 244k init, 0k highmem)
Hierarchical RCU implementation.
NR_IRQS:128
Detected MIPS clock frequency: 404 MHz (202.497 MHz counter)
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
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.24.
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 5: set to [mem 0x10510000-0x10510fff] (PCI address [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
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: 128 (order: 0, 4096 bytes)
UDP-Lite hash table entries: 128 (order: 0, 4096 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.
NTFS driver 2.1.30 [Flags: R/W].
JFFS2 version 2.2. (NAND) (SUMMARY) © 2001-2006 Red Hat, Inc.
msgmni has been set to 269
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, bootconsole disabled
console [ttyS0] enabled, bootconsole disabled
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 STB NAND controller (BrcmNand Controller)
bcmemac: Broadcom STB 10/100 EMAC driver v3.0
bcmemac: registered interface #0 at 0x10080000 as 'eth0' (00:1d:ec:02:9a:ce)
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
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
ata1: SATA link down (SStatus 4 SControl 300)
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
Success! Registering the characther device success with 0
blackhole initialised
Bluetooth: Generic Bluetooth USB driver ver 0.6
usbcore: registered new interface driver btusb
usbcore: registered new interface driver usbhid
usbhid: USB HID core driver
ALSA device list:
No soundcards found.
TCP cubic registered
NET: Registered protocol family 17
Bluetooth: HIDP (Human Interface Emulation) ver 1.2
lib80211: common routines for IEEE802.11 drivers
EBI CS0: setting up NAND flash (primary)
mtd->oobsize=0, mtd->eccOobSize=0
NAND_CS_NAND_XOR=00000001
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Block size=00020000, erase shift=17
NAND Config: Reg=55042200, chipSize=128 MB, blockSize=128K, erase_shift=11
busWidth=1, pageSize=2048B, page_shift=11, page_mask=000007ff
BrcmNAND mfg ec f1 Samsung K9F1G08U0A 128MB on CS0

Found NAND on CS0: ACC=d3000000, cfg=55042200, flashId=ecf10095, tim1=4232222d, tim2=00000d94
BrcmNAND version = 0x0201 128MB @00000000
B4: NandSelect=40000101, nandConfig=55042200, chipSelect=0
brcmnand_read_id: CS0: dev_id=ecf10095
After: NandSelect=40000101, nandConfig=55042200
Found NAND flash on Chip Select 0, chipSize=128MB, usable size=128MB, base=0
brcmnand_scan: B4 nand_select = 40000101
brcmnand_scan: After nand_select = 40000101
page_shift=11, bbt_erase_shift=17, chip_shift=27, phys_erase_shift=17
Brcm NAND controller version = 2.1 NAND flash size 128MB @18000000
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 7 MTD partitions on "brcmnand.0":
0x000000000000-0x000007600000 : "rootfs"
0x000007600000-0x000007a00000 : "kernel"
0x000007a00000-0x000007c00000 : "boot"
0x000007c00000-0x000007d00000 : "cfe"
0x000007d00000-0x000007d80000 : "mac"
0x000007d80000-0x000007e00000 : "env"
0x000007e00000-0x000007f00000 : "nvm"
UBI: attaching mtd0 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: empty MTD device detected
UBI: max. sequence number: 0
UBI: create volume table (copy #1)
UBI: create volume table (copy #2)
UBI: attached mtd0 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 118 MiB
UBI: number of good PEBs: 942
UBI: number of bad PEBs: 2
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: 0
UBI: available PEBs: 929
UBI: total number of reserved PEBs: 13
UBI: number of PEBs reserved for bad PEB handling: 9
UBI: max/mean erase counter: 0/0
UBI: image sequence number: -1101451558
VFS: Cannot open root device "ubi0:rootfs" or unknown-block(8,1)
UBI: background thread "ubi_bgt0d" started, PID 44
Please append a correct "root=" boot option; here are the available partitions:
1f00 120832 mtdblock0 (driver?)
1f01 4096 mtdblock1 (driver?)
1f02 2048 mtdblock2 (driver?)
1f03 1024 mtdblock3 (driver?)
1f04 512 mtdblock4 (driver?)
1f05 512 mtdblock5 (driver?)
1f06 1024 mtdblock6 (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,1)
Rebooting in 180 seconds..

when i left a usb stick in the vu and boot:

BCM73350010
012
Shmoo Version=1.9

MEMC-00000000 RW=00000010 WW=00000049 G=00000001 R=00000008 W=00000012
MEMC-00000001 RW=00000010 WW=0000004D G=00000001 R=00000008 W=00000004 #$
3
COPY CODE
A567

BCM97335B0 CFE v2.17, CFE core v2.12, Endian Mode: Little
Build Date: Thu Sep 29 12:01:32 2011 (shcheong@ncsh)
Copyright (C) Broadcom Corporation.

writing vfd

DDR Freq: 395MHz
CPU speed: 405MHz
Memory Config: 32+16 non-UMA
Device Tech: 1Gb
Total memory: 384MB
Boot Device: NAND
ECC: Hamming
Total flash: 128MB

Initializing USB.
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub

CFE initialized.

**Exception 32: EPC=8D953881, Cause=00008028, VAddr=00000000
RA=87041191, PRID=0002A044

0 ($00) = 00000000 AT ($01) = A0000000
v0 ($02) = 00005355 v1 ($03) = 870105CC
a0 ($04) = 87148578 a1 ($05) = 87041180
a2 ($06) = 00000001 a3 ($07) = 00000001
t0 ($08) = 00000000 t1 ($09) = 870465C4
t2 ($10) = 00000038 t3 ($11) = 8706E538
t4 ($12) = 00000001 t5 ($13) = 00000000
t6 ($14) = 00000000 t7 ($15) = 00000000
s0 ($16) = 00000002 s1 ($17) = 00000000
s2 ($18) = 00000000 s3 ($19) = 00000000
s4 ($20) = 00000038 s5 ($21) = 8706E538
s6 ($22) = 00000001 s7 ($23) = 00000001
t8 ($24) = 00000000 t9 ($25) = 870471F4
k0 ($26) = 00000000 k1 ($27) = 00000018
gp ($28) = 8704E210 sp ($29) = 871485A8
fp ($30) = A706D6D0 ra ($31) = 87041191


*** Waiting for system reset ***


ctrl + c just stops the vu in a short time, need to ctrl + u aswell to manual usb.. if a usb is inserted @ start.

do any one have a clue what i can do to make this box work again? and yes its a 100% orginal vu+duo

/regards malacai

mcquaim
09-02-12, 12:59
Are you flashing with the bootloader first before trying to flash the new image?

malacai
09-02-12, 13:03
in vuutil is doesent work at all to flash bootloader, but in 2.01 it works.. but i get a faulty message.. dont realy remeber what it says.. but i can try another bootloader flash and give u the exact faulty message?

Sicilian
09-02-12, 13:06
Is this a genuine or clone unit?

malacai
09-02-12, 13:10
this is 100% genuine box

mcquaim
09-02-12, 13:13
Try it without using Vu Util, I never use that..

Simply download the files from the link below and extract them onto a USB stick:

http://www.world-of-satellite.com/showthread.php?14236-Vu-Duo-ViX-2-3-(Linux-3-1-1)-Image-Release-s

This is the note from the Image download page about the bootloader:

This image requires the latest bootloader (attached to this post) to be flashed. This is because Vu+ have changed the way the drivers work. So, before updating your image, you will need to first flash the bootloader, then flash the new image. Flashing of new bootloader only takes a few seconds, so once flashing's completed, then just turn off the box, transfer the new image to the usb stick, and flash with that.

Try this and see how you get on..

malacai
09-02-12, 13:16
well i can give it a try.. but i dubt it.. cos i cant get my vu to read from usb in anyway.. :/

malacai
09-02-12, 13:22
nah.. since i cant get it to read of usb.. no go..

mcquaim
09-02-12, 13:59
This looks like a query for the big guns, no power to the USB ports is a worry :confused:

Some of the lads will post a reply shortly I'm sure with some ideas to try!

sonc
09-02-12, 14:02
In the video it looks like you still have the internal HDD attached. I would suggest removing everything, HDDs, rear USB sticks, network connection, power lead, then leave the box for at least 30minutes.

Then attach the power lead, insert a USB stick (front port) that you know has worked in the past (with the correct /vuplus/duo/* directory set-up), and give that a try.

malacai
09-02-12, 14:06
i have power on the usb, but its seems like somehow it skips the "i want to check the usb first"..
sata+power is disconected from the hdd.. aswell as hdmi etc.

and big thanks for trying to help me

/regards malacai

micscave
09-02-12, 17:16
This happened to me using a USB stick that I knew worked. On that occasion I had formated it using a 3rd party program. Once I formated it to FAT32 in windows, it worked again & has done ever since.

Worth a try.
micscave

malacai
09-02-12, 17:33
i have used hp storage format tool.. and fat32 for all my pen drives.. :/.. have tested windows format to fat 32 aswell :/

malacai
09-02-12, 19:52
no one has any other suggestions and try usb... i can promise.. it wont boot usb.. box totaly skips that step when power on.

Rob van der Does
10-02-12, 08:19
I would suggest removing everything, HDDs, rear USB sticks, network connection, power lead, then leave the box for at least 30minutes.

Then attach the power lead, insert a USB stick (front port) that you know has worked in the past (with the correct /vuplus/duo/* directory set-up), and give that a try.
I agree with removing all stuff first.
Using front or rear port should make no difference: try both
Make sure the USB pen only contains the image folder.
Format the pen with the attached program.

malacai
10-02-12, 12:31
sorry.. allready done that like 50 times

Rob van der Does
10-02-12, 13:03
sorry.. allready done that like 50 times
Then I guess there's only one conclusion: hardware defect.

pooface
10-02-12, 14:41
Try connecting the rs232 and putty to get the log, then plug in the usb, and turn on the box. Post the log from putty...

malacai
10-02-12, 16:03
this is when i start the vu with a usb inserted in the front:


BCM73350010
012
Shmoo Version=1.9

MEMC-00000000 RW=00000010 WW=0000004B G=00000001 R=00000008 W=00000011
MEMC-00000001 RW=00000010 WW=0000004B G=00000001 R=00000008 W=00000003 #$
3
COPY CODE
A567

BCM97335B0 CFE v2.17, CFE core v2.12, Endian Mode: Little
Build Date: Thu Sep 29 12:01:32 2011 (shcheong@ncsh)
Copyright (C) Broadcom Corporation.

writing vfd

DDR Freq: 395MHz
CPU speed: 405MHz
Memory Config: 32+16 non-UMA
Device Tech: 1Gb
Total memory: 384MB
Boot Device: NAND
ECC: Hamming
Total flash: 128MB

Initializing USB.
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub
USB: Locating Class 09 Vendor 0000 Product 0000: USB Hub

CFE initialized.

**Exception 32: EPC=89951081, Cause=00008028, VAddr=00000000
RA=8704124C, PRID=0002A044

0 ($00) = 00000000 AT ($01) = A0000000
v0 ($02) = 00005355 v1 ($03) = 87010000
a0 ($04) = 87148578 a1 ($05) = 87016369
a2 ($06) = 00000001 a3 ($07) = 00000001
t0 ($08) = 00000000 t1 ($09) = 870465C4
t2 ($10) = 00000038 t3 ($11) = 8706E538
t4 ($12) = 00000001 t5 ($13) = 00000000
t6 ($14) = 00000000 t7 ($15) = 00000000
s0 ($16) = 00000002 s1 ($17) = 00000000
s2 ($18) = 00000000 s3 ($19) = 00000000
s4 ($20) = 00000038 s5 ($21) = 8706E538
s6 ($22) = 00000001 s7 ($23) = 00000001
t8 ($24) = 00000000 t9 ($25) = 870471F4
k0 ($26) = 00000000 k1 ($27) = 00000018
gp ($28) = 8704E210 sp ($29) = 871485A8
fp ($30) = A706D6D0 ra ($31) = 8704124C


*** Waiting for system reset ***

ekkostar
13-02-12, 22:05
Sounds pretty much like the USB stick.

VU is particular about the flash memory on a pen drive. You may need to try a few until you get one that works. Try use an old small memory size flash if you can, format FAT32.