Dbox2 not booting up and unable to flash

[cgscott]

it was tried to start ten times in vain dbox from netzwerk. please uberprufen them try theirs netzerkkonfiguration. resetten them dbox fur a renewed one

but hopefully theres a german here to help you

something to do with network configuration me thinks

[peco]

Yeah sorry, I re-read it and pasted the same one twice, edited super quick though.

<--capa added 7 Minutes and 23 Seconds later...-->

Tried the Hyperterminal thingy but as you can see:

kdebug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.0 mID 01
debug: feID 7a gtxID 0b
debug: fpID 5a dsID 01-50.6e.ce.05.00.00-b9
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 16/16/08
WATCHDOG reset enabled
dbox2:root> debug:
BOOTP/TFTP bootstrap loader (v0.3)
debug:
debug: Transmitting BOOTP request via broadcast
debug: Given up BOOTP/TFTP boot
boot net failed

Flash-FS bootstrap loader (v1.5)

Found Flash-FS superblock version 3.1
Found file /root/platform/nokia-dbox2/kernel/o
debug: Got Block #0032

will verify ELF image, start= 0x800000, size= 154332
verify sig: 262
Branching to 0x40000


U-Boot 1.2.0 (Tuxbox) (Apr 7 2008 - 06:04:09)

CPU: PPC823ZTnnA at 67.200 MHz: 2 kB I-Cache 1 kB D-Cache
*** Warning: CPU Core has Silicon Bugs -- Check the Errata ***
Board: DBOX2, Nokia, BMon V1.0
Watchdog enabled
I2C: ready
DRAM: 32 MB
FLASH: 8 MB
Scanning JFFS2 FS: ......... done.
env: found "console"
env: found "baudrate"
env: found "lcd_inverse"
env: found "lcd_contrast"
FB: ready
LCD: ready
In: serial
Out: serial
Err: serial
Net: SCC ETHERNET

Options:
1: Console on null
2: Console on ttyS0
3: Console on framebuffer
Select option (1-3), other keys to stop autoboot: 0
### FS (jffs2) loading 'vmlinuz' to 0x100000
### FS load complete: 670086 bytes loaded to 0x100000
.................................................. ............. done
Un-Protected 63 sectors
## Booting image at 00100000 ...
Image Name: dbox2
Image Type: PowerPC Linux Kernel Image (gzip c
Data Size: 670022 Bytes = 654.3 kB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Uncompressing Kernel Image ... OK
kdebug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.0 mID 01
debug: feID 7a gtxID 0b
debug: fpID 5a dsID 01-50.6e.ce.05.00.00-b9
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 16/16/08
WATCHDOG reset enabled
debug: &_text 0x10000, &_etext 0x26160, &_data 0x26160, &_edata 0x29c50
debug: &_end 0x347dc, &__stack 0x400000
debug: Memory tests (0x400000 -- 0x1000000)
debug: NumberTest: debug: passed
debug: MarchTest: debug: passed
debug: PermTest: debug: passed
debug: Extension Memory tests (0x1000000 -- 0x2000000)
debug: NumberTest: debug: passed
debug: MarchTest: debug: passed
debug: PermTest: debug: passed
dbox2:root> DL 800000
unrecognized command DL, args[0][0] 0x44
dbox2:root> DL 800000 followed of
unrecognized command DL, args[0][0] 0x44
dbox2:root>

The first thing I am asked to type isn't recognised.

dbox2:root> DL 800000
unrecognized command DL, args[0][0] 0x44

[Fergal]

Your box is 16/16/08 its recognising this but unplug from the power and take the lid off you will see a memory expansion module its held in with a plastic clip (see piccie) either check its seated properly and or take it out and see if the box boots up without it in if it does try flashing it then pop it back in again.

[peco]

OK I'll give that a go and report back. I'll need to buy the little star screw drivers. Thanks to Fergal and everyone else who's helped so far.

[Fergal]

OK I'll give that a go and report back. I'll need to buy the little star screw drivers. Thanks to Fergal and everyone else who's helped so far.

You can use a small flathead screwdriver just jam it in between the center pin and use a pair of pliers to turn the screwdriver.

[peco]

You were right about the screw drivers. hehe

I took the lid of the box and check the memoery expansion module, but it was in pretty tight and secure. I unclipped it (removed it completely) and tried another flash but it didn't do anything different.

Keep the ideas coming if you have any more matey.

[Skiboy]

The one I done once when I had the same problem was putting it into a kein system state...that was I flashed using IFA a 1 x image...then a 2x image when it was showing kein system...worked a treat.


cheers

[peco]

I dont even know what that means mate. Can you explain more? Kein system and how to do it?

[Skiboy]

I dont even know what that means mate. Can you explain more? Kein system and how to do it?

sorry mate this not what you want to do, was trying to answer another query, not your's forget this advice.

cheers

[peco]

You were right about the screw drivers. hehe

I took the lid of the box and check the memoery expansion module, but it was in pretty tight and secure. I unclipped it (removed it completely) and tried another flash but it didn't do anything different.

Keep the ideas coming if you have any more matey.

Just a little refresh for the helpers out there that might have any other ideas?

[Skiboy]

Have you tried the new version of IFA 3.1.1 sometimes you have to keep powering the dbox off and on for up to 10 times but it should eventually take the image mate.


cheers

[Renwich]

From what I've seen around and about , being patient and keep flashing it may be the answer,

[smoggie]

have you tried flashing with the null modem cable only, like Fergal suggested?? it will take about 40 mins i think. well worth trying if you cant connect using crossover cable. rename the image u are going to use mtd3 and put in C: You will need the uboot file i have uploaded for here ........................Next click on Transfer on top of hyperterminal window, select "send text file", select type of file "All files", [/COLOR][/COLOR]select the file u-boot.mot (attached here) and click on "open" to start the transfer.
The file transfer take about 5 minutes and in hyperterminal no announcement appears about the process of the transfer.

[jitjunior]

The best way when the box is like that is to use null modem cable only, and using hyperterminal (if you're on xp i think it's only available in professional, not home edition) i know this from my own experience, i put laky pro on my box then after that it stuck at the loading kernel stage of boot. If you need a walkthrough just PM me mate i'll be happy to help out.

[peco]

Have you tried the new version of IFA 3.1.1 sometimes you have to keep powering the dbox off and on for up to 10 times but it should eventually take the image mate.


cheers

Yeah I've tried 3 different versions on IFA including the latest version above mate.

<--capa added 8 Minutes and 50 Seconds later...-->

have you tried flashing with the null modem cable only, like Fergal suggested?? it will take about 40 mins i think. well worth trying if you cant connect using crossover cable. rename the image u are going to use mtd3 and put in C: You will need the uboot file i have uploaded for here ........................Next click on Transfer on top of hyperterminal window, select "send text file", select type of file "All files", [/COLOR][/COLOR]select the file u-boot.mot (attached here) and click on "open" to start the transfer.
The file transfer take about 5 minutes and in hyperterminal no announcement appears about the process of the transfer.

Yeah mate I tried flashing using Hyperterminal as Fergal suggested. I downloaded his instructions and gave them a go. I can get into debug mode and the command prompt in hyperterminal comes up "dbox2:root" ok. But as soon I try the next step I get the error unrecognized command DL as below:

"dbox2:root> DL 800000
unrecognized command DL, args[0][0] 0x44"

So I decided to try using the uboot file you gave me ragardless of this first step not working but when I send text file the message in Hyperterminal is "Connection timed out". 5 minutes later the message appeard in a seperate box: "No response from the remote system", with an "OK" button to close it.

I should add that I can connect using a Null modem cable, (or at least the cable works ok).

Here's what the full Hyperterminal message says:

"kdebug: DDF: Calibrating delay loop... debug: DDF: 67.79 BogoMIPS
debug: BMon V1.0 mID 01
debug: feID 7a gtxID 0b
debug: fpID 5a dsID 01-50.6e.ce.05.00.00-b9
debug: HWrev X5 SWrev 0.81
debug: B/Ex/Fl(MB) 16/16/08
WATCHDOG reset enabled
debug: &_text 0x10000, &_etext 0x26160, &_data 0x26160, &_edata 0x29c50
debug: &_end 0x347dc, &__stack 0x400000
debug: Memory tests (0x400000 -- 0x1000000)
debug: NumberTest: debug: passed
debug: MarchTest: debug: passed
debug: PermTest: debug: passed
debug: Extension Memory tests (0x1000000 -- 0x2000000)
debug: NumberTest: debug: failed at 0x1ffffdc
debug: MarchTest: debug: failed at 0x1ffffdc
debug: PermTest: debug: passed
dbox2:root> DL 800000
unrecognized command DL, args[0][0] 0x44
dbox2:root>"

So frustrating.

<--capa added 13 Minutes and 44 Seconds later...-->

The best way when the box is like that is to use null modem cable only, and using hyperterminal (if you're on xp i think it's only available in professional, not home edition) i know this from my own experience, i put laky pro on my box then after that it stuck at the loading kernel stage of boot. If you need a walkthrough just PM me mate i'll be happy to help out.

Yes I'm on XP Pro matey and I'd love a walk through but I fear, as you will read above, that I'll not get past the first part. Unless you can think of something?

<--capa added 16 Minutes and 59 Seconds later...-->

"The message appears
S record load, offset: 800000"

If DL is typed in lower case!! "dl 800000" works.. You maybe want to update those instructions Fergal matey.

Unfortunately though it still timed out after doing the send file uboot thing.

Is the protocol at the sending file stage supposed to be set to "Zmodem with crash recovery"? As there are a few other options in there...