Products > Test Equipment

Agilent MSO-X 3014A not booting past Ref/Math/Digital/Serial LEDs

<< < (4/6) > >>

elemenoh:
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!   :D

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?

elemenoh:
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 P500

CPU:   SPEAr600
DRAM:  128 MiB
Flash: 512 KiB
NAND:  fsmc-ecc1 128 MiB
In:    serial
Out:   serial
Err:   serial
SerNum:serial number not programmed
Chip:  BD Board Rev: 4
Net:   smsc
Press space to stop autoboot:  0
## Booting kernel from Legacy Image at f8050000 ...
   Image Name:   PBOOT
   Created:      2015-05-07   8:18:27 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    37749 Bytes = 36.9 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Uncompressing Kernel Image ... OK

Starting kernel ...


Debug serial initialized ........OK
RTC: 2023-1-16   14:24:24.50 UTC

Microsoft Windows CE Bootloader Common Library Version 1.4 Built May  7 2015 01:38:03
Microsoft Windows CE 6.0 Ethernet Bootloader for the Agilent P500 board
Adaptation performed by Agilent Technologies (c) 2008


System ready!
Preparing for download...
RTC: 2023-1-16   14:24:24.54 UTC
 Loading image 1 from memory at 0xD0600000
O
BL_IMAGE_TYPE_BIN

X
XXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOOXOOOOXXXOOOOOOOOOXOOOOXOXXOXOXXOXOXOXOXXXXOOXXXOOOOOOXXOXXOXXXXXXOOOXXXOXXOOOXXXOOOXOOXOOXXOOXOXOOOOXOXOOOOOXOOOXOOOXXXOXOXXXXXXOXXXXOOX
OOOXOOXOOOOXXXOOOOXOOXXOOXOOOOOOOOOXOXOOOXOOOOOOXOXOOOOXOXOOOOOOOXOXOXOOXOXOOOXOOOXOOXOXXOXOOOXOXXXXXOXOXXOXXXXOXOXXOOOXXOXXXXXXXOXXXXXXXOXXXXOXOXXOXOOOXXXXOXXXXXOOOXXOX
OOXXOXXXOOXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXXXOXOOOXO.
XXImageStart = 0x80361000, ImageLength = 0x1ACB780, LaunchAddr = 0x80362000

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x1ACB780  Name="" Target=RAM
 Loading image 1 succeeded.
ROMHDR at Address 80361044h
Preparing launch...
RTC: 2023-1-16   14:24:27.91 UTC
Launching windows CE image by jumping at address 0x  362000

Windows CE Kernel for ARM (Thumb Enabled) Built on Mar  8 2013 at 17:05:33
Setting up for a Cold Reboot
Done Setting up for a Cold Reboot
Windows CE Firmware Init
BSP 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...done
 OALKitlStart
Firmware Init Done.
OALIoctlHalEnterI2cCriticalSection init i2c cs
++SER_Init: context Drivers\Active\14
SER_Init, dwIndex:2
SER2 got sysintr:0x00000017
SER2 Serial Port, new baud rate:0x1c200  (UARTCLK:48000000 IBRD:0x1a FBRD:0x2)
OHCI\system.c, GCFG_USBH1_SW_RST
OHCI\system.c, GCFG_USBH2_SW_RST
-EDeviceLoadEeprom 00:30:D3:20:46:AD
Phy found addr 31 (ticks=3363)
WaitForLink Start (ticks=3364)
No Link (ticks=4367)
<--EDeviceInitialize

GMAC DMA status register = 0x0
LIN: Data Valid
BALDWIN_DDI: cBaldwinHwIf::Init: Initializing...
BALDWIN_DDI: cBaldwinHwIf::Init: Scope successfully identified.
BALDWIN_DDI: cBaldwinHwIf::Init: Success!
Running infiniiVisionInstallHelper
Failed to start/configure network.
Device load time:
   NANDFLASH: 91 ms
   SNANDFLASH: 91 ms
   USB Hard Disk Drive: 91 ms

--- End code ---

elemenoh:
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 complaining :)

Thanks again for all of the help here!

tv84:

--- Quote from: elemenoh on January 16, 2023, 08:57:25 pm ---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 complaining :)

--- End quote ---

 :clap: Well done.

Let's hope that you upgraded to 2.65...  ::) or else problems may continue...

switchabl:
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.  :-+

Navigation

[0] Message Index

[#] Next page

[*] Previous page

There was an error while thanking
Thanking...
Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod