dm800 boot loop after image upgrade

hi all,

i have a dm800 clone sim2.01 with ssl84d
after trying to upgrade to:
TSimage-3.0-OE-2.0-dm800hd-2014-09-28-ramiMAHER#ssl84D
the unit stuck in boot screen for a few minutes than reset and so on,

1. tried another image flashing - no good,
it seems i can still flash over the LAN interface properly,

2. tried PSU off for a few minutes/over night - no good,

3. Removed tuner - no good,

Dream-up
tried to connect an RS232 cable with Dream-up but the Dream-up doeskin recognize the unit,

i understand i need an RS232 null cable and that is what i used,

in order for the Dream-Up to recognize DM800 do i need both LAN & RS232 connected or RS232 is enough and the LAN is for image flashing later?

does somebody happens to know what are the working setting of the COM port in order to communicate with the DM800?
Speed/115200?
Data/8?
Parity?/no
Stop bit/1?
Flow Control/(no)/(xon/xoff)/(hardware)?

Or any ideas at all?

BR
Shambi

hi
thanks you very much for your reply,
do i need to use some special setting inside the optiflasher GUI?
* do i have to register the ProKey?
BR
Shambi

hi
used optiflasher 2.0.0.9 with one of the images recommanded - no news - same
BR
Shambi

ok i did it, the new bootloader drivers i flashed using the "write bootlaoder/update" checkbox
still - no luck
LCD shows:
".4-dm800.gzux-2.6.18-"
something like that,
* mabye i shuold go to the DreamUp option?
BR
Shambi

- - - Updated - - -

hi
why is the repair/no CA found option is not possible in optiflasher GUI?
BR
Shambi

to flash the bootloader using the optiflasher "write image" or "write bootloader" checkbox?
Thanks Shambi

ok
tried - no improvement
it seems it gets stuck right after starting to run,
it writes booting it writes the " ".4-dm800.gzux-2.6.18-" and i think get stuck in the middle...
mabye that is the reason it doesnt connect to DreamUp, it simply stops running after the start of boot,
it shows bootlogo --> than halts --> than reboots after a few minuets --> bootlogo -->....
BR
Shambi

hi
an update,
succeeded to connect with DreamUp but i didnt burn with Dreamup cause it takes a lot of time,
i do not know if burning using Dreamup will fix the problem,
used 76D SSL and image with no luck
operated Dreamup bad sectors fix - no improvement,
i'm attaching the simple log file i recorded from the COM1/RS232 terminal when the unit wakes up from power-on and get stuck,
i still can perform various flash image programming using the LAN interface,
BR
Shambi

hi
i got the satdreamgr tools
when i try to activate the no ca error
it returns a "no such file"
also why is the nocaerror valid in optiflasher ?
can someone review the log and see if he can point the problem or malfunctioning component ?
br
shambi

hi
performed no ca error fix ith yassinov NCF V3 with SSL82b --> flashed SL84D image --> no luck
can you understand from the log file what does it imply

"find_inode failed for name=secondstage.conf
load: Failed to find inode
- failed to open /boot/secondstage.conf
- failed to open /cf/autorun.bat"

what is the unit looking for or what is malfunctioning due to the above log error?
BR
Shambi

- - - Updated - - -

does flashing an image using the dreamup has any edge over the lan flashing method to solve problems?

thanks again for your help,
what is b4?
i can make no ca error on 84b,

if i understand your 2nd suggestion is:
flash ssl82 image[eighty two]
fladh ssl84b boot[eighty four]
than any 84d image ?[eighty four]

not must the no ca error procedure?

br
shambi

- - - Updated - - -

i wonder if from the log file you understand the cpu doesn't recognize the tuner ?

so to flash ssl82b boot
flash ssl84 image ?
can u explain what r the errors in the log file means?
br
shambi