Agilent MSO6014A Not Booting - Page 1
Forum section: electronics / testgear

author: jack_elec
author_rank: Contributor
timestamp: March 31, 2025, 07:59:43 pm
content: Greetings all.I bought an Agilent MSO6014A around year ago, second-hand off eBay. The analogue channels don't work properly (that's for another day), but digital channels work fine (even got the logic analyser pods included in the sale). Hacked all the options supported and none of the ones which aren't, all working OK, so no issues there.A few weeks ago, I was using it in digital mode to debug SPI on an MCU and loving the MSO interface as many have commented already. Powering off the 'scope between uses and powering it on the following day with no problems.Powered 'scope off using front-panel power button, and when I turned it on again it now won't bootThe only thing I did differently when powering off this time around, was to save the setup I was using for debugging to the internal (C:\setups) memory. It didn't auto-save a couple of days prior to this happening, so I didn't want to have to set up all the digital channels again if it happened again this time around.I have tried doing the emergency restore procedure from USB drive using the procedure documented on the Keysight website using sys6000.bin (v6.20) and sys6000.jzp, lib6000.jzp, lpk6000,jzp, gsp6000.jzp (from Keysight website, all latest versions) but no luck.I then connected to the debug UART using the details in analogRF's post on the main MSO/DSO5000/6000/7000 thread to see what is going on and got the following boot log:Code:chkMacAddr(VxWorks System BootCopyright 1984-2002 Wind River Systems, Inc.CPU: Agilent KOM PPC405, SA27E rev1Version: VxWorks5.5.1BSP version: 1.2/0Creation date: Oct 5 2006, 09:45:26Bad checksum stored for boot line in NV ram.Calculated 0xfe, stored = 0xffStoring checkSum = 0xfePress any key to stop auto-boot...1auto-booting...boot device : tffs;usbunit number : 0processor number : 0host name : bootfile name : sys6000inet on ethernet (e) : 0.0.0.0host inet (h) : 0.0.0.0user (u) : targetftp password (pw) : targetflags (f) : 0x8target name (tn) : targetother (o) : emac0USBD Initialized.Searching for USB device .... Could not find USB device.Error loading file: errno = 0x0.Attaching to TFFS... done.Loading /tffs0/bin/sys6000.bin... 10678464Starting at 0x10000...Instantiating /ram0 as rawFs, device = 0x1Error in boot line:machine checkException next instruction address: 0x00397f00Machine Status Register: 0x00029200Condition Register: 0x40000044Bus Error Address Register: 0x22204002Bus Error Syndrome Register: 0x00000000Task: 0x1fffd30 "tRootTask"0x1fffd30 (tRootTask): task 0x1fffd30 has had a failure and has been stopped.0x1fffd30 (tRootTask): fatal kernel task-level exception!Even with the recovery USB inserted, the 'scope detects it and loads sys6000.bin file properly, but still fails on Error in boot line: machine check.I tried playing with the bootargs since they differed from the boot logs posted by other owners on the main thread (host name : bootHost, target name (tn) : a-m6014a- [also tried a-d6014a-]) but still no luck - boot still fails on the machine check.The NVRAM battery is definitely failing - reads around 2V instead of 3V - so I'm going to replace it, but not holding out much hope that this is the root cause.Any other suggestions as to what to try next?Thanks in advance for any advice!