[superscipion]

0

    Dear all,
I really need your help: I try since days to flash an new image on my DM800 HD (which seems to be original version) after a "no CA found" message.
I use OptiFlasher V 2.0.0.5 only with serial cable
Image is Merlin-3_OE-2.0-drhg_SIM2_ssl84D_dm800_18-12-2013.nfi
PC is running with Win7 pro (all updates performed)
All first steps went well (including second boot loader) but when flashing, I am still there after 24 hours (finalising job phase 2).
Can you help?
Thanks in advance

[superscipion]

0

I forgot to write that SIM is 2.01
Sorry

[fairbird]

0

Follow this link
[Only registered and activated users can see links You are not allowed to view links. Register or Login to view.]
1-first flash last botloader ssl84D by using (Null modem cable only without Network lan) method
2-Then if you fixed (No Ca Found) you can flash any new image by using (Flashing by Network lan only)method
[Only registered and activated users can see links You are not allowed to view links. Register or Login to view.]

P.s:Must be have GOOD Null cable (Rs232)
Download last Bootloader for Your box SSl84D from attach...

[superscipion]

0

Hi Fairbird,
Nice to get in touch
I did point one using serial cable and I had no problem to flash ssl84D provided
Box is ok at the stage but when I restart (without serial cable and with or without network cable) keeping the power button engaged and pluging electrical socket to enter the stop mode, it well enters into STOP mode but giving me "DHCP" instead of an IP adress (192.168.1.77).
Your opinion?
Kind regards

[fairbird]

0

1-Turn power off from Box
2-Open Optiflasher
3-Click to Advanced (Select coma & Loader)
4-Click to Reset Bios Factory Settings
5-Click to Do Job
6-Turn power on to box
7-Let optiflasher finish job

Then you can use interface flashing by press and holding on front power button

[superscipion]

0

Hi fairbird
I followed the seven points above and at the end I received: "BIOS MODE SUCCESS & Bios Reset SUCCESS"
Then, getting out of Optiflasher I turned DM off the On holding the STOP button: display gave me again "DHCP" instead of 192.168.1.77
I started the whole process again (7 points) the I made a "Write Bootloder / update" using ssl84D you provided.
This times, it went through the two phases saying "Dreambox flashed successfully" an this time on the display I have stop mode and 192.168.1.77.
So Box seems to be ok at the stage but when I restart (without serial cable and with or without network cable) keeping the power button engaged and pluging electrical socket to enter the stop mode, it well enters into STOP mode but giving me "DHCP" again instead of 192.168.1.77.
So I am back to my starting point.
Your opinion?
Thanks in advance

[fairbird]

0

Of course if you make stop mode without lan cable will be get default ip.. Don't remove lan cable never...

is your router main ip adress on range : 192.168.1.x example : 192.168.1.1 or diffrent 192.168.x.x r an other one ?
if diffrent then for sure will not work then you will need a crossover cable connection

[superscipion]

0

I become a little bit "nuts"
I use a stand alone PC (Windows 7 pro) with a crossover cable connected to the DM
(PC has a fixed IP 192.168.1.14 with 255.255.255.0 no Gateway and no dns)
Using optiflasher, after the boot load everything is OK (display gives 192.168.1.77) I can ping the DM and access the DM web interface, leds on both network cards are blinking intensiveky exchange of data is performed,....
Just putting power off then on (with crossover and serial cables present and in Stop mode) I am back to that display DHCP.
Any idea?
Thanks for your patience

[fairbird]

0

Are you connected box with Pc directly? If yes, Then must be to set manually ip in box make DHCP = off and put Ip manually ...

[superscipion]

0

Hello Fairbird
I finally found the solution
I used an old router for which I set an IP of 192.168.1.1 with DHCP
Than I connected the stand alone PC on 192.168.1.3 and the DM gave me 192.168.1.2 as default adress. Both devices connected with standard cables and ..... anything ran well
So it seems that it was a pure network problem (I still don't know why because crossover cable was checked and working well)
Those are the mysteries of IT. Anyway thanks for your help, availability and support (I will make a donation soon).
This case can be closed