Thank you, but I think my main question has to do with how you log in as root. I assume there is a root password, and I'm under the assumption that it is not something known it easily guessed, so how do I install the software update so that I can either know or set the root user password?
SMB784, are you asking how you interface with the unit? You'll need to telnet into the device through the ethernet connection. As rf-loop said, it depends what your current firmware version is. This determines the path you need to take. The firmware is upgraded by copying files to a USB flash and following the on-device menus.
Once you have an updated firmware, you need to load the special OS build found in the message that rf-loop mentioned in B above.
It sounds like all you need is the password for the modified firmware! Most of these modified firmware files for the Siglent devices floating around on this forum all us the same password. The author who posts on this forum likes to make sure that the forum users who download the files from this forum are regular forum users who've been around on this forum for a while. See these other forum posts:
https://www.eevblog.com/forum/testgear/siglent-sdg1000x-waveform-generators/msg1447972/#msg1447972
https://www.eevblog.com/forum/testgear/siglent-sdg1000x-waveform-generators/msg1449465/#msg1449465
It sounds like all you need is the password for the modified firmware! Most of these modified firmware files for the Siglent devices floating around on this forum all us the same password. The author who posts on this forum likes to make sure that the forum users who download the files from this forum are regular forum users who've been around on this forum for a while. See these other forum posts:
https://www.eevblog.com/forum/testgear/siglent-sdg1000x-waveform-generators/msg1447972/#msg1447972
https://www.eevblog.com/forum/testgear/siglent-sdg1000x-waveform-generators/msg1449465/#msg1449465
Well, I tried the very same password that logs me into the website in the first link of your message, and it tells me that it's wrong. The user name is root, and the password is the same one as the one that logs me into that website, and it says that the login credentials are wrong.
This leads me to believe that the custom software update is not being applied correctly for some reason.
Hmmm... that's the right one. The credentials are changed through the modified OS update file, rather than the App firmware update.
https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg1606243/#msg1606243
As rf-loop described in A. Load the standard SDS1004X-E Firmware (4-Channel Model) - 6.1.25R2 (Release Date 06.29.18 ) file, then the modified SDS1004X-E Operating System-V1 (Only For 4-Channel ) (Release Date 06.26.18 ) from the post listed.
Update latest FW and OS (if not already out from box).
SDS1004X-E Firmware (4-Channel Model) - 6.1.25R2 (Release Date 06.29.18 )
SDS1004X-E Operating System-V1 (Only For 4-Channel ) (Release Date 06.26.18 )
These both can download from Siglent official side. Inside these both packages (zip) there is also instructions.
Its possible that they have invalidated this method of changing the root user login when you install the official software update first, so at this point it is my suggestion that anyone attempting this process install the modified software provided here on the forums instead of trying the official software update.
Any suggestions are most welcome.
I wonder if it is possible to do the update using the update configuration key. Anyone have any experience with this?
I wonder if it is possible to do the update using the update configuration key. Anyone have any experience with this?
Your screen image
Is it displaying all files in your USB in root folder for OS update.
AFAIK There need be 4 files! included in eevblog zip
devicetree.dtb
rootfs.cramfs
sds1004x_e_udiskEnv.txt
uImage
Here is an image of the system info
Alright then, I must be doing something wrong. I am going to scrutinize this process in detail and maybe I can figure out what I have done wrong
Its possible that they have invalidated this method of changing the root user login when you install the official software update first.
Any suggestions are most welcome.
Its possible that they have invalidated this method of changing the root user login when you install the official software update first.
Any suggestions are most welcome.
No, the work being done by forum members has been on the latest firmware and os versions from what I can tell. Post one of your telnet sessions (including initiating the telnet connection) so we can see that you are connecting correctly. Also it might be useful to have a screenshot of the IP configuration screen on the scope. Are you able to connect to the webserver on the scope through your browser?
Its possible that they have invalidated this method of changing the root user login when you install the official software update first.
Any suggestions are most welcome.
No, the work being done by forum members has been on the latest firmware and os versions from what I can tell. Post one of your telnet sessions (including initiating the telnet connection) so we can see that you are connecting correctly. Also it might be useful to have a screenshot of the IP configuration screen on the scope. Are you able to connect to the webserver on the scope through your browser?
He sees the login prompt.
I get that he thinks he is. But without knowing his comfort level with the command line I would prefer to see proof to be able to rule it out. If he swears that the firmware has been installed correctly, and he is for sure using the correct username and password, then the next thing to check is that he really is connecting to the scope. I agree that it does sound like he probably is, but I've seen telnet connections fool other users before (as in they were at the telnet prompt, but not actually connected to anything).
On a separate note, thanks for your contributions in getting this process worked out.
Edit: I don't mean the first line as an insult. smb784 specifically mentioned earlier that wasn't completely sure was using telnet correctly, and I really have seen telnet connections trick people before.
Everything you are doing looks correct to me, sorry, I'm out of ideas.