Problematic flashing of DBox 2

frederick

frederick

Hi Guys

Hope some one can help me out

I have a Nokia Dbox2 ( 2x intel) I am trying to flash. I have flashed with IFA using a known good backup image ( andromeda 2) from another dbox.

All seems OK with IFA and appears to flash OK.

On rebooting the box the LCD shows the debug screen, the brief U Boot screen, loading Kernel, the spinning dbox lcd logo, which then freezes. After a few seconds the screen just goes blank ( well a faint green, power stays on)

And nothing else. Currently the box is not connected to the TV, but when it was it got as far as showing the startup screen for Andromeda.

I can ftp to the box and also see the Yweb screen in internet explorer so it must have picked up the network address in my backup image !

Attached is what i hope is the bootlog from IFA when i tried to reflash >>

9debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.0 mID 01
debug: feID 7a gtxID 0b
debug: fpID 5a dsID http://Hallenberg.com
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 32/00/08
WATCHDOG reset enabled
debug: autoboot aborted from terminal
dbox2:root>
dbox2:root> boot net net net net net net net net net net
debug:
BOOTP/TFTP bootstrap loader (v0.3)
debug:
debug: Transmitting BOOTP request via broadcast
debug: Got BOOTP reply from Server IP 192.168.2.39, My IP 192.168.2.202
debug: Sending TFTP-request for file D/dboxifa_tmp/tftpboot/u-boot
will verify ELF image, start= 0x800000, size= 140336
verify sig: 263
boot net: boot file has no valid signature
Branching to 0x40000


U-Boot 1.1.2 (Tuxbox) (Jun 12 2005 - 13:44:14)

CPU: PPC823ZTnnB2 at 67.200 MHz: 2 kB I-Cache 1 kB D-Cache
Board: DBOX2, Nokia, BMon V1.0
Watchdog enabled
I2C: ready
DRAM: 32 MB
FLASH: 8 MB
FB: ready
LCD: ready
In: serial
Out: serial
Err: serial
Net: SCC ETHERNET
BOOTP broadcast 1
Using SCC ETHERNET device
TFTP from server 192.168.2.39; our IP address is 192.168.2.202
Filename 'D/dboxifa_tmp/tftpboot/u-boot'.
Load address: 0x100000
Loading: *Using SCC ETHERNET device
TFTP from server 192.168.2.39; our IP address is 192.168.2.202
Filename '/tftpboot/logo-lcd'.
Load address: 0x100000
Loading: *##
done
Bytes transferred = 7680 (1e00 hex)
BOOTP broadcast 1
Using SCC ETHERNET device
TFTP from server 192.168.2.39; our IP address is 192.168.2.202
Filename 'D/dboxifa_tmp/tftpboot/u-boot'.
Load address: 0x100000
Loading: *Using SCC ETHERNET device
TFTP from server 192.168.2.39; our IP address is 192.168.2.202
Filename '/tftpboot/logo-fb'.
Load address: 0x100000
Loading: *####################################
done
Bytes transferred = 179877 (2bea5 hex)

Options:
1: Console on null
2: Console on ttyS0
3: Console on framebuffer
Select option (1-3), other keys to stop autoboot: 0

Bank # 1: INTEL 28F320C3B (32M, bottom boot sect), 32 bit

Size: 8192 kB in 71 Sectors

Using SCC ETHERNET device
TFTP from server 192.168.2.39; our IP address is 192.168.2.202
Filename 'kernel-yadd'.
Load address: 0x100000
Loading: *#################################################################
#################################################################
####################
done
Bytes transferred = 763552 (ba6a0 hex)
...............................................................
Un-Protected 63 sectors
## Booting image at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 763488 Bytes = 745.6 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK


















dbox2 - ImageFlashingAssistent

- Hallenberg.com -

Wilkommen auf ihrer dbox2


Starte Backup....
Schreibe Backup: 8064k von 8064k (100%)
Backup abgeschlossen!
Der Flashprozess wird nun gestartet...
Lösche Sektoren: 63 von 63 (100%)
Schreibe Daten: 8064k von 8064k (100%)
Verifziere Daten: 8064k von 8064k (100%)
Flashen beendet!



All help in getting this box going greatly appreciated


TIA


Freddy
 
Looks like a bad flash to me, have to tried to reflash again usin IFA ?
If i was you i would start fresh too (download a clean copy of andro2 from download section )
 
Hi

and thanks for reply

I have tried flashing may times using all the versions of IFA but with same result :(

Have just done as you suggested using a clean copy of andromeda 2, but same end result >>>

this time have posted bootlog generated using IFA RC003, seems to have lot more information in it. To be honest it doesn't mean anything to me , but hope it might help someone to try to resolve my problem. ( did this one from my laptop)

All and any other thoughts appreciated ......

9debug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.0 mID 01
debug: feID 7a gtxID 0b
debug: fpID 5a dsID http://Hallenberg.com
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 32/00/08
WATCHDOG reset enabled
debug: autoboot aborted from terminal
dbox2:root> boot net net net net net net net net net net
debug:
BOOTP/TFTP bootstrap loader (v0.3)
debug:
debug: Transmitting BOOTP request via broadcast
debug: Got BOOTP reply from Server IP 192.168.2.44, My IP 192.168.2.202
debug: Sending TFTP-request for file u-boot
debug: Got Block #0050
debug: Got Block #0050
debug: Got Block #0100
debug: Got Block #0150
debug: Got Block #0200
debug: Got Block #0250
will verify ELF image, start= 0x800000, size= 140064
verify sig: 262
boot net: boot file has no valid signature
Branching to 0x40000


U-Boot 1.3.1 (Tuxbox - Hallenberg.com) (Dec 23 2007 - 22:22:21)

CPU: PPC823ZTnnB2 at 67.200 MHz: 2 kB I-Cache 1 kB D-Cache
Board: DBOX2, Nokia, BMon V1.0
Watchdog enabled
I2C: ready
DRAM: 32 MB
FLASH: 8 MB
FB: ready
LCD: ready
In: serial
Out: serial
Err: serial
Net: SCC ETHERNET
BOOTP broadcast 1
Using SCC ETHERNET device
TFTP from server 192.168.2.44; our IP address is 192.168.2.202
Filename 'u-boot'.
Load address: 0x100000
Loading: *Using SCC ETHERNET device
TFTP from server 192.168.2.44; our IP address is 192.168.2.202
Filename 'logo-lcd'.
Load address: 0x100000
Loading: *##
done
Bytes transferred = 7680 (1e00 hex)
BOOTP broadcast 1
Using SCC ETHERNET device
TFTP from server 192.168.2.44; our IP address is 192.168.2.202
Filename 'u-boot'.
Load address: 0x100000
Loading: *Using SCC ETHERNET device
TFTP from server 192.168.2.44; our IP address is 192.168.2.202
Filename 'logo-fb'.
Load address: 0x100000
Loading: *####################################
done
Bytes transferred = 179877 (2bea5 hex)

Options:
1: Console on null
2: Console on ttyS0
3: Console on framebuffer
Select option (1-3), other keys to stop autoboot: 1  0
Using SCC ETHERNET device
TFTP from server 192.168.2.44; our IP address is 192.168.2.202
Filename 'kernel-cdk'.
Load address: 0x100000
Loading: *#################################################################
##########################################################
done
Bytes transferred = 626057 (98d89 hex)
Using SCC ETHERNET device
TFTP from server 192.168.2.44; our IP address is 192.168.2.202
Filename 'u-initrd'.
Load address: 0x400000
Loading: *#################################################################
#################################################
done
Bytes transferred = 581765 (8e085 hex)
............................................................... done
Un-Protected 63 sectors
## Booting image at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip compressed)
Data Size: 625993 Bytes = 611.3 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
## Loading RAMDisk Image at 00400000 ...
Image Name: Ramdisk Image
Image Type: PowerPC Linux RAMDisk Image (gzip compressed)
Data Size: 581701 Bytes = 568.1 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Ramdisk to 01f21000, end 01faf045 ... OK
Linux version 2.4.35.5-dbox2 (www.hallenberg.com) (gcc version 3.4.6) #5 So 23. Dez 21:59:04 CET 2007

On node 0 totalpages: 8192

zone(0): 8192 pages.

zone(1): 0 pages.

zone(2): 0 pages.

Kernel command line: console=ttyS0 root=/dev/ram rw ip=192.168.2.202:192.168.2.44:::::off

Decrementer Frequency = 252000000/60

m8xx_wdt: active wdt found (SWTC: 0xFFFF, SWP: 0x1)

m8xx_wdt: keep-alive trigger installed (PITC: 0x12C0)

Console: colour dummy device 80x25

Calibrating delay loop... 66.96 BogoMIPS

Memory: 30352k available (1048k kernel code, 324k data, 72k init, 0k highmem)

Dentry cache hash table entries: 4096 (order: 3, 32768 bytes)

Inode cache hash table entries: 2048 (order: 2, 16384 bytes)

Mount cache hash table entries: 512 (order: 0, 4096 bytes)

Buffer cache hash table entries: 1024 (order: 0, 4096 bytes)

Page-cache hash table entries: 8192 (order: 3, 32768 bytes)

POSIX conformance testing by UNIFIX

Linux NET4.0 for Linux 2.4

Based upon Swansea University Computer Society NET3.039

Initializing RT netlink socket

Starting kswapd

devfs: v1.12c (20020818) Richard Gooch ([email protected])

devfs: boot_options: 0x1

i2c-core.o: i2c core module version 2.6.1 (20010830)

i2c-dev.o: i2c /dev entries driver module version 2.6.1 (20010830)

CPM UART driver version 0.04

ttyS0 at 0x0280 is on SMC1 using BRGÿttyS1 at 0x0380 is on SMC2 using BRG2

pty: 256 Unix98 ptys configured

eth0: CPM ENET Version 0.2.dbox2 on SCC2, 00:50:9c:42:38:14

RAMDISK driver initialized: 16 RAM disks of 3333K size 1024 blocksize

D-Box 2 flash driver (size->0x800000 mem->0x10000000)

D-Box 2 flash memory: Found 2 x16 devices at 0x0 in 32-bit bank

Intel/Sharp Extended Query Table at 0x0035

cfi_cmdset_0001: Erase suspend on write enabled

Creating 6 MTD partitions on "D-Box 2 flash memory":

0x00000000-0x00020000 : "BR bootloader"

0x00020000-0x00040000 : "FLFS (U-Boot)"

0x00040000-0x006a0000 : "root (rootfs)"

0x006a0000-0x00800000 : "var (jffs2)"

0x00020000-0x00800000 : "Flash without bootloader"

0x00000000-0x00800000 : "Complete Flash"

Linux video capture interface: v1.00

mice: PS/2 mouse device common for all mice

NET4: Linux TCP/IP 1.0 for NET4.0

IP Protocols: ICMP, UDP, TCP

IP: routing cache hash table of 512 buckets, 4Kbytes

TCP: Hash tables configured (established 2048 bind 4096)

IP-Config: Guessing netmask 255.255.255.0

IP-Config: Complete:

device=eth0, addr=192.168.2.202, mask=255.255.255.0, gw=255.255.255.255,

host=192.168.2.202, domain=, nis-domain=(none),

bootserver=192.168.2.44, rootserver=192.168.2.44, rootpath=

NET4: Unix domain sockets 1.0/SMP for Linux NET4.0.

RAMDISK: Compressed image found at block 0

Freeing initrd memory: 568k freed

EXT2-fs warning: checktime reached, running e2fsck is recommended

VFS: Mounted root (ext2 filesystem).

Mounted devfs on /dev

Freeing unused kernel memory: 72k init


init started: BusyBox v1.8.2 (2007-12-23 23:51:42 CET)
lcd.o: init lcd driver module

lcd.o: found KS0713/SED153X lcd interface





------ Extra Informations ------
Selected Network adapter: 3Com Megahertz (B) 10-100 LAN + 56K Modem (Ethernet) - Packet Scheduler Miniport (0)
IP-Adress of the Network Adapter: 192.168.2.44
IP-Adress of the Dbox: 192.168.2.202
Comport: Communications Port (COM1)
Operatingsystem: Microsoft Windows XP Professional Service Pack 2 (Build 2600)
CPU 1: Intel Pentium II @ 233 MHz
Filename of the Images: Andromeda V2.0 Nokia 2x.img
Imagetype: Two Flashs
DBOX-IFA Version: 3.0
------ Powered by http://www.dboxservice-hallenberg.de ------




TIA



Freddy
 
Last edited:
Yes, I have tried a number of different images, mostly backups from my other box, but i will try a few more "clean" original versions.

Do you have any suggestions on what images i should try which are known to be good on problematic boxes ??

I realise that this may not be an easy one to solve, its got me foxed, and need to be patient and hope some of the flashing / bootlog guru's can help :)


any other suggestions most welcome, hopefully its something simple and stupid I've missed !



cheers

Freddy
 
Last edited:
I used IFA 3.0 and Andromeda 2.0, an xover cable and I also tried it with an RL45 cable via my Router. I had no real problems during flashing or post flash. It is just important to make sure that you turn the dbox off and on at the correct moment in the flash process and also allow IFA to flash in your firewall. Turning the box off and on at the correct moment was the only thing I realised you can get wrong and it makes all the differnce.

My point being it was my 1st flash of a dbox2.
 
Due to the flashlogs there is no flash problem.
There is a problem at bootup time from the image at the box and that problem is only visible at a bootlog.
 
same problem to

i have exactly the same problem mate.have tried loads of images as well using xover cable.havent got a null cable so i cant get the boot log.cant eve get into settings of the box either so i dont even know the ip address of the box as it was given to me like this.it just boots like normal loading kernal then the image comes up then blank screen with just a faint green light.?
 
thanks for comments and suggestions

@mgb sorry it was a flashlog and not a bootlog, haven't had to do this before so a bit confused !

hopefully the attached file is what is required, this time just attached rather than posting as the thread gets quite long ( ive also tidied up the previous post a bit )



hopefully you can point me in the right direction ( from my untrained eye it looks as though there may be a problem with the avia chip ??? )

TIA

Freddy
 
avia_av_core: Starting avia_av_wdt thread.
avia_av: microcode verify: 4569 errors.

Something is wrong with the avia chipset.
Faulty chip or maybe faulty ram for the avia chip.
 
cheers mgb

if you had to hazard a guess what would be your best bet , the chipset or the ram.

When it boots it does show the andromeda loadup picture on the tv screen , does this give any clues ??

TIA

freddy
 
Freddy- whip the lid off your nokia and see if it's aVia500 or 600 chipped. These new images are supposed to load the right avia driver automatically. 600 driver works perfectly OK on a 500 nokia, but a 500 driver might cause mayhem on a 600 nokia...

Might be safer to try a pre-Christmas release image, where this has to be set manually? Cheers- AL
 
Hmmm- my nokia's are all aVia500, too. I've found they run perfectly no matter which avia driver is installed- 500 or 600. Which leads me to assume that the 600 driver is backwardly compatible on a 500 box.

But when I tried a backed-up 500 image on a 600 box- all hell broke loose! Draw your own conclusions from that...

I suggest you try the new NJLworld6.1 2x image, m8. If you get the same results with that, then I'm afraid I'll have to agree with mgb- you've got a hardware problem to sort out.

Cheers- AL
 
Thnaks Al,

Sort of resigned to the fact that its a hardware problem, and as mgb has said something to do with the avia chipset.

Looks like i can buy these so will probably take the plunge as i have colleagues at work who can do surface mount ( or so they say !).

You or anyone have any experience of replacing these and any pitfalls ??


TIA

Freddy
 
Never had to go down that road, m8 (Thank goodness!!). But before YOU do, it's not going to hurt trying another image first, is it? Takes one factor out of the equation...

Cheers- AL
 
Hi

Yes OK, have tried NJLWorld 6.1 , and a few more besides , but no go. Box either hangs on empty LCD screen ( faintly on) or goes back into standby.

me thinks unless i try to replace avia chips its a gonner :(


i see that i can get them ( used 100% tested) from http://www.d-box2.co.uk/, does anyone know of any other potential alternative sources ??


Tia


Freddy
 
Dbox2's seem to be VERY expensive... is there a major shortage of them? I upgraded to a couple of D500c Dreambox 12 - 18 months ago and DBOX2's could be picked up for £80 then!! I have 3 DBOX2's sat in the garage doing nowt at moment :-) One i had loads of problems with ages ago but i think the other 2 work... might have to get them out and play with them later and put em on the bay :-)

In my opinion m8 i would start to read the Dreambox section and maybe purchase one of those and a booster to replace the OLD expensive Dbox2..

Regards

q2
 
You must log in or register to reply here.

Similar threads

D
VU+ Duo Vu+ Duo Set up information
Replies
0
Views
2K
dannyparks
D
M
please help me
Replies
2
Views
2K
memo_79
M
M
help stuk on starting kernel
Replies
2
Views
1K
memo_79
M
V
VectorZ - report on setup and 29/03/2012 test
Replies
4
Views
2K
VectorZ
V
P
How to set up your new Vu+Duo. with ViX
Replies
2
Views
21K
cactikid
cactikid
Back
Top