[SOLVED] Keysight DSO-X 3024T - Possible NAND corruption - Page 1
Forum section: electronics / testgear

author: AltF4Swe
author_rank: Newbie
timestamp: March 08, 2024, 12:35:58 pm
content: Hi!I've got a Keysight DSO-X 3024T which shows all symptoms of the NAND corruption problem.The scope hangs with just the "Ref" light on, with the following u-boot segment:QuoteI've tried the "titiris" fix (https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg2136181/#msg2136181) and everything works fine until it's time for the "go" command at the end. It hangs at the "BALDWIN_DDI identification step. Here's the log:QuoteWhat do you think, can it be fixed or should I throw my scope in a nearby lake?Best regards / AltF4Swe

author: HighVoltage
author_rank: Super Contributor
timestamp: March 08, 2024, 02:35:10 pm
content: Contact Keysight first.If you are lucky, they will take care of the scope, as they have done many times in the past, even if the warranty has expired.

author: TheSteve
author_rank: Unknown
timestamp: March 08, 2024, 04:06:48 pm
content: Yes, that is typical nand corruption(quite rare on the T models).I don't believe you will be able to use any of the files in the link you provided as you have a T model and those files are for the 2000/3000A series.

author: Pinkus
author_rank: Frequent Contributor
timestamp: March 08, 2024, 05:08:14 pm
content: Quote from: HighVoltage on March 08, 2024, 02:35:10 pmI second this. Keysight installed a new motherboard with a new calibration in my DSOX4024a, no questions asked. But better mention that you expect, that the service note still applies for a free repair due to NAND issues.

author: Bud
author_rank: Super Contributor
timestamp: March 08, 2024, 05:24:44 pm
content: QuoteYou 3000T afficionados please tell the guy the proper address for image2 so he could try loading it.

author: AltF4Swe
author_rank: Newbie
timestamp: March 09, 2024, 01:41:52 pm
content: QuoteOk! I might have missed that the v2.35 .cab didn’t include the T-models. Maybe that’s the cause for the ”Unknown board config” error message during startup after Ymodem-transfer. So, it might work if I find a firmware for the DSOX T-model? Guess it will have to be an old one, to be able to boot from USB. Question is, where can I find a backdated firmware?

author: Bud
author_rank: Super Contributor
timestamp: March 09, 2024, 02:39:44 pm
content: QuoteYou know the length of the nk image, this gives you a clue what firmware version to look for. You then can write it to NAND, no need to worry about USB.Can you stop autoboot and type printenv from p500 prompt to view the environment variables. Also type help to see which commands are available.

author: AltF4Swe
author_rank: Newbie
timestamp: March 11, 2024, 12:46:04 pm
content: Success! The DSO-X 3024T is now unbricked!Thank you for getting me on the right track. The thing I missed was that the v2.35 firmware in the "titiris method" didn't include the T-series.I managed to find an old firmware (04.08) for the T-series and did the following (a few changes to the titiris method).1. Extracted the recover.nk.bin.com from the .ksx (renamed it to .cab first)2. Ran the UnKsx.exe tool to decrypt the recover.nk.bin.comp (Thank you user: abyrvalg)3. Extracted nk.bin from the decrypted recover.nk.bin.comp with bincompress4. Got the length of nk.bin with viewvbin.exe5. Converted nk.bin to nk.nb0 with cvrtbin.exe6. Connected to the scope via 3.3V Serial7. Stopped the boot sequence8. Entered the "loady 0x0361000 115200" command at p500> prompt9. Transferred the nk.nb0 via YMODEM10. Entered "go 0x00362000" commandAnd, boom!The u-boot sequence finally looked much better and the scope started! Once started it complained that the FW was corrupt, but I just took the corresponding .ksx firmware I used earlier, put in on a USB and ran the prompted FW-upgrade. After upgrade the scope started and worked 100%. After this I grabbed the latest firmware (7.60 from 2023) and made yet another firmware upgrade.Greetings from a happy user

author: xyqahzw
author_rank: Newbie
timestamp: September 05, 2025, 02:53:04 am
content: Quote from: AltF4Swe on March 11, 2024, 12:46:04 pmI tried to use the UnKsx.exe tool to decrypt the recover.nk.bin.comp, and it prompted that it is not a ksx file. Could you send me a copy of the recover.nk.bin.comp file? The error on my device is exactly the same as yours.