Products > Test Equipment
Siglent .ads firmware file format
<< < (63/85) > >>
janekivi:
Header checksum is calculated differently.
Previous one depends from data length. Short data has bigger checksum
and larger data has smaller. Like 277 byte text file has FF FF B9 BA and
40 Mb file CE C2 02 7B, 50 Mb 77 1D AD 8B...
So, to get 00 1C 9F BC ?
n3mmr:

--- Quote from: janekivi on June 13, 2018, 05:28:26 pm ---Replacing the shadow file wasn't very hard to do so let's test this method

SDS1004X-E_OSV1_EN_eevblog.zip

--- End quote ---

That file was on some free server, and is gone.

Is the same file available elsewhere???

Or is there a substitute that might be better to use??
ebastler:

--- Quote from: tv84 on October 04, 2018, 09:02:12 pm ---How to open a telnet session in a Siglent when the root password is unknown?

Use the following scripts, according to each equipment.
They provide a root session via port 10101.

--- End quote ---

Sorry to come back to this old post. (And thank you for posting, tv84!) I am obviously to stupid for this...

I copied the SDG2000X.ADS from the above post to a USB stick, inserted into my SDG2042X, activated the LAN interface and DHCP.  But:

* Port 10101, as indicated by tv84, does not work. Port is not open, "connection refused".

* I can get a telnet prompt via the standard port 23, and it comes up with "SIGLENT SDG project". I believe that's different from the standard prompt, so the ADS script seems to have been activated? But I can't log in; the root/eevblog credentials do not work.
Where did I get this wrong?
Thanks for your help!

EDIT:

Duh, figured it out... The .ADS file is not loaded automatically upon insertion of the USB stick, or upon booting the SDG with an inserted stick. One has to explicitly trigger a "firmware update" via the system menu. The SDG will state that the update failed, but subsequently it does have port 10101 enabled. No credentials required for a telnet session on that port.

I fooled myself be believing that the "SGD project" headline had appeared only after I inserted the USB stick, but apparently that's bog standard...  I'll keep my post here anyway, in case someone else falls into the same trap and starts Googling for help...
tv84:

--- Quote from: ebastler on April 13, 2019, 04:58:09 pm ---Duh, figured it out... The .ADS file is not loaded automatically upon insertion of the USB stick, or upon booting the SDG with an inserted stick. One has to explicitly trigger a "firmware update" via the system menu. The SDG will state that the update failed, but subsequently it does have port 10101 enabled. No credentials required for a telnet session on that port.

--- End quote ---

 :) How did you figure it out?  (That is the most educational part that you can leave here... )

ebastler:

--- Quote from: tv84 on April 13, 2019, 06:46:28 pm --- :) How did you figure it out?  (That is the most educational part that you can leave here... )

--- End quote ---

I started to doubt my recollection that the "Siglent SDG project" headline had only shown up after I had inserted the USB stick. (I had tried a "plain" Telnet session before, but had not taken screenshots or notes.) So I doubted whether I could really be sure that your modification was actually activated.

And then, shame on me, I actually read the manual (on how to perform a firmware upgrade)...  ;)
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