dd conv=noerror,sync if=/dev/mtdblock7 of=/usr/bin/siglent/usr/mass_storage/U-disk0/mtdblock7-P0707.imgDimitar,
this may be an indication for a bad block in your NAND FLASH. That's actually not uncommon, the same as you (almost) won't find hard disks without bad blocks, yet they are automatically remapped inthe HDs. The OS should hide the bad blocks in NAND memory as well, yet, since "dd" accesses the raw data of the chip, errors may appear. To read the partition, you may try the commandCode: [Select]dd conv=noerror,sync if=/dev/mtdblock7 of=/usr/bin/siglent/usr/mass_storage/U-disk0/mtdblock7-P0707.img
I'm not sure if this switch works on the DD version implemented in the SSA3000X since I haven't got a machine with bad blocks to test. In case you need to restore your machine, you should be fine as long as you write back the original file as "dd'ed".
Cheers,
Thomas

...
The chip you get for a few bugs at digikey.
...
Hi Gents,
OK, so in case of bad blocks we don't have a way to backup at the mtd level.
Has anyone managed to reflash some MTD partition from uboot?
Has anyone managed to reflash an UBI volume from uboot?
Do you know what nand flash chip the Analyzer is using (if I have to replace it)
Are only those two directories unique as per instrument
/usr/bin/siglent/firmdata0
/usr/bin/siglent/usr/backup
Do we know where the update script is located for 7.07?
I want to check what it does so eventually get some idea what can happen.
I hope I will not need all this info but knowing me I will update to 8.01 soon
Sorry for the long questions list and thank you in advance!
Dimitar
Hi rf-loop,
Yes you are perfectly right. I am just such a kind of person who tries so solve his problem himself if possible. (often it is better for the nature)
Keep also in mind that if I have to send the instrument back for repairmen it means 1 month without it right?
Take into account we already have MT29F2G08ABAEAWP in stock and we have facility to replace it if necessary.
If I know that reflashing wouldn't take me much time I will go to this option for sure.
But as far as i understand no one has done it yet?
In addition I thought talking about my Analyzer here may be interesting for somebody else.
Hi Gents,
OK, so in case of bad blocks we don't have a way to backup at the mtd level.
Has anyone managed to reflash some MTD partition from uboot?
Has anyone managed to reflash an UBI volume from uboot?
....
Anyway, we've got complete NAND images of F/W 7.03 and 8.01 in the "community" so what's really important is to back up the configuration and calibration of your machine (on a FS base) since this is individual to each SA. If you need other images that are common to all machines, there will be a way to help.
All the best,
Thomas

I agree, the calibration is important.
In this respect can someone confirm(or share some thoughts) that those two directories contain all the unique data for a given Analyzer?
/usr/bin/siglent/firmdata0
/usr/bin/siglent/usr/backup
As per the update I did a quick check and the update is happening calling functions from /usr/lib/siglentlib.sh
Probably "check_and_upgrade()"
So basically they just do "nandwrite mtdN image" from linux. In theory nandwrite is bad block aware, so I and other having bad blocks should be OK.
But I will cross fingers when I do my update
bad block.
calibration is important.
Quote
bad block.
I have updated equipment what have this situation and in this case not any problem.
QuoteQuote
bad block.
I have updated equipment what have this situation and in this case not any problem.
Oh rf-loop, this is very relaxing!
How do you know you have bad blocks, partition dump from using dd command?
Was your bad blocks on the mtdblock7/rootfs?
Thanks


1. This firmware must be upgraded from V1.2.8.1 or later. If your SSA3000X has an earlier version, please to V1.2.8.1 first and then proceed to uplate to the latest version.
2. Add socket/telnet-scpi, you can operate remote control through LAN port without NI-VISA installed. Please check SSA3000X Programming Guide for more details.
3. Change two limit lines in different colours.
4. When quit from TG, stay in“Auto”sweep.
5. Lower some spurs when FFT.
6. Improve the stability.
V 1.2.8.2 is out. Who will be the 1st to try???
http://siglentamerica.com/prodcut-gjjrj.aspx?id=5113&tid=227&T=2
V 1.2.8.2 is out. Who will be the 1st to try???
http://siglentamerica.com/prodcut-gjjrj.aspx?id=5113&tid=227&T=2
Thanks for the info!
Download doesn't work atm, so I can't!