Buyer Beware: Siglent Electronic Load - Page 1
Forum section: electronics / testgear

author: digby70
author_rank: Newbie
timestamp: June 23, 2021, 01:15:22 am
content: I purchased a Siglent SDL 1020X-E Electronic Load 3 weeks ago. Upon receiving the unit, I attempted to upgrade the firmware.This upgrade failed and the display gave me multiple error messages (see attachment.). In addition the unit did not function at all.I returned the unit to the place of purchase and they sent me another Siglent SDL 1020X-Eand I tried again to upgrade the firmware butexperienced the same problem. This makes me doubt the quality of their products. I am now wondering if others are having problems withSiglent test equipment as I was going to purchase a spectrum analyzer from them.

author: TheDefpom
author_rank: Frequent Contributor
timestamp: June 23, 2021, 01:20:01 am
content: I have the same load and updated the firmware without issue, it is certainly an interesting issue.

author: digby70
author_rank: Newbie
timestamp: June 23, 2021, 01:28:32 am
content: I reported the incident to Siglent and they are looking for a solution.

author: james_s
author_rank: Super Contributor
timestamp: June 23, 2021, 01:39:48 am
content: I suspect it's defective. Getting a bad one straight out of the box is not unheard of, it even happens with the big guys like Fluke, Tek and Keysight once in a while.

author: mindcrime
author_rank: Unknown
timestamp: June 23, 2021, 01:43:24 am
content: To be fair to Siglent, I wouldn't rush to judgment knowing that pretty much every manufacturer on the planet has had some variation of a similar problem at some point in time. The software / firmware industry in general is not particularly competent at shipping quality software (and I speak as someone who has been writing software for 20+ years). Software is hard and everybody screws it up at some point in time. I'd give them a little time to research it and get back to you before judging them as "low quality" in general (relative to the rest of the industry that is).I'm sure Keysight, Rohde & Schwarz, GW Instek, Rigol, Fluke, Yokogawa, Keithley, Tektronix, etc., etc., etc. have had their share of machines over the years where a firmware update failed.

author: tautech
author_rank: Super Contributor
timestamp: June 23, 2021, 02:53:49 am
content: Quote from: digby70 on June 23, 2021, 01:15:22 amWelcome to the forum.Good on you for coming here and having a bitch however what you have offered is a lot short on detail.Which FW version upgraded from to which version ?Source of FW files used to upgrade ?What instructions did you use for FW installation guidance ?

author: TurboTom
author_rank: Super Contributor
timestamp: June 23, 2021, 08:36:54 am
content: Did the electronic load work ok out of the box before the firmware update attempt? I'ld always recommend to check general function to be sure a product is working as it's supposed to before applying any updates or modifications (should be common sense actually...).

author: digby70
author_rank: Newbie
timestamp: June 23, 2021, 03:53:03 pm
content: Yes, the unit worked fine before the attempted upgrade.As far as detail, my purpose for the post was not to "bitch" but merely provide general information. Particular details were provided to Siglent USA.

author: digby70
author_rank: Newbie
timestamp: June 23, 2021, 05:05:53 pm
content: Problem solved: I was using a Verbatim 16 GB flash drive to upgrade the firmware but the upgrade failed. Upon switching toa Cruzer 2 GB drive allowed the unit to complete the firmware upgrade successfully (both of these drives do work in my PC and laptop).

author: james_s
author_rank: Super Contributor
timestamp: June 23, 2021, 06:02:38 pm
content: It's possible the instrument just can't deal with large drives, >2gb is a common barrier when working with devices that are either older or based on a microcontroller rather than a full fledged PC.

author: kcbrown
author_rank: Frequent Contributor
timestamp: June 23, 2021, 09:10:10 pm
content: Quote from: digby70 on June 23, 2021, 05:05:53 pmThis is clearly a bug in the firmware update mechanism, either on the software end or the hardware end. A failed upgrade shouldnevercompromise the device. Flash memory is so cheap these days that there's absolutely no excuse for the device to not have enough to store both the pre-upgrade boot image and the upgraded one, so that boot from the pre-upgraded one would happen in the event the upgrade fails or is incomplete. Verification of the upgraded version in flash is an obvious required step, as is integrity checking the firmware image copied from the USB drive prior to installation of it, as is not changing which of the two boot images the device will boot from until after the installation has been completed (thus guaranteeing that in the event of a failure or interruption, the device will boot from the pre-upgrade image).I would suggest registering a bug with Siglent on this.

author: james_s
author_rank: Super Contributor
timestamp: June 24, 2021, 07:44:27 pm
content: Quote from: kcbrown on June 23, 2021, 09:10:10 pmI completely agree there. Unfortunately this sort of failsafe seems to be far less common than it ought to be.

author: rf-loop
author_rank: Super Contributor
timestamp: June 25, 2021, 04:14:25 am
content: Quote from: digby70 on June 23, 2021, 05:05:53 pmIn many Siglent instruments there is limits. In some Siglent instrument one update was even so that Siglent told it can use Only! 8G USB with Only 4k cluster size. But so tight limits are rare,With over 10 years experience with Siglent instruments I have made my own decision for my own use. I use only Kingston (2G, 4G) and 8G formatted to native FAT32 with 4k cluster sizes. And I keep these some sticks only for use with Siglent. These 2 and 4G have also led if there is some reason for watch activity)Of course many Siglent instruments may work today also with bigger capacity USB sticks, but because in my homeland I also give technical support to some my friends etc... for avoid "Oops things" (I use these old USB drives so I do not need think what pass for what model) what I know works reliable and if with these is some problem I know that problem is not USB stick itself.Also never use any USB stick what have used for some linux or some other boot... if so, they need restore to original factory state (deep format) and example in Windows, example using "diskpart" (Windows key + R and write justdiskpart, after then you need really know what you are doing for avoid "oops")Normal quick format is just bullshit for this purpose.Last least 8 years I have never meet any single FW update problem with Siglent instruments and I have done these quite lot (or other problems with USB sticks).But mostly I do these things so that I use first brain and after then hands.Also before plug out USB from computer, first close it... safe to remove and so on... (you may have experience it is not necessary... until you first time meet "what a shit happen" situation.Deep format for critical USB drives are also good to do some times because it also find and block bad sectors ( I do it also for all new drives if used for critical purposes). It need remember that USB drives are not reliable!Partition size, Cluster size512 - 8191 MB, 4 KBAnd note, for use with Siglent FW updates. There must be only one partition!

author: Sighound36
author_rank: Frequent Contributor
timestamp: June 25, 2021, 10:26:35 am
content: Rf-loopDid you have a hand in this design or coding for this product or were the SA & VNA more your field of expertise?digby70Personally, If I find a fault with a test product I go back to the point of sale, explain the issue and leave the ball firmly in their court. 95% of time I receive satisfactory outcome. The vendor is more than happy to assist, if he cannot resolve the issue, the manufacturer is involved simple process. Personally, I find bitching about it on an open forum distasteful, However I would suggest that if all avenues have failed then this maybe your only option. Though if a manufacturer lets the situation escalate to this stage without intervention or just fobbing you off then possibly. Still, they are ways and means of going about it, just my observations.Its called customer service, strange old fashioned concept I know but it is very valid personally I have encountered issues with various manufacturers and the suppling vendor has rectified the problem very positively.Just a side bar;Our company has a distribution company, and not so long ago I was presentating at a new product launch at one of our retailers, at the end of which I asked the question to around 20 guests (pre covid);"What in your minds constitutes good dealer service?"Answers ranged from:'Phoning up at 4pm and getting a next day delivery''Giving me x£££ on a trade in and free delivery''Great coffee and chat'So, I posed the questionIf you purchased say a 48inch 4K tv from an online retailer, you could possibly save £250 on your purchase with a genuine warranty.Now if in that warranty period the set went wrong, you call the supplier who says 'Right we will arrange for collection of the unit’ You have to remove it from its wall mount etc, pack it up securely and wait in for the courier to collect which will be between 8am and 6pm sorry we can’t be any more specific due to couriers’ route'You do not get a loan unit in the meantime and its down the manufacturer whether they repair or replace the unit which could take up to three to four weeks, then you have the reverse of having to wait in for delivery and then mount and set up the tv again.Purchasing from a reputable dealer you will not have these issues, they will arrange collection and removal of the faulty unit at your convince and will leave a loan unit while your faulty one is attended to. Then when ready will arrange a delivery time to suit you and reinstall the unit.Yes, you pay more, however is this customer service worth the extra against two days out or paying the mother in law to stay in and wait for the collection and drop off?You pay your money and makes your choice

author: 2N3055
author_rank: Super Contributor
timestamp: June 25, 2021, 12:52:02 pm
content: I stumbled upon this topic, and must say that Sighound summed it up nicely.My first reaction was:1. If I tried to flash 2 different devices and they had same error, first thing I would check iswhat I did wrong.2. Error was to try upgrade with same device that was involved in first unsuccessful upgrade. I would download again, use different stick with fresh format.3. I would contact vendor to try to troubleshoot with them.4. Only after I had definitive proof that it wasn't my fault and with explanation what is wrong and if vendor would refuse to fix the problem although it was their to fix, and then only, I would publish to general public an inflammatory topic with inflammatory title "Buyer beware...:"This way it came out as: don't buy Siglent loads because I'm a Muppet...My advice to OP: Everybody make mistakes.. God knows I reacted too soon many times in my life.. But please be so kind and fix (edit topic title to something like: False alarm and warning: Siglent Loads are sensitive to USB stick properties..). That would convert a mistake to a useful topic that will warn other users that if they have problem, the USB stick might be the culprit...

author: nctnico
author_rank: Super Contributor
timestamp: June 25, 2021, 01:09:41 pm
content: Quote from: 2N3055 on June 25, 2021, 12:52:02 pmBut still the DC load could have failed in a more descriptive / well defined manner; for example by checking the USB stick layout and testing the checksum of the firmware image to see if the image is actually complete. A message saying 'USB stick incompatible' or 'firmware image corrupt' is way more descriptive than the device getting into a non-working state.

author: Gridstop
author_rank: Contributor
timestamp: June 25, 2021, 02:03:13 pm
content: Quote from: 2N3055 on June 25, 2021, 12:52:02 pmThis is an incredibly insulting response to someone who has brought to light an inexcusable firmware bug in a shipping product. Nobody has pointed out where in the documentation siglent says you must use a specific size/format USB stick to perform the upgradeor the unit will be bricked, not just fail the update. I know because I went and looked and neither the firmware update instructions nor the user manual says anything beyond "The SDL1 can be upgraded with new firmware using an external FAT32 formatted USB memory device." That's it, nothing about size, nothing about sector size, nothing about the unit being bricked, nothing about the unit completely failing to validate the firmware before starting the install. This is absolutely not a 'False Alarm'.Keep in mind people will have to use this flawed update process to upgrade to any future fixed version of the firmware, so anybody unfortunate enough to have not seen warnings like this thread is likely to have the same problem since larger and larger usb sticks are becoming the default. I think I just bought a 5 pack of 16GB ones for $10 from amazon. I only have a single <2GB kicking around the house. Anybody who hasn't hit this exact same problem before or seen this warning will be seriously likely to brick their siglent load in the same way. But I guess they all must be muppets so who cares.

author: mawyatt
author_rank: Super Contributor
timestamp: June 25, 2021, 02:17:40 pm
content: Quote from: rf-loop on June 25, 2021, 04:14:25 amCaution!!! Our luck with Kingston SD cards has been just the opposite, these are the only SD card brand that have failed (had 2) so we've removed all Kingston brand SD cards and destroyed them. I opened one before it was crushed, and found a unbranded micro SD card wire bonded to an SD caseThese may have been counterfeit, don't know, but we don't buy memory products from unauthorized dealers off eBay, most are from B&H or local Best Buy which is likely where these Kingston cards came from.Now, since the Kingston issue long ago all our memory products are from Sandisk, Transcend and the old Lexar (when they were owned by Micron which actually made the memory chips) and never had an issue with any of these memory sources. Our use was hard on the cards since many thousands of images were collected with our chip imaging work, this was repeated often so the cards got many read/write cycles with many images, tough use indeed!!Don't want to bash Kingston, since these could have been fake and happened long ago, but we won't be using any Kingston memory product USB sticks or SD cards, others can decide for themselves.Best,

author: nctnico
author_rank: Super Contributor
timestamp: June 25, 2021, 02:35:49 pm
content: I have used hundreds of Kingston SD cards in products. Not a single problem. But these where sourced from a professional (business to business) vendor with traceable sourcing; not from the equivalent of the local supermarket that goes for rock bottom prices. However Sandisk and Transcend are also reliable brands.All in all I'm quite sure you have bought counterfeits.

author: 2N3055
author_rank: Super Contributor
timestamp: June 25, 2021, 02:59:53 pm
content: Quote from: Gridstop on June 25, 2021, 02:03:13 pmI didn't say Siglent load couldn't have more robust /better firmware upgrade procedure.. In fact they should, because obviously things can go wrong.It is not a firmware bug. It is a upgrade procedure that cannot cope with absolutely every combination that can happen in the field.Wrong thing was repeating same procedure expecting different outcome. I would have returned load and demanded it to be replaced with one with the current firmware, so they have the responsibility to do it right. I wouldn't do it twice in a row, same way.. And would demand explanation what happened.In addition to manual, there are release notes and firmware update with the firmware that go in more detail. There is a recovery procedure to load firmware even on device that failed previous update.. Which in the end worked for OP.Problem I have is not that he had problem, which he had. And problem is with firmware updated being fiddly about USB sticks. That is something Siglent should look into if they can.Problem is that OP declared "Buyer Beware: Siglent Electronic Load ....This makes me doubt the quality of their products. I am now wondering if others are having problems withSiglent test equipment as I was going to purchase a spectrum analyzer from them.".That was his first reaction... Before troubleshooting, before waiting to hear what happened, before finding out the problem or solution. That is just lame.And then saying, problem solved, device works fine, upgrade worked fine with different stick...But all previously said is still there...That being said, English is not my first language, and I know as much as I do, not much. I also don't know what are cultural side notes on Muppets. It seems that you took that as a hard insult. Muppet show in my country is referring to goofy behavior but in an humorous and endearing way. You would tell that to somebody that you like but that did something goofy.If I think someone is an idiot, word I would use would be an idiot. Not Muppet. Smiley next to it was a hint..If someone find it insulting, I apologize. Now I explained what I meant.

author: 2N3055
author_rank: Super Contributor
timestamp: June 25, 2021, 03:04:20 pm
content: Quote from: mawyatt on June 25, 2021, 02:17:40 pmI use free 4 GB USB sticks that my vendor sends me with every shipment filled with documentation. I have handful of those and they work perfectly.Those that work best are USB 2 4GB or less. Format with FAT32 with 4k sectors and voila..I agree with Nico, those Kingstons were probably counterfeits.

author: Gridstop
author_rank: Contributor
timestamp: June 25, 2021, 03:22:43 pm
content: Quote from: 2N3055 on June 25, 2021, 02:59:53 pmI agree that digby definitely could have saved himself some headache/hassle by changing up his procedure.Obviously I disagree that I think this is a serious bug, not just a quirk. Like the others in this thread have demonstrated, everyone seems to have different experience with different brands/types of flash. I totally understand how this happens on a development team because I've been there. You get something working, the lab has a big supply of a single variety of usb or sd card flash in the cabinet, and everyone falls into the habit of doing what works. Then the product ships and you realize not everybody has 8GB Sandisk Class 2 micro sd cards or whatever. I agree they can't support every possible combination but it needs to fail gracefully and safely.And lastly I appreciate I may have inferred more offense than intended, sorry. It just felt like calling out a guy who was genuinely trying to warn others. If I owned this exact model I would have really appreciated the warning. I just bought another siglent product and I'll be keeping this in mind for sure.

author: Old Printer
author_rank: Frequent Contributor
timestamp: June 25, 2021, 03:45:27 pm
content: https://youtube.com/watch?v=srbCmB-RjYM&feature=shareThis is a link to a video by Tomtektest who is a retired EE with a PhD. It describes a similar situation of upgrading FW on a Siglent AWG but from outside of the warranty period. Tom is a gentle soul and a very calm guy, not sure I would be quite so relaxed about it. If this turns out to be a brand defect that runs through the Siglent line, they have some work to do. I have an 1104X-E scope that may be outside warranty and I am concerned about updating the FW.Just checked, I am still inside their 3 year warranty so I will get the ideal flash drive and get my scope updated.

author: RoGeorge
author_rank: Super Contributor
timestamp: June 25, 2021, 04:07:04 pm
content: Siglent fans, you are not doing any good to Siglent by bashingdigby70, a buyer and a newcomer to EEVblog, with words like "bitching" and "Muppet".

author: mawyatt
author_rank: Super Contributor
timestamp: June 25, 2021, 04:07:58 pm
content: Quote from: 2N3055 on June 25, 2021, 02:59:53 pmWe are in the middle of a very difficult & complex design task which includes a high voltage multi-output (7 independent outputs) power supply. To help with the power supply test and evaluation an electronic load was considered. After noting this thread title it does convey more than just a USB stick issue with the Siglent Load, and did raise an issue if the Siglent Load has more problems. After reading a few times, we went ahead and ordered the Siglent Load and accept the "Buyer Beware" riskBest,

author: 2N3055
author_rank: Super Contributor
timestamp: June 25, 2021, 04:56:29 pm
content: Quote from: RoGeorge on June 25, 2021, 04:07:04 pmYeah don't inflame the issue... I said what I said, read again, all of it. If I say something and I'm proved to be wrong ,I apologize. I won't be going back and "rewrite history". I own my mistakes, and it wasn't even mistake but really misunderstanding in terms.. You're very intelligent and decent person, I'm sure you can take balanced look.And no, no need for Siglent lovers or haters equally... Fact that OP had problems is undisputable. How he reacted, is a matter of discussion.Also I'm really amused by all of the people who take device firmware upgrade as some easy-peasy thing that is supposed to be completely risk free.Try updating firmware with flaky power.. There are many things that can go wrong with firmware update.. And maybe 10 years ago, you had to return device to factory to update firmware.I have few Siglent devices at my disposal and ones that I have do seem to say "verifying image" when doing upgrade.I don't know what underlying OS /RTOS it uses and what is actual Firmware upgrade code.So instead of making this a bashing in all directions, I suggested to make it constructive:Maybe a question to Siglent if they could make it more robust (not to use "foolproof" to insult more people), and maybe being able to detect and reject USB sticks that doesn't work well...

author: kcbrown
author_rank: Frequent Contributor
timestamp: June 25, 2021, 07:54:21 pm
content: Quote from: nctnico on June 25, 2021, 01:09:41 pmThere's really no excuse whatsoever, in this day and age, to fail to test the firmware image prior to installing it, much less after installing it. Such verification must happen at both levels becausein the absence of fallback firmware, you risk bricking the device otherwise. Bricking the device is acompletely unacceptableoutcome in the event of anything other than a major hardware failure.Obviously there should be enough flash storage to hold two copies of the firmware: the one that is currently in use, and the one that is being upgraded to.

author: kcbrown
author_rank: Frequent Contributor
timestamp: June 25, 2021, 08:32:01 pm
content: Quote from: 2N3055 on June 25, 2021, 04:56:29 pmYes, there are many things that can go wrong with the update process itself. But save for actual hardware failure, there's no excuse for such failures to result in the device attempting to use the resulting corrupt firmware installation. Even yanking the power in the middle of the update process should not cause the device to fail to boot from a good firmware image because there should be enough flash to holdat leasttwo separate copies of the firmware.QuoteImage verification should happen twice. The first should be of the image on the USB stick. The second should be of the image in flash after it's been written.QuoteCertainly this request should be made, but c'mon. Flash firmware upgrades have been a thing forat leasta decade now. If flash firmware upgrades were a relatively new thing such that the techniques were still being figured out, it might be understandable to see a problematic implementation. But at some point, the way to do something becomes standardand obviouspractice, and failure to adhere to that standard is clearly deserving of criticism.QuoteHonestly, I don't understand this issue with USB sticks at all. This ain't the early 2000's, you know, when USB sticks were just becoming a thing. We're talking about a20 year old technologyhere. The standards are well-developed and well-known. The filesystems are even older than that! The filesystem code and the USB storage driver code has been aroundin open source formfor about that long as well. No, at this point, there is no excusewhatsoeverfor having limits on the size or formats (when the formats are one of the standards in use) of USB sticks that will work here. FAT32 as a filesystem supports volumes up to 2terabytes, and has been around since1996. So no, there is no excuse at all for being unable to deal with any USB stick of that size or less, save for when there's a hardware fault with the USB stick.

author: 2N3055
author_rank: Super Contributor
timestamp: June 25, 2021, 09:31:29 pm
content: Quote from: kcbrown on June 25, 2021, 08:32:01 pmPC motherboard updates (which seems to be what people are expecting) are happening either in DOS boot or from OS but with flash in banks. That become more common with UEFI that has more integration with BIOS and OS.Before that, it was boot to DOS and upgrade firmware.I agree it is unusual that USB stack on firmware updates is picky . I would presume that code that updates firmware from USB stick is some sort of bootloader, and not running Linux and therefore not having real full USB stack and filesystem as a proper OS has... That might be the problem. I don't know. That part of code may be the part of development platform.. Or ready bought library..

author: kcbrown
author_rank: Frequent Contributor
timestamp: June 26, 2021, 07:33:00 pm
content: Quote from: 2N3055 on June 25, 2021, 09:31:29 pmExactly. But the point here is that the state of the art is now, and has been for quite a long time, to use flash in banks.An alternative would be to have a known good image in good old ROM, so that you're guaranteed to have something to boot from (and to upgrade with) in the event an upgrade attempt goes wrong. ROM has the advantage that you can boot from it even if the flash is malfunctioning. You might well have an emergency flash upgrader in ROM already, in which case you may as well use a larger ROM and put a full copy of a known good boot image there.QuoteThat might be, but I don't buy it as a good reason for it. These devices have JTAG interfaces that can be used (and almost certainly are at the factory) to initially program the flash. So you don't need the bootloader code to program the flash unless your flash isn't in banks or isn't sufficiently sized to hold more than one image. But the point here is exactly that the use of banked flash or flash sized large enough to hold multiple images is the standard approach to this problem, and there just isn't any excuse anymore to not use that approach.About the only complication I can think of is if the operating system itself is executed directly from flash, rather than being loaded into RAM from it. But RAM, too, is cheap, most certainly in the quantities necessary to house an embedded OS, and executing from RAM instead of directly from flash solves a whole host of problems that you'd otherwise have, such as very slow instruction fetch times while within the operating system. If the operating system is executing from RAM as it should be, then it would be just as able to upgrade the flash image as anything else, and that eliminates the excuse of not being able to perform upgrades from within code that understands how to read all properly functioning USB sticks.So the bottom line is that the current state of the art has been what it is for quite some time now, and there's no real excuse that I can think of for these devices to be deviating from it.

author: 2N3055
author_rank: Super Contributor
timestamp: June 26, 2021, 11:02:26 pm
content: Quote from: kcbrown on June 26, 2021, 07:33:00 pmI don't want this to be considered as an excuse for Siglent for having problems with some USB sticks, but today I took a look at Dave's video about fancy PSU from R&S and that one also couldn't read one properly formatted stick but worked OK with other brand... It does seem that this USB stick compatibility problem is more common with those kinds of devices that use bare metal RTOS and embedded USB stacks, than people think,...Still, even if a USB compatibility cannot be made such that work with absolutely every USB stick disk, device should simply reject it with clear error message. That would be good start. In that case, you could simply try few sticks, pick one that works and keep it dedicated for that purpose.

author: kcbrown
author_rank: Frequent Contributor
timestamp: June 26, 2021, 11:49:03 pm
content: Quote from: 2N3055 on June 26, 2021, 11:02:26 pmI agree with you there. But it's unclear why this is. I can see how that could be the case if they're using an RTOS that stopped development a decade ago or so, but anything newer than that should be able to easily deal with any of the modern USB sticks that are out there. The sole possible exception might be pure USB3 devices that don't work with pure USB2 interfaces. But those should be incompatible withallUSB2 ports.It's on the manufacturers to make use of an operating system that is properly maintained. I would argue that an operating system that cannot properly recognize modern USB sticks is one that isnotproperly maintained.For Siglent, there's no excuse at all. They're using Linux as the operating system in all of the devices I'm aware of (if the electronic load here is an exception, one is left wondering why in the world that is), and thatdoeshave proper compatibility with modern USB sticks of all sizes. Whatever Siglent's issue is, it's almost certainly not in the operating system itself. Or if it is, they're doing somethinghorriblywrong for that to be the case.QuoteI certainly agree with this, but obviously it should be in addition to a properly level of compatibility with modern USB sticks, not a replacement for it.

author: Caltech-WireWizard
author_rank: Newbie
timestamp: February 18, 2024, 09:41:36 pm
content: I'm not entirely convinced it's a Firmware "UPDATE" problem. I received my Siglent SDL1020X-E 2mo. ago on December 12, 2023. First thing after I received it was update the Firmware. No issues. In-fact, I had Siglent Tech Support on the phone while I was doing it in case of any issues. There were no issues during the update. BTW, According to Siglent, the maximum drive size is 4GB FAT32 formatted w/4k cluster size) It's now Feb. 18th 2024 (2mo. of use). I had that same boot error screen. I had no issues leading up to that. All I did was power-cycle it and it booted fine. Then I had it a second time. I suspect corrupt firmware. I reflashed it. No problems since. (here's hopping..... crossing fingers)

author: slugrustle
author_rank: Frequent Contributor
timestamp: February 18, 2024, 10:32:50 pm
content: Even if the instrument doesn't have enough flash memory to hold two firmware images, it should at the very least read the entire new image from the USB drive and verify that with checksum before trying to go further. That doesn't take any more memory on the instrument and should catch issues with bad images, bad flash drives, unsupported drive formats, etc.Heck, you would think that if there are requirements on USB drive size and partition formatting, the instrument would check that the USB drive meets the requirements and give the user a helpful warning if it doesn't, then refuse to attempt an update in such circumstances.I agree that the original post was phrased in a slightly drastic way if the poster hadn't tried to work with Siglent or the distributor yet, but I can also understand how frustrating these situations can be. Certainly, bricked instruments shouldn't happen simply due to drive size or partition formatting.All of this said, I updated the firmware on a Rigol bench DMM recently, and I was careful to follow the instructions, including plugging the DMM into a UPS during the update. You never know... I also stick to USB drives with SLC flash, usually 1GB size with a singe FAT16 partition. Those seem to work on everything.