I had more time so I made some research on the behavior of my 1202D.
power ON is OK
booting, Voltcraft logo appears
then scope usual screen appear
CH1 MENU, MATH Menu, CH2 MENU, AUTO SET and RUN/STOP lit but no response for single pus on buttons or selecting a function.
Seems to be the device hangs.
Although it does not work but a bit of life is in it (behind the scenes)
E.g. if I push a function button and keep it a bit longer time the corresponding function screen appears.
Also if I touch nothing osmetimes the device changes screen/function on its own.
Another interesting thing is if I connect a memory stick the system is recognise it, the disk icon appears on the top of the screen and even I was able to use the 'Update' menu of 'UTILITY' and I have successfully updated the firmware.
Unfortunately after the update then reboot the device behavior is the same as I described above.
Another thing what is working that is the boot menu.
With the booting cycle(ON/OF then ON again) the system recovery menu appears and I can start the system recovery function.
It is finishing well but unfortunately the device behavior is same as before.
like the next step I wanted to connect to the device on UART to see if I can access the operating system or not.
To do this was needed to find UART RX/TX pin inside the device. After a while I found them. See the attached picture.
I have connected an USB-Serial converter then via a terminal emulator was possible to access the system (connection speed 115200bps)
eg unix LS command is OK (see picture #ls)
See terminal screen after booting the scope (see attached)
So operating system on the device seems to be operational.
At this point if I use a function or menu button (push shortly) nothing happen on the terminal but if the push it longer (2-3 secs) some corresponding sequence appears on the screen.
Eg if I push CH1 MENU button shortly noting can seen, but If I keep it pushed longer then on terminal I can see this:
"t_unscan_wave_vertic_operate:ch0:5, 5
factor:chid0, vb:5, pos:0, factor:1.088000
Disp_SyncChOnOff:in
yt_unscan_wave_vertic_operate:ch0:5, 5
factor:chid0, vb:5, pos:0, factor:1.088000
Disp_SyncChOnOff:in
yt_unscan_wave_vertic_operate:ch0:5, 5
factor:chid0, vb:5, pos:0, factor:1.088000
Disp_SyncChOnOff:in
yt_unscan_wave_vertic_operate:ch0:5, 5"
Well, based on above finding I think my scope is not totally dead, but unfortunately I do not know what can/should I do with it to get back a functional device.
Is the problem whether hardware or software related?
If somebody has idea please tell me.
Thank you