Products > Test Equipment
Hantek DSO1152S - Wont boot after firmware update
<< < (10/26) > >>
tinhead:
regards pictures, thank you very much!. Sure, when you have time you can uplaod higher res somewhere. It would be cool if you would try to check what numbers/name/logo on these ICs in attachement.
tinhead:
i've checked your pictures and it seems that you have hardware revision hw1.00.1 and not hw1.00.4, like on current "S" models:

https://www.eevblog.com/forum/testgear/hantek-tekway-dso-hack-get-200mhz-bw-for-free/msg433286/#msg433286

On your PCB the date is 2012-04, so that really old one. I remember Hantek introduced S models long time ago, but i never ever saw any from that time, you the first one. On hw 1.00.4 they improved the PCB a bit (moved some passive parts to top, isolation clearance better on DMM, smaller LAN IC), howeve the funtion should be the same.
othello:
The CRC warning he gets, could that mean some kind of corruption is in their firmware for that model causing these problems ?
rob77:

--- Quote from: tinhead on July 13, 2014, 01:57:10 pm ---
--- Quote from: WanaGo on July 13, 2014, 01:05:21 pm ---Have no idea what that does, but I tried it, and the scope ran

[root@Hantek /]# ./dso.exe > /dev/null 2>/dev/null < /dev/null &
[root@Hantek /]# s3c2440_clkcon=00FFFFF0
s3c2440_clkcon=00FFFFF0
save exit: isCheckpointed 0


--- End quote ---

well yes, when started manually it will run, but not when started from rcS. It looks like the dso.exe from 2.01.1_(140408.0) is not initializing properly when runned from rcS (i can't connect via USB to my dev board, so it deos NOT run properly). When killed and started manually it does works. So there must be general problem with that executable version.


--- End quote ---

apparently yes, the binary is broken.. tha's why i suggested to daemonize the executable from shell.
my guess is that when running from a tty - it's in some kind of "debug" mode - dumping messages to the tty . and the guys messed up the binary and it doesn't turn itself into a daemon properly when started from initscript - therefore doesn't run from init scripts.
if it works ok when redirecting stdout, stderr and stdin descriptors (the workaround i suggested), then the "solution" is just to modify the startup script (add the redirections to /dev/null) and wait for a new version from Hantek.
tinhead:

--- Quote from: othello on July 13, 2014, 03:48:44 pm ---The CRC warning he gets, could that mean some kind of corruption is in their firmware for that model causing these problems ?

--- End quote ---

the "*** Warning - bad CRC or NAND, using default environment" can be ignored, it does not have anything to do with firmware but only with env for bootloader.
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