Agilent MSO-X 3014A not booting past Ref/Math/Digital/Serial LEDs - Page 1
Forum section: electronics / testgear

author: elemenoh
author_rank: Contributor
timestamp: January 07, 2023, 05:57:49 pm
content: This scope is new to me and not booting. Before digging in too far, I'm hoping someone here might know where I should focus troubleshooting.This is currently what happens when the power switch is pressed:Fan turns onThe backlit buttons (Run/Stop, Single, Wave Gen and the channels) flash twice then remain offRef, Math, Digital and Serial lights turn on one after the other and stay lit.Nothing happens after. Backlit buttons don't light up when pressed.I took it apart to check for anything visually obvious like burned components or disconnected cables, but didn't notice anything. The scope behaved the same way after reassembly.Any ideas?

author: AndyC_772
author_rank: Super Contributor
timestamp: January 07, 2023, 06:01:16 pm
content: Sounds like the well known NAND Flash corruption issue. The scope's firmware is stored in a memory device that's not 100% reliable, and later software versions included mitigation that allowed it to be recovered in the event of the application becoming corrupted. Earlier firmware could simply crash.IIRC the only fix is to return it to Keysight to be re-flashed, but they have been known to do this on out-of-warranty scopes as a goodwill gesture. It's definitely worth asking, IMHO.

author: elemenoh
author_rank: Contributor
timestamp: January 07, 2023, 06:11:13 pm
content: Thanks for the suggestion. I'll try reaching out.

author: elemenoh
author_rank: Contributor
timestamp: January 07, 2023, 07:06:10 pm
content: I've written to Keysight to see if they'll take care of it. If not, is there a DIY fix for this?

author: switchabl
author_rank: Frequent Contributor
timestamp: January 07, 2023, 07:32:22 pm
content: Several people (myself included) have successfully fixed this using the internal serial console. See the "hacking" thread for more information:https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg4525313/#msg4525313

author: elemenoh
author_rank: Contributor
timestamp: January 10, 2023, 06:20:08 pm
content: I've been having trouble getting serial from the scope. Hopefully I'm just doing something dumb.Jumper wires are connected to GND, TX and RX. I tested the ground pins with a multimeter first to make sure the orientation is correct.I connected to two different FTDI USB/TTL adapters. One is a very cheap knock off and the other was more expensive and hopefully genuine. Both have the same results.The host is a M1 MacBook Pro with CoolTerm 1.8.0. The terminal is configured with 115200,8,N,1.There's no serial output when powering up the scope other than an occasional ˇ. When powered off, a single period is output.The scope still shows the math lights coming up in sequence but nothing other than that on the front panel. The fan spins continuously. There's no difference in behavior even if the scope is left powered on or off for several minutes during attempts.Does this still sound like the NAND issue and I just have a bad serial setup or is there maybe something else going on?

author: james_s
author_rank: Super Contributor
timestamp: January 10, 2023, 06:28:53 pm
content: Make sure you're using a 3.3V serial adapter, not 5V. At least I'd assume the logic in the scope is 3.3V given it is not all that old. Does the serial adapter echo what you type if you wire tx directly to rx?

author: elemenoh
author_rank: Contributor
timestamp: January 10, 2023, 06:40:07 pm
content: Quote from: james_s on January 10, 2023, 06:28:53 pmYep it's jumpered for 3.3V and echos if RX/TX are in loopback too.

author: elemenoh
author_rank: Contributor
timestamp: January 12, 2023, 05:51:10 pm
content: Keysight quoted me $3,776 for the repair, so I think I'm going to keep trying to figure this out DIY lol

author: AndyC_772
author_rank: Super Contributor
timestamp: January 12, 2023, 06:29:30 pm
content: I'd query that with them, it sounds like someone has just quoted a standard repair charge. I got something similar when I asked about a failed PSU in my MSO-X3104A, and to be fair to them, they did make me a more reasonable offer when I metaphorically spat out my coffee in their general direction.Keysight's marketing guy Daniel has an eeblog presence, it might be worth seeking him out to see if he can help. I know this particular fault (if, indeed, that's what's wrong with your scope) was one that Keysight have been known to cover even outside of warranty.

author: TheSteve
author_rank: Unknown
timestamp: January 12, 2023, 07:13:28 pm
content: Keysight did have a service note indicating that NAND corruption would be covered past the original warranty date. However I believe the extended coverage provided by the service note has expired. I don't think you'll find they will still do a no charge repair. Always worth asking of course.99.9% of the time NAND corruption can be fixed yourself.If you're seeing any LED's flash/turn on then there should be serial data output. Double(triple) check your connections and terminal settings, chances are something isn't correct.

author: james_s
author_rank: Super Contributor
timestamp: January 12, 2023, 10:53:19 pm
content: There's probably a good chance it's the flash, but I'd start with some simple checks. Confirm the power supply voltage(s) are present and within a reasonable tolerance. Check any oscillators you can find and make sure they're putting out something. See if you can find the reset line for the CPU and see what it's doing. Look at the bus and see if there's any activity. Of course a lot of this relies on having access to another oscilloscope.

author: switchabl
author_rank: Frequent Contributor
timestamp: January 13, 2023, 01:09:49 am
content: Most likely there is a problem with your serial connection. If you see flashing LEDs, I think the boot process is getting at least as far as the Windows CE bootloader. So supply voltages and clock (at least for the main processor) are almost certainly fine. And like TheSteve said, there should at least besomeactivity on the serial console. at that stageMake sure you don't have the RX and TX pins swapped (try connecting the RX pin of your adapter to either to be sure). Check your serial adapter on something else to make sure you have it set up correctly, maybe the serial console on a Raspberry Pi or some other SBC that you may have lying around. If nothing else helps, check the 3000X TX pin with a second oscillscope to make sure that there is any activity at all.Also, I've had signal integrity issues with cheap USB<->UART adapters before and adding a USB isolator or using a laptop running on battery may help in that case.

author: elemenoh
author_rank: Contributor
timestamp: January 13, 2023, 06:50:50 pm
content: Well of course I had RX/TX mixed up despite checking several times. Anyway, I'm in now and will continue to follow the steps in the other thread. Thanks for the help so far everyone.Code:U-Boot 2010.03 (Oct 18 2011 - 14:28:06)Agilent P500CPU: SPEAr600DRAM: 128 MiBFlash: 512 KiBNAND: fsmc-ecc1 128 MiBIn: serialOut: serialErr: serialSerNum:serial number not programmedChip: BD Board Rev: 4Net: smscPress space to stop autoboot: 0## Booting kernel from Legacy Image at f8050000 ...Image Name: PBOOTCreated: 2011-08-24 22:35:34 UTCImage Type: ARM Linux Kernel Image (gzip compressed)Data Size: 36045 Bytes = 35.2 KiBLoad Address: 00000000Entry Point: 00000000Uncompressing Kernel Image ... OKStarting kernel ...Debug serial initialized ........OKMicrosoft Windows CE Bootloader Common Library Version 1.4 Built Aug 24 2011 15:15:48Microsoft Windows CE 6.0 Ethernet Bootloader for the Agilent P500 boardAdaptation performed by Agilent Technologies (c) 2008System ready!Preparing for download...Loading image 1 from memory at 0xD0600000OBL_IMAGE_TYPE_BINXXXXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOXOXOOOOXXOOOOOOOOOXOOOOXOXXOXOXXOOOXOXXXXXOOXXXOOOOOOXOOXXXOXXOOOXOXXOOXXOXOOOXOOXOOXXOOOXOOOOXOXOOOOOXOOOXOOXOXXXXXOXOXOXOXXXXXXOXXXXOOOXOOOXOXOOOOXOOOOXOXOXOOOOOOXOOOXOOXOOOOOXXOOOOOXOOXOOXXOOOOOOOOOXOOOOXOOOOOOOXXOOOOOXXOOOOOOOXOOOOXOXOOOOXOOOXOOXOOXOOXOXOXOOXOXOXXOXOOOXXXOOXXOXXOOOXXXXOXOOXOXOOOOXOOOOXOOOXOOERROR: Checksum failure (expected=0x6F6450 computed=0x6F64F4)****** Checksum failure on record 125, ABORT!!! ******Completed file(s):-------------------------------------------------------------------------------: Address=0x80361000 Length=0x13064E8 Name="" Target=RAMLoading image 1 failed, trying next oneLoading image 2 from memory at 0xD1600000BL_IMAGE_TYPE_UNKNOWNLoading image 2 failed, trying next oneAll images failedPress r to reset

author: TheSteve
author_rank: Unknown
timestamp: January 13, 2023, 08:35:32 pm
content: Good Good, standard NAND corruption. Hopefully the fix goes well.

author: elemenoh
author_rank: Contributor
timestamp: January 16, 2023, 12:40:21 am
content: I've made good progress but could use a little more help.I'm doing this on a Mac. For anyone else who only has access to a Mac, a couple of notes which might save you trouble.1) The steps to prepare the nk.nb0 and USB flash drive files have to be done on Windows. I tried setting up VMWare Fusion 13 on an M1 MacBook Pro with a beta of Windows 11 for ARM, but too much stuff is broken. I ended up using Fusion 13 with Windows 11 on an older Intel MacBook Pro which worked fine.2) I had trouble uploading the nk.nb0 file from TeraTerm via Fusion. It would just stop transferring at random points unexpectedly. I ended up copying nk.nb0 to the Mac side. CoolTerm usually works okay for me, but didn't have ymodem options and whatever it was using would transfer the file but then loady would just time out. I ended up installing minicom via HomeBrew. That has a ymodem option but would just do nothing when initiating the transfer. I had to install lrzsz via HomeBrew as well and configure minicom to use lsb and lrb instead of sb and rb respectively. With that setup the file transferred okay and the scope booted!Help wanted:The USB drive was prepped as the instructions advised with 02.35 firmware. The drive mounted on the scope okay. I selected the CAB file to update and a dialog popped up to confirm. It seemed to start to kick off the process but then the USB drive would disconnect and nothing else would happen. Trying again and again had the same results.I checked the currently installed firmware which is 02.36. So I tried copying over 02.37 CAB from the thread and the 02.65 CAB (renamed from .ksx) from Keysight's site. Both of those had the same behavior as 02.35. Rebooting the scope regressed to the original symptom.So, is this a known issue too? Am I possibly doing something wrong? Maybe try a different USB stick?

author: elemenoh
author_rank: Contributor
timestamp: January 16, 2023, 08:41:32 pm
content: Update: I tried another USB stick which did kick off the update, but seems to hang and boot loop. I tried setting up the USB stick with both 20.35 and 20.37 firmware (following the linked instructions) but got the same results. The front panel cycles through the channel, wave gen, math and run/single LEDs and eventually reboots.Here's the serial output:Code:U-Boot 2010.03 (Oct 18 2011 - 14:28:06)Agilent P500CPU: SPEAr600DRAM: 128 MiBFlash: 512 KiBNAND: fsmc-ecc1 128 MiBIn: serialOut: serialErr: serialSerNum:serial number not programmedChip: BD Board Rev: 4Net: smscPress space to stop autoboot: 0## Booting kernel from Legacy Image at f8050000 ...Image Name: PBOOTCreated: 2015-05-07 8:18:27 UTCImage Type: ARM Linux Kernel Image (gzip compressed)Data Size: 37749 Bytes = 36.9 KiBLoad Address: 00000000Entry Point: 00000000Uncompressing Kernel Image ... OKStarting kernel ...Debug serial initialized ........OKRTC: 2023-1-16 14:24:24.50 UTCMicrosoft Windows CE Bootloader Common Library Version 1.4 Built May 7 2015 01:38:03Microsoft Windows CE 6.0 Ethernet Bootloader for the Agilent P500 boardAdaptation performed by Agilent Technologies (c) 2008System ready!Preparing for download...RTC: 2023-1-16 14:24:24.54 UTCLoading image 1 from memory at 0xD0600000OBL_IMAGE_TYPE_BINXXXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOOXOOOOXXXOOOOOOOOOXOOOOXOXXOXOXXOXOXOXOXXXXOOXXXOOOOOOXXOXXOXXXXXXOOOXXXOXXOOOXXXOOOXOOXOOXXOOXOXOOOOXOXOOOOOXOOOXOOOXXXOXOXXXXXXOXXXXOOXOOOXOOXOOOOXXXOOOOXOOXXOOXOOOOOOOOOXOXOOOXOOOOOOXOXOOOOXOXOOOOOOOXOXOXOOXOXOOOXOOOXOOXOXXOXOOOXOXXXXXOXOXXOXXXXOXOXXOOOXXOXXXXXXXOXXXXXXXOXXXXOXOXXOXOOOXXXXOXXXXXOOOXXOXOOXXOXXXOOXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXXXOXOOOXO.XXImageStart = 0x80361000, ImageLength = 0x1ACB780, LaunchAddr = 0x80362000Completed file(s):-------------------------------------------------------------------------------: Address=0x80361000 Length=0x1ACB780 Name="" Target=RAMLoading image 1 succeeded.ROMHDR at Address 80361044hPreparing launch...RTC: 2023-1-16 14:24:27.91 UTCLaunching windows CE image by jumping at address 0x 362000Windows CE Kernel for ARM (Thumb Enabled) Built on Mar 8 2013 at 17:05:33Setting up for a Cold RebootDone Setting up for a Cold RebootWindows CE Firmware InitBSP 1.0.0 for the SPEARHEAD600AB board (built Mar 7 2021)Adaptation performed by ADENEO (c) 2005+OALIntrInit-OALIntrInit(rc = 1)Initialize driver globals Zeros area...pDrvGlobalArea 0xa0060000 size 0x800 (0xa0060800 -0xa0060000)Initialize driver globals Zeros area...doneOALKitlStartFirmware Init Done.OALIoctlHalEnterI2cCriticalSection init i2c cs++SER_Init: context Drivers\Active\14SER_Init, dwIndex:2SER2 got sysintr:0x00000017SER2 Serial Port, new baud rate:0x1c200 (UARTCLK:48000000 IBRD:0x1a FBRD:0x2)OHCI\system.c, GCFG_USBH1_SW_RSTOHCI\system.c, GCFG_USBH2_SW_RST-EDeviceLoadEeprom 00:30:D3:20:46:ADPhy found addr 31 (ticks=3363)WaitForLink Start (ticks=3364)No Link (ticks=4367)<--EDeviceInitializeGMAC DMA status register = 0x0LIN: Data ValidBALDWIN_DDI: cBaldwinHwIf::Init: Initializing...BALDWIN_DDI: cBaldwinHwIf::Init: Scope successfully identified.BALDWIN_DDI: cBaldwinHwIf::Init: Success!Running infiniiVisionInstallHelperFailed to start/configure network.Device load time:NANDFLASH: 91 msSNANDFLASH: 91 msUSB Hard Disk Drive: 91 ms

author: elemenoh
author_rank: Contributor
timestamp: January 16, 2023, 08:57:25 pm
content: Right after I posted my last update, the scope fully booted and is now updated to 20.65. All tests passed. Not sure what got it to stop boot looping but I'm not complainingThanks again for all of the help here!

author: tv84
author_rank: Super Contributor
timestamp: January 16, 2023, 09:14:13 pm
content: Quote from: elemenoh on January 16, 2023, 08:57:25 pmWell done.Let's hope that you upgraded to2.65...or else problems may continue...

author: switchabl
author_rank: Frequent Contributor
timestamp: January 16, 2023, 09:29:19 pm
content: The USB stick still has the boot override file on it. So you need to unplug it after the firmware upgrade, otherwise it won't boot properly. I will add a note to my other post, so more people don't have to find out by accident.Anyway, happy you got it working again.

author: elemenoh
author_rank: Contributor
timestamp: January 17, 2023, 02:32:11 am
content: @switchabl, you might want to add some additional indication about how to tell the update was performed and the USB stick is okay to be unplugged. Assuming it'd be when the display turns off when a reboot is kicked off?

author: TheSteve
author_rank: Unknown
timestamp: January 17, 2023, 04:16:41 am
content: Nicely done! Does it really have the 1 GHz upgrade hardware installed?

author: elemenoh
author_rank: Contributor
timestamp: January 17, 2023, 05:42:49 am
content: Quote from: TheSteve on January 17, 2023, 04:16:41 amYep, 1GHz, 5GSa/s and a nice stack of options. I saw there's a way to hack it to get the rest of the options but it's more than enough for me as-is for now. This was a really nice ewaste score and will be my new main scope.

author: TheSteve
author_rank: Unknown
timestamp: January 17, 2023, 06:04:24 am
content: Quote from: elemenoh on January 17, 2023, 05:42:49 amAn amazing find, so worth saving.

author: mhsprang
author_rank: Regular Contributor
timestamp: January 18, 2023, 09:19:39 am
content: I am experiencing the exact same problem on my 2014A. Reading that Keysight has fixed this in the past, I contacted them. They quoted me a main board replacement for €3362! I paid €2100 for that scope, new, at Farnell back in 2014...

author: james_s
author_rank: Super Contributor
timestamp: January 19, 2023, 03:18:10 am
content: That's a heck of a nice scope, I hadn't noticed the 1GHz upgrade. Maybe that's why these things are so shockingly expensive for a 100MHz scope.

author: TheSteve
author_rank: Unknown
timestamp: January 19, 2023, 04:18:33 am
content: Quote from: james_s on January 19, 2023, 03:18:10 amFrom the factory the 100 MHz scope can be software unlocked to 200 MHz. The hardware was swapped out completely to upgrade to 1 GHz.

author: Randomized
author_rank: Newbie
timestamp: December 08, 2023, 09:04:43 pm
content: I have most likely the same problem.unfortunately the links to the firmware seem to be dead, does anyone have a copy of the firmware that I need to flash?Thanks....