https://www.eevblog.com/forum/testgear/siglent-ads-firmware-file-format/msg1870091/#msg1870091i have downloaded sdg1000x ads file but i am unable to flash it to my AWG...are there any additional steps to use it?
You mean this [telnet_SDG1000X.ADS]
This you can not flash at all. You do all like FW update with this file and SDG tell that it fails... do not care...do not shut off... just telnet and do what ever inside SDG system. If you do not know what to do there inside system and how... then please study first...yes it may take time to find all or if you find right place there can perhaps find all very detailed full instructions (it is like spring festival gift package what include all you need) what can use like blind (after you have telnet working) but be careful... it do not forgive any kind of typemistakes. Do not try..oops...try...oops iteration... because this method may lead you to real problems and nearly like "destroy" your SDG
And seriously, do NOT downgrade to semidanger factory original or "eevblog version" FW ....01P22 even if you find it somewhere because if bad happen and it goes to boot problem... it do not support USB recovery method.
But NSP_limit_data.xml is under config and not under firmware0.
mount -o remount,rw /dev/ubi2_0 /usr/bin/siglent/firmdata0
or
mount -o remount,rw /dev/ubi2_0 /usr/bin/siglent/config
But NSP_limit_data.xml is under config and not under firmware0.
You have full instructions in document "SDG1000X Modification instructions V33R1" what you have from zip package where is included exactly all. All commands, all what you need, even after pdf there is also plain txt file for use copypaste for commands. There is also one suitable terminal software and all other things needed. Why you did not read it *). You think that first muscle and after then brain. I recommend to do just opposite.
Read it all, and read it again because you have now jumped over important row. Yes @Orange give just also right one... but is it still better to read all instructions because there is also warnings what must not adjust and if there is not told some adjustment, then do not it just like "try this and try that and after then ...oops" method.
*)And I know you have not read it because you ask this question here.
But NSP_limit_data.xml is under config and not under firmware0.
You have full instructions in document "SDG1000X Modification instructions V33R1" what you have from zip package where is included exactly all. All commands, all what you need, even after pdf there is also plain txt file for use copypaste for commands. There is also one suitable terminal software and all other things needed. Why you did not read it *). You think that first muscle and after then brain. I recommend to do just opposite.
Read it all, and read it again because you have now jumped over important row. Yes @Orange give just also right one... but is it still better to read all instructions because there is also warnings what must not adjust and if there is not told some adjustment, then do not it just like "try this and try that and after then ...oops" method.
*)And I know you have not read it because you ask this question here.
Thank you,
wouldn't it have been easier to tell me what the mistake is than to review my possible way of operating?
I have already changed the version to SDG1062X.
The only difference is the firmware which is currently 1.01.01.33R1B6: is this the problem?
I think that in a forum we should help ourselves rather than being pedantic!
current mount points are:
rootfs on / type rootfs (rw)
ubi0: rootfs on / type ubifs (ro, relatime)
none on / tmp type tmpfs (rw, relatime)
proc on / proc type proc (rw, relatime)
sysfs on / sys type sysfs (rw, relatime)
mdev on / dev type tmpfs (rw, relatime)
devpts on / dev / pts type devpts (rw, relatime, mode = 600)
none on / sys / kernel / debug type debugfs (rw, relatime)
ubi1_0 on / usr / bin / siglent / usr type ubifs (rw, relatime)
ubi2_0 on / usr / bin / siglent / firmdata0 type ubifs (ro, relatime)
But NSP_limit_data.xml is under config and not under firmware0.
You have full instructions in document "SDG1000X Modification instructions V33R1" what you have from zip package where is included exactly all. All commands, all what you need, even after pdf there is also plain txt file for use copypaste for commands. There is also one suitable terminal software and all other things needed. Why you did not read it *). You think that first muscle and after then brain. I recommend to do just opposite.
Read it all, and read it again because you have now jumped over important row. Yes @Orange give just also right one... but is it still better to read all instructions because there is also warnings what must not adjust and if there is not told some adjustment, then do not it just like "try this and try that and after then ...oops" method.
*)And I know you have not read it because you ask this question here.
Thank you,
wouldn't it have been easier to tell me what the mistake is than to review my possible way of operating?
I have already changed the version to SDG1062X.
The only difference is the firmware which is currently 1.01.01.33R1B6: is this the problem?
I think that in a forum we should help ourselves rather than being pedantic!
current mount points are:
rootfs on / type rootfs (rw)
ubi0: rootfs on / type ubifs (ro, relatime)
none on / tmp type tmpfs (rw, relatime)
proc on / proc type proc (rw, relatime)
sysfs on / sys type sysfs (rw, relatime)
mdev on / dev type tmpfs (rw, relatime)
devpts on / dev / pts type devpts (rw, relatime, mode = 600)
none on / sys / kernel / debug type debugfs (rw, relatime)
ubi1_0 on / usr / bin / siglent / usr type ubifs (rw, relatime)
ubi2_0 on / usr / bin / siglent / firmdata0 type ubifs (ro, relatime)
Is it so that this do not work anymore?
mount -o remount,rw
(and then go to right folder)
I am thousands of km far from my workshop and can not check/test anything and not even sure know when can return, if can..
I have not made any attempt other than what is reported in the document.
Then I switched off it and after few seconds powered on, but with the usb key inserted.
Now it is freezed on logo
But NSP_limit_data.xml is under config and not under firmware0.
You have full instructions in document "SDG1000X Modification instructions V33R1" what you have from zip package where is included exactly all. All commands, all what you need, even after pdf there is also plain txt file for use copypaste for commands. There is also one suitable terminal software and all other things needed. Why you did not read it *). You think that first muscle and after then brain. I recommend to do just opposite.
Read it all, and read it again because you have now jumped over important row. Yes @Orange give just also right one... but is it still better to read all instructions because there is also warnings what must not adjust and if there is not told some adjustment, then do not it just like "try this and try that and after then ...oops" method.
*)And I know you have not read it because you ask this question here.
Thank you,
wouldn't it have been easier to tell me what the mistake is than to review my possible way of operating?
I have already changed the version to SDG1062X.
The only difference is the firmware which is currently 1.01.01.33R1B6: is this the problem?
I think that in a forum we should help ourselves rather than being pedantic!
current mount points are:
rootfs on / type rootfs (rw)
ubi0: rootfs on / type ubifs (ro, relatime)
none on / tmp type tmpfs (rw, relatime)
proc on / proc type proc (rw, relatime)
sysfs on / sys type sysfs (rw, relatime)
mdev on / dev type tmpfs (rw, relatime)
devpts on / dev / pts type devpts (rw, relatime, mode = 600)
none on / sys / kernel / debug type debugfs (rw, relatime)
ubi1_0 on / usr / bin / siglent / usr type ubifs (rw, relatime)
ubi2_0 on / usr / bin / siglent / firmdata0 type ubifs (ro, relatime)
Is it so that this do not work anymore?
mount -o remount,rw
(and then go to right folder)
I am thousands of km far from my workshop and can not check/test anything and not even sure know when can return, if can..
Not a problem.
You say:
mount -o remount,rw
but I think you missed the mount point /
so I try:
mount -o remount,rw /
and I receive this message:
mount: mounting ubi0:rootfs on / failed: Bad message
Iattached dmesg file: it could be an error in filesystem
But NSP_limit_data.xml is under config and not under firmware0.
You have full instructions in document "SDG1000X Modification instructions V33R1" what you have from zip package where is included exactly all. All commands, all what you need, even after pdf there is also plain txt file for use copypaste for commands. There is also one suitable terminal software and all other things needed. Why you did not read it *). You think that first muscle and after then brain. I recommend to do just opposite.
Read it all, and read it again because you have now jumped over important row. Yes @Orange give just also right one... but is it still better to read all instructions because there is also warnings what must not adjust and if there is not told some adjustment, then do not it just like "try this and try that and after then ...oops" method.
*)And I know you have not read it because you ask this question here.
Thank you,
wouldn't it have been easier to tell me what the mistake is than to review my possible way of operating?
I have already changed the version to SDG1062X.
The only difference is the firmware which is currently 1.01.01.33R1B6: is this the problem?
I think that in a forum we should help ourselves rather than being pedantic!
current mount points are:
rootfs on / type rootfs (rw)
ubi0: rootfs on / type ubifs (ro, relatime)
none on / tmp type tmpfs (rw, relatime)
proc on / proc type proc (rw, relatime)
sysfs on / sys type sysfs (rw, relatime)
mdev on / dev type tmpfs (rw, relatime)
devpts on / dev / pts type devpts (rw, relatime, mode = 600)
none on / sys / kernel / debug type debugfs (rw, relatime)
ubi1_0 on / usr / bin / siglent / usr type ubifs (rw, relatime)
ubi2_0 on / usr / bin / siglent / firmdata0 type ubifs (ro, relatime)
Is it so that this do not work anymore?
mount -o remount,rw
(and then go to right folder)
I am thousands of km far from my workshop and can not check/test anything and not even sure know when can return, if can..
Not a problem.
You say:
mount -o remount,rw
but I think you missed the mount point /
so I try:
mount -o remount,rw /
and I receive this message:
mount: mounting ubi0:rootfs on / failed: Bad message
Iattached dmesg file: it could be an error in filesystem
Oups... of course sloppy writer me... corrected now.
But how to go forward it need now some other peoples help who have access to SDG with latest FW or can find reason due to knowledge and or experience.
I have not made any attempt other than what is reported in the document.
Then I switched off it and after few seconds powered on, but with the usb key inserted.
Now it is freezed on logois there any recovery? or I have to do an RMA?
I have not made any attempt other than what is reported in the document.
Then I switched off it and after few seconds powered on, but with the usb key inserted.
Now it is freezed on logo
I have not made any attempt other than what is reported in the document.
Then I switched off it and after few seconds powered on, but with the usb key inserted.
Now it is freezed on logo
Sounds familiar if you boot with the telnet ads inserted. It seems to bricks instruments.
Thank you, I am happy it supports USB recovery
I wrote to Tautech.
What do you think?
what was the problem?
I read about SDG800 with this problem and it was hardware
Thank you, I am happy it supports USB recovery
I wrote to Tautech.
What do you think?Got your message.
You broke your SDG1kX playing with its file system but it can be recovered.Quotewhat was the problem?
I read about SDG800 with this problem and it was hardwareDifferent issue, we can recover all SDG800 now.
Contact info-eu@siglent.com and ask them nicely for the SDG1032X recovery package.
Probably there was a problem on file system before the hack.
After recovery sent by Siglent it works already fine.
what are the differences between 1032 (transformed into 1062) and the original 1062?
Why auto recovery is not already included inside system, just external reliable timer and when boot fails it do automatic recovery for weak up back to life. It is not even difficult or expensive.
what are the differences between 1032 (transformed into 1062) and the original 1062?
A sticker on the front panel that says "1032".
This is square wave @ 60 MHz