Hw error vu+ solo2 clone

caucaso

Inactive User
Joined
Mar 31, 2014
Messages
14
Reaction score
2
Good afternoon I read a lot for this great forum, I expose my problem after reading and not have doubts if you have solution:
I have a vu + clone solo2 try to update my problem started and there I went HW ERROR, I have tried with other pictures mime result blachole 2.0.7, 208, 2.0.9, 2.0.2 blachole even not as do more, my question is simple and has a solution as fix, or better forget me and I miss her aid
pardon my language use google translator, greetings
 
Good afternoon I read a lot for this great forum, I expose my problem after reading and not have doubts if you have solution:
I have a vu + clone solo2 try to update my problem started and there I went HW ERROR, I have tried with other pictures mime result blachole 2.0.7, 208, 2.0.9, 2.0.2 blachole even not as do more, my question is simple and has a solution as fix, or better forget me and I miss her aid
pardon my language use google translator, greetings

you really have not read this great forum that well.Look!


http://www.digitalworldz.co.uk/index.php?resources/1412/ flash this

http://www.digitalworldz.co.uk/index.php?resources/1464/ or this

then try this. http://www.digitalworldz.co.uk/vu-solo2-receivers-633/391241-upgrading-vu-solo2-clone.html.

And when your bored read through this thread as just about anything related to solo 2 clone is here..

http://www.digitalworldz.co.uk/vu-solo2-receivers-633/378201-anyone-got-chinese-vu.html
gets good around page 40.
 
Last edited by a moderator:
Thanks for reading and I'm really cost me much since I use the google translator but if I try to read and is a great forum, and thank you very much again to you and many teachers like you
 
Thanks for reading and I'm really cost me much since I use the google translator but if I try to read and is a great forum, and thank you very much again to you and many teachers like you

Hello I've been reading, the first thing I did was put this Blackhole 2.0.9 by AJT clone safe image, HW ERROR now does not appear to me only me appears starting, I have VU + Solo2 Clone FPGA Update and null Cable moden my dreambox 800 I guess be worth, but not firmly continue excuse my clumsiness
 
If you are trying to firmware update the box you need to use the cable that came with the box, a null modem cable won't really work although I have read that some people have used a null modem cable to actually partially revive a non working box.
 
Cable not carrying my box, I'm making a cable with the connections I've read in the forum, my pc has input rs232

PC ------------------- STB
2 ----------------------- 1
3 ----------------------- 6
5 ----------------------- 5

thanks
 
I tried the whole process and the steps correctly accept same problem continues "from" Nobody read me said putty or not it has "cfe_cfe_auto.bin" I've looked everywhere, but only the solo vu encounter and vusolo2 duo did not find, any ideas, it seems he lacks the bootloader boot and can not give more
 
Last edited:
I tried the whole process and the steps correctly accept same problem continues "from" Nobody read me said putty or not it has "cfe_cfe_auto.bin" I've looked everywhere, but only the solo vu encounter and vusolo2 duo did not find, any ideas, it seems he lacks the bootloader boot and can not give more

Hi cfc auto bin is the boot loader.
 
it makes me even more mad, after making the whole process according to its manual image blachole 2.08, 2.07, 2.0,6 etc hw errror image 2.09 and new pictures starting always, the deco is the leading chip laying Vusolo2 and 2 seems fine writing pen.
Do not throw in the towel
Thanks for your attention
 
I tried with 2.0.7 original FGA update OK a writing successfull update file via serial but nothing HW error
Using a satbenus patched image 2.0.9 FGA update say file not found!
 
yo he puesto hasta la original y se queda igual, ayer me comento un buen amigo despues de mas de dos horas haciendo pruebas que el deco esta correcto pero hay que adivinar cual es la imagen correcta para este aparato, yo soy poseedor de una vusolo2 original, esta que me da problemas era para usar en otra habitacion
 
yo he puesto hasta la original y se queda igual, ayer me comento un buen amigo despues de mas de dos horas haciendo pruebas que el deco esta correcto pero hay que adivinar cual es la imagen correcta para este aparato, yo soy poseedor de una vusolo2 original, esta que me da problemas era para usar en otra habitacion
I put up the original and remains the same, yesterday I commented a good friend after more than two hours doing tests that the deco is correct but you have to guess which is the right image for this product, I am holder of the original vusolo2 this was giving me problems for use in another room
 
data step that gives me the putty with blachole2.0.7
ehci-brcm ehci-brcm.0: irq 69, 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: 1 port 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 70, 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: 1 port detected
ehci-brcm ehci-brcm.2: Broadcom STB EHCI
ehci-brcm ehci-brcm.2: new USB bus registered, assigned bus number 3
ehci-brcm ehci-brcm.2: irq 74, io mem 0x10490300
ehci-brcm ehci-brcm.2: USB 0.0 started, EHCI 1.00
hub 3-0:1.0: USB hub found
hub 3-0:1.0: 1 port detected
ehci-brcm ehci-brcm.3: Broadcom STB EHCI
ehci-brcm ehci-brcm.3: new USB bus registered, assigned bus number 4
ehci-brcm ehci-brcm.3: irq 75, io mem 0x10490500
ehci-brcm ehci-brcm.3: USB 0.0 started, EHCI 1.00
hub 4-0:1.0: USB hub found
hub 4-0:1.0: 1 port 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 5
ohci-brcm ohci-brcm.0: irq 71, io mem 0x10480400
hub 5-0:1.0: USB hub found
hub 5-0:1.0: 1 port detected
ohci-brcm ohci-brcm.1: Broadcom STB OHCI
ohci-brcm ohci-brcm.1: new USB bus registered, assigned bus number 6
ohci-brcm ohci-brcm.1: irq 72, io mem 0x10480600
hub 6-0:1.0: USB hub found
hub 6-0:1.0: 1 port detected
ohci-brcm ohci-brcm.2: Broadcom STB OHCI
ohci-brcm ohci-brcm.2: new USB bus registered, assigned bus number 7
ohci-brcm ohci-brcm.2: irq 76, io mem 0x10490400
hub 7-0:1.0: USB hub found
hub 7-0:1.0: 1 port detected
ohci-brcm ohci-brcm.3: Broadcom STB OHCI
ohci-brcm ohci-brcm.3: new USB bus registered, assigned bus number 8
ohci-brcm ohci-brcm.3: irq 77, io mem 0x10490600
usb 4-1: new high-speed USB device number 2 using ehci-brcm
hub 8-0:1.0: USB hub found
hub 8-0:1.0: 1 port 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
WARNING: You are using an experimental version of the media stack.
As the driver is backported to an older kernel, it doesn't offer
enough quality for its usage in production.
Use it with care.
Latest git patches (needed if you report a bug to [email protected]):
3151d14aa6e983aa36d51a80d0477859f9ba12af [media] media: remove __dev* annotations
978ae2247fac3b330ecd1095823001d2c08c7efd [media] extract_xc3028.pl: fix permissions
73ec66c000e9816806c7380ca3420f4e0638c40e [media] stv0900: Multistream support
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
Success! Registering the characther device success with 0
blackhole initialised
sdhci: Secure Digital Host Controller Interface driver
sdhci: Copyright(c) Pierre Ossman
sdhci-pltfm: SDHCI platform and OF driver helper
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
lib80211: common routines for IEEE802.11 drivers
PM: CP0 COUNT/COMPARE frequency does not depend on divisor
EBI CS0: setting up NAND flash (primary)
NAND device: Manufacturer ID: 0xec, Chip ID: 0xda (Samsung NAND 256MiB 3,3V 8-bit)
brcmnand brcmnand.0: 256MiB total, 128KiB blocks, 2KiB pages, 16B OOB, 8-bit, Hamming ECC
Bad block table found at page 131008, version 0x06
Bad block table found at page 130944, version 0x06
nand_read_bbt: bad block at 0x000000700000
nand_read_bbt: bad block at 0x000001aa0000
nand_read_bbt: bad block at 0x0000030c0000
nand_read_bbt: bad block at 0x000006b40000
nand_read_bbt: bad block at 0x000007fe0000
nand_read_bbt: bad block at 0x000008760000
nand_read_bbt: bad block at 0x00000a780000
nand_read_bbt: bad block at 0x00000af80000
nand_read_bbt: bad block at 0x00000bfa0000
nand_read_bbt: bad block at 0x00000c260000
nand_read_bbt: bad block at 0x00000de80000
nand_read_bbt: bad block at 0x00000e4e0000
Creating 4 MTD partitions on "brcmnand.0":
0x000001f00000-0x000010000000 : "rootfs"
0x000001f00000-0x000010000000 : "rootfs(redundant)"
0x000000200000-0x000000900000 : "kernel"
0x000000900000-0x000000a00000 : "mac"
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
scsi2 : usb-storage 4-1:1.0
UBI: max. sequence number: 4
UBI: attached mtd0 to ubi0
UBI: MTD device name: "rootfs"
UBI: MTD device size: 225 MiB
UBI: number of good PEBs: 1786
UBI: number of bad PEBs: 14
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: 1786
UBI: number of PEBs reserved for bad PEB handling: 17
UBI: max/mean erase counter: 314/78
UBI: image sequence number: 939172080
UBI: background thread "ubi_bgt0d" started, PID 46
scsi 2:0:0:0: Direct-Access USB DISK 2.0 PMAP PQ: 0 ANSI: 0 CCS
sd 2:0:0:0: Attached scsi generic sg0 type 0

sd 2:0:0:0: [sda] 7829504 512-byte logical blocks: (4.00 GB/3.73 GiB)
sd 2:0:0:0: [sda] Write Protect is off
sd 2:0:0:0: [sda] No Caching mode page present
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] No Caching mode page present
sd 2:0:0:0: [sda] Assuming drive cache: write through
sda: sda1
sd 2:0:0:0: [sda] No Caching mode page present
sd 2:0:0:0: [sda] Assuming drive cache: write through
sd 2:0:0:0: [sda] Attached SCSI removable disk
UBIFS: parse sync
UBIFS: recovery needed
UBIFS: recovery completed
UBIFS: mounted UBI device 0, volume 0, name "rootfs"
UBIFS: file system size: 222715904 bytes (217496 KiB, 212 MiB, 1754 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:14.
devtmpfs: mounted
Freeing unused kernel memory: 184k freed
INIT: version 2.88 booting
procmk_init
dvb_bcm7356: module license 'Proprietary' taints kernel.
Disabling lock debugging due to kernel taint
DVB: registering new adapter (vusolo2)
bcm7356: hotplug_callback():
Hotplug - status.connected 0:0
[GP]:brcm_pwm_init

CPU 0 Unable to handle kernel paging request at virtual address e0d58ab4, epc == e0d58ab4, ra == 80077274
Oops[#1]:
Cpu 0
$ 0 : 00000000 10108300 e0d58ab4 00060000
$ 4 : 00000004 e17b2310 00000000 10000000
$ 8 : 10108700 1000001f 00000001 fffffff4
$12 : 8065fc00 8065fc00 0000000a 004c0000
$16 : ccc4f900 00000004 00000000 00000000
$20 : 00000004 8062ed80 80640000 806b0000
$24 : 004bf200 77ce6e2c
$28 : cff72000 cff73be8 805bad78 80077274
Hi : 00000003
Lo : ef7bdf62
epc : e0d58ab4 0xe0d58ab4
Tainted: P O
ra : 80077274 handle_irq_event_percpu+0x78/0x248
Status: 10108302 KERNEL EXL
Cause : 00800008
BadVA : e0d58ab4
PrId : 00025a11 (Brcm4380)
Modules linked in: procmk(O)
Process modprobe (pid: 72, threadinfo=cff72000, task=cf70a038, tls=77d9a490)
Stack : 80639a54 8069ee80 00000000 8069ee80 8069e630 8005980c 8062ed80 00000004
00000001 00000020 00411400 00411600 cff73e6c 00000000 80000000 80077494
0000000a 00000000 806ab200 80639a54 8069e630 8002b0f4 8062ed80 8007aae0
00000001 00000000 00000004 00000001 00000000 800768c4 00000000 00000002
00000001 00000020 00000000 80005e54 cff73e6c 00000000 00000002 8002b454
...
Call Trace:
[<8005980c>] run_rebalance_domains+0x68/0x23c
[<80077494>] handle_irq_event+0x50/0x8c
[<8002b0f4>] __do_softirq+0x104/0x1bc
[<8007aae0>] handle_level_irq+0xd4/0x13c
[<800768c4>] generic_handle_irq+0x34/0x54
[<80005e54>] do_IRQ+0x18/0x24
[<8002b454>] do_softirq+0x64/0x78
[<80003048>] brcm_intc_dispatch.isra.0+0x90/0x220
[<80005e54>] do_IRQ+0x18/0x24
[<8002b73c>] irq_exit+0xac/0xd4
[<800032a4>] plat_irq_dispatch+0xcc/0x10c
[<80004144>] ret_from_irq+0x0/0x4
[<8008a55c>] __alloc_pages_nodemask+0xec/0x66c
[<800a4548>] unmap_vmas+0x440/0x63c
[<8009cbf0>] __dec_zone_state+0x38/0x18c
[<8008aaf4>] __get_free_pages+0x18/0x54
[<800a4548>] unmap_vmas+0x440/0x63c
[<80090464>] pagevec_lru_move_fn+0xe0/0x11c
[<8009113c>] lru_add_drain+0xd4/0x144
[<800a840c>] unmap_region+0x90/0x120
[<800a97d8>] do_munmap+0x2a8/0x344
[<800aad0c>] sys_munmap+0x40/0x68
[<8000d77c>] stack_done+0x20/0x40
[<802d1f38>] __bzero+0xbc/0x164


Code: (Bad address in epc)

---[ end trace 56f8e1dec44bc007 ]---
Kernel panic - not syncing: Fatal exception in interrupt
Rebooting in 180 seconds..
 
some news???
I have this error and I dont know...
Help!!!!
 
How check FPGA version in image and on tuner?

Dont think there is a way to check the version other then flashing a v4 clone safe image if it boots you have V4 if not work backwards to a v3 image etc then the image that boots will be the version you have.
 
I know this is an old thread but thought I would post my findings as a search may lead people here/

I've an old Dragonworth solo2 so tied to V2 images only.

I've been getting a few random freezes and either just power light on a re-boot or HW Error
This has been going on for a week or so.
Upon a little investigation, I found the PSU was outputting 11.82 Volts
I've swapped it out for a supply that is outputting 12.4 Volts and had no issues since.

Thought it may be worth a mention.
 
Back
Top