| Products > Test Equipment |
| Siglent .ads firmware file format |
| << < (32/85) > >> |
| SMB784:
--- Quote from: BillB on July 01, 2018, 02:58:46 pm ---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. --- End quote --- Alright here's what my process was before failing to get login credentials correct: The first thing I did was format my 32 gigabyte USB flash drive to FAT32. Then I added the FW 7.1.6.1.25R2.ads file to the usb drive, dismounted it, and plugged it into the scope. I turned the scope on, and then followed the instructions to install the firmware and self calibrated the scope. I verified that I was running the 25R2 firmware at software level 0 (no software update performed yet). Then, according to RF-Loop's instructions: --- Quote ---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. --- End quote --- I downloaded the latest software update from the siglent website and put the 4 software files on a newly FAT32 reformatted USB drive. I turned off the scope and plugged the USB drive in. I then booted the scope, and it installed the software, and verified that I was now running at software level 1. Then I turned the scope off, took out the USB, reflashed it with the 4 custom files with the modified root login, plugged this back into the scope, started it up and let it return to the main screen. I then tried to telnet into the scope on port 23, I got to the login page and entered the username root and the modified password and received a "login incorrect" message. I tried many different combinations of login name and password, as well as the correct password numerous times. I rebooted the scope, tried reinstalling the modified software, tried reinstalling the 25R2 firmware, all to no added effect. I noticed that the boot time to main screen remained the same regardless of what software file I put on the USB, and regardless of whether or not there was even a USB inserted (20 seconds regardless). These times were measured after the initial official software boot. I can try instaling the 25R1 firmware and retrying this whole process, but I cannot seem to find a good download location for it. Also I have tried to hardware reset the scope using the instructions on the Siglent website, but that process has not worked each time I have attempted it. 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. |
| BillB:
--- Quote from: SMB784 on July 01, 2018, 04:26:27 pm ---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. --- End quote --- The OS update after turning on the scope is very fast, and it definitely worked the first time because you did bump from version 0 to 1. As far as the order of update, my scope had both the 25R2 and V1 factory updates applied for a while before I updated with the modified OS. My process went like 25R1->25R2->OSV1(factory)... a week or two later... ->OSV1(modified). So, I'm at a loss now to explain why you aren't able to log in. :-// |
| SMB784:
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 |
| SMB784:
I wonder if it is possible to do the update using the update configuration key. Anyone have any experience with this? |
| rf-loop:
--- Quote from: SMB784 on July 01, 2018, 07:04:35 pm ---I wonder if it is possible to do the update using the update configuration key. Anyone have any experience with this? --- End quote --- 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 |
| Navigation |
| Message Index |
| Next page |
| Previous page |