Products > Test Equipment
Hantek DSO1152S - Wont boot after firmware update
<< < (24/26) > >>
WanaGo:
Got the tool, thanks for the PM Peter. I couldnt reply to you though, i seem to be 'blocked' from doing so.

Has anyone attempted to edit the /disp file to modify the logo?
Any success?
WanaGo:
I had just spotted that too, thanks.
So ive made the logo (640x480 in my case, 24 bit etc), made the ebm file with the tool, and now to do the disp stuff.
I have the disp file on the computer, but unsure exactly what I am looking for to find this offset, and also how to split the file. I am guessing this is to make the disp1 and disp2 files from the original disp?
Is there any information on that part available?
Thank you
WanaGo:
OK, figured it out.
The information for the DSO1152S didn't seem to work which is strange, so here is what I found out. No doubt a reason why.

Instructions stated it was to be 24bit BMP, turns out this needed to be 16bit BMP. 24bit was too large.
DSO1152S is 640x480, compared to the example which is 800x600 (but it did state this needed to change).
Inside the /dso/app folder on my machine, is nothing but dsod and dsod.old files, there is no disp file in there. disp is only found in the root folder /.

The tool required disp1 and disp2, which then get combined around the ebm file to form the new disp file.
Comparing disp1 with my original disp file, part 1 ends ~ 0xb10 in with 0x0100 0x0200, so the equivalent in my file is at 0xb04.
Comparing disp2 with my original disp file, part 2 starts ~0x96b04 with '/dev/fb0, just fount the equivalent in my file which is at 0x96b04 too.
Therefore the 'ebm' is  0x96000 long, which corresponds to a 640x480x2=614400 ebm.
In the Image2Lcd tool, there are actually 2 options for 16bit. Initially, I selected the 2nd one which resulted in a 900KB file (9821600 bytes) which I think was actually 24bit, and then I selected the first one which resulted in a 600KB file (614400 bytes) which was correctly 16bit.
Combined them together resulting in a 608KB file the same as the original. The 24bit file resulted in a corrupt startup image and simply didn't work.

I uploaded the file to /dso/app and nothing happened. Uploaded to / instead, and boom, the new logo appears. Lovely.

Old and new images attached for reference.
WanaGo:
Yes, spot the typo :)
WanaGo:
The next part of the puzzle is the EEPROM contents.

Using Tinheads utility instructions from here: https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg467313/#msg467313

I firstly had a look at the i2c.log file on the / folder of the scope.
It is essentially blank. Anyone know why?

Die Datei '/i2c.log' wurde gelesen. Größe: 8192 Bytes

Die ersten 256 Bytes:

00000| 00 00 00 9F 03 00 00 00 00 00 00 00 00 00 00 00 |................|
00010| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00020| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00030| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00040| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00050| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00060| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00070| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00080| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
00090| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000A0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000B0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000C0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000D0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000E0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
000F0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

Die letzten 256 Bytes:

01F00| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01F10| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01F20| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01F30| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01F40| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01F50| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01F60| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01F70| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01F80| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01F90| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01FA0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01FB0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01FC0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01FD0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01FE0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|
01FF0| 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 |................|

Carried on anyway. Connected with USB and connected the Tool, and all the options were 'default', nothing specific looking for my scope at all.

My PCB is my scope is 2012 dated and is Revision 1.00.1 yet is a DSO1152S. HW version is 10010x555583e8.
Based on the Version file, selecting 1001 in the tool would be the wrong move. It suggests 1002 and 1004 are checked for by the firmware. Does anyone have any suggestion as to what mine should be?
My Serial number is DSO06000xx, so is well above the 15000 threshold, even though its 2012 dated. I purchased it in 2013.

I set the Language to English etc and clicked the write button for the centre section, hoping that it might trigger the scope to update the i2c.log file just from having the language items updated, however nothing happened. In the text box to the right of the tool, it came up with 'failed' shortly afterwards. Wondering if my model is just odd and the EEPROM is somehow different...?

The end game is to try and install the SD and Video functions. I have LAN by default already installed and working.

The next question is where do you obtain the video files to put on the SD card in the first place? I cannot find information on this yet.
Does the card have to be a specific capacity and format?

Another question is around the LAN IP address. Every time I power cycle the scope, my IP address is reset back to default. Is this normal? Is there any way to have it remember the IP address, as its a pain in the butt.

Thanks
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod