Author Topic: Agilent DSOX3054A not booting possible NAND corruption HELP! (RESOLVED) (Read 8675 times)

analogRF · « **on:** February 05, 2021, 03:34:13 pm »

after a couple of years (!) of searching and not being able to buy a 3000A/T model I finally got hold of a defective DSOX3054A which is stuck at boot. After a quick flash of several LEDs, only the REF and MATH LEDs remain on and nothing else.

Attached is what I got on the serial console and it looks to me to have a NAND flash corruption but I am not sure, I hope someone can confirm
I also ran a couple of informational commands after stopping the U-Boot which you can see in the attached file and below

Code: [Select]

U-Boot 2010.03 (Jan 26 2011 - 12:37:34)Agilent P500

CPU:   SPEAr600
DRAM:  128 MiB
Flash: 512 KiB
NAND:  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:      2011-01-27  11:38:14 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    36703 Bytes = 35.8 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Uncompressing Kernel Image ... OK

Starting kernel ...


Debug serial initialized ........OK

Microsoft Windows CE Bootloader Common Library Version 1.4 Built Jan 27 2011 02:04:15
Microsoft Windows CE 6.0 Ethernet Bootloader for the Agilent P500 board
Adaptation performed by Agilent Technologies (c) 2008


System ready!
Preparing for download...
 Loading image 1 from memory at 0xD0600000
O
BL_IMAGE_TYPE_BIN

X
XXXXOOOOXOOOOOOOOXOXXOOOOOOOOXOOXOXOOOOXXXOOOOOOOOOXOOOOXOXXOXXOXOOOXOXXXXXXOOXXOOOOOOXOOXXOXXOOOERROR: Checksum failure (expected=0x1217115  

computed=0x1217126)
****** Checksum failure on record 36, ABORT!!! ******

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x12F9870  Name="" Target=RAM
 Loading image 1 failed, trying next one
 Loading image 2 from memory at 0xD1600000

BL_IMAGE_TYPE_UNKNOWN

 Loading image 2 failed, trying next one
 All images failed

Press r to reset




================================================================================================

p500> imls
Legacy Image at F8000000:
   Image Name:   XLOADER
   Created:      2010-09-24  21:30:18 UTC
   Image Type:   ARM Linux Firmware (uncompressed)
   Data Size:    5370 Bytes = 5.2 KiB
   Load Address: d2800b00
   Entry Point:  d2800b00
   Verifying Checksum ... OK
Legacy Image at F8010000:
   Image Name:   UBOOT
   Created:      2011-01-26  19:52:00 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    194572 Bytes = 190 KiB
   Load Address: 03f00000
   Entry Point:  03f00000
   Verifying Checksum ... OK
Legacy Image at F8050000:
   Image Name:   PBOOT
   Created:      2011-01-27  11:38:14 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    36703 Bytes = 35.8 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
p500> nand
nand - NAND sub-system

Usage:
nand info - show available NAND devices
nand device [dev] - show or set current device
nand read - addr off|partition size
nand write - addr off|partition size
    read/write 'size' bytes starting at offset 'off'
    to/from memory address 'addr', skipping bad blocks.
nand erase [clean] [off size] - erase 'size' bytes from
    offset 'off' (entire device if not specified)
nand bad - show bad blocks
nand dump[.oob] off - dump page
nand scrub - really clean NAND erasing bad blocks (UNSAFE)
nand markbad off [...] - mark bad block(s) at offset (UNSAFE)
nand biterr off - make a bit error at offset (UNSAFE)
p500> nand info

Device 0: NAND 128MiB 3,3V 8-bit, sector size 128 KiB
p500> nand bad

Device 0 bad blocks:
p500>

I measured most or all of the voltages marked on board and they seem to be OK except one VP23V which is always 0V (see attached picture)
Other voltages are OK but some are less close than I thought they should be

The front USB has no power at all unless I stop the U-Boot then it gets 5.54V which seems a bit high!? (see the picture)

that's as far I have been able to go.

I have been/am reading the very very long thread on 2000/3000 and it is really next to impossible to find clear answer in 106 pages

if someone can give me a direction it is highly appreciated.

TheSteve · « **Reply #1 on:** February 05, 2021, 04:39:07 pm »

Appears to be classic NAND corruption.

nctnico · « **Reply #2 on:** February 05, 2021, 04:42:39 pm »

How about sending it to Keysight for a free repair?

analogRF · « **Reply #3 on:** February 05, 2021, 05:37:55 pm »

Quote from: nctnico on February 05, 2021, 04:42:39 pm

How about sending it to Keysight for a free repair?

are they still doing that free replacement thing? this is quite an old scope, Agilent branded S/N MY5316xxx

analogRF · « **Reply #4 on:** February 05, 2021, 05:40:00 pm »

Quote from: nctnico on February 05, 2021, 04:42:39 pm

How about sending it to Keysight for a free repair?

I would also like to repair it myself as a good experience.
I dont have a lan card (yet) but is it possible to boot it by uploading the image through the YMODEM method (serial console)?

is there any way to know what version of FW it has had?

Pinkus · « **Reply #5 on:** February 05, 2021, 05:45:32 pm »

My DSOX4K (one of the first productions) had the NAND problem too. I sent it to Keysight together with the printouts (UBoot etc.) to proof it would be the NAND. Also I mentioned in my letter that there is a service note which allows a free repair when NAND is the problem. It was repaired for free without any question. That was about a year ago.

analogRF · « **Reply #6 on:** February 05, 2021, 07:02:41 pm »

Based on Keysight website, this scope's warranty ended in Jan 2017. It seems the unit must have been manufactured in May 2013 and it has a Cal certificate with that date. No other history apparently...

Still I appreciate if someone can point me to how it can be recovered by LAN card and/or using the serial console.
I have talked to one of the forum members for a home made LAN card and hopefully I'll get that soon.
USB is powered when I stop the U-Boot, there should be a way to upload the image to through USB, no?

TheSteve · « **Reply #7 on:** February 05, 2021, 07:37:14 pm »

The new firmware is read in via USB but UBOOT has no support for it, the scope needs to be booted up. The firmware can be loaded via the serial console but that will not always work. Depending on the level of corruption the scope may not finish booting from the image enough to select the firmware upgrade option. I do all recoveries via network. Often I need to try various firmware versions to see which will boot as you need them to match, or be very close. Without booting and being able to telnet in I'm not aware of anyway to know the exact version installed.

analogRF · « **Reply #8 on:** February 05, 2021, 07:41:35 pm »

Quote from: TheSteve on February 05, 2021, 07:37:14 pm

The new firmware is read in via USB but UBOOT has no support for it, the scope needs to be booted up. The firmware can be loaded via the serial console but that will not always work. Depending on the level of corruption the scope may not finish booting from the image enough to select the firmware upgrade option. I do all recoveries via network. Often I need to try various firmware versions to see which will boot as you need them to match, or be very close. Without booting and being able to telnet in I'm not aware of anyway to know the exact version installed.

I am waiting for a LAN card from one of the members.
In the mean time, can you please point me to the correct/verified procedure for the recovery from network?
Do I need to set up tftp on my laptop?

analogRF · « **Reply #9 on:** February 05, 2021, 09:13:54 pm »

Ok I just tried the YMODEM method using serial console with nk.nb0 extracted from 2.35 FW
I followed instructions by titiris here (msg # 2092)
https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg2136181/?topicseen#msg2136181

the uploading went well in 35 minutes but after executing the 'go' command this is what I got:

Code: [Select]

p500> loady 0x0361000 115200
## Ready for binary (ymodem) download to 0x00361000 at 115200 bps...
CCxyzModem - CRC mode, 1(SOH)/19482(STX)/0(CAN) packets, 5 retries
## Total Size      = 0x013064d4 = 19948756 Bytes

p500> go 0x00362000

## Starting application at 0x00362000 ...
Windows CE Kernel for ARM (Thumb Enabled) Built on Jan 24 2013 at 14:52:37
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 Jun 18 2013)
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
ERROR: C:\WINCE600\PLATFORM\COMMON\SRC\SOC\STM\SPEARHEAD600\DRIVERS\GPIO\.\sh600_gpio_hw.cpp line 170: GPB driver, RegQueryDword('ISTPriority') failed, status:2
ERROR: C:\WINCE600\PLATFORM\COMMON\SRC\SOC\STM\SPEARHEAD600\DRIVERS\GPIO\.\sh600_gpio_hw.cpp line 170: GPB driver, RegQueryDword('ISTPriority') failed, status:2
++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:DA:4C
Phy found addr 31 (ticks=2707)
WaitForLink Start (ticks=2709)
No Link (ticks=3711)
<--EDeviceInitialize

GMAC DMA status register = 0x0
BALDWIN_DDI: cBaldwinHwIf::Init: Initializing...
BALDWIN_DDI: cBaldwinHwIf::Init: Scope successfully identified.
BALDWIN_DDI: cBaldwinHwIf::Init: Success!
Running infiniiVisionInstallHelper
ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETBOOTMENAME
Failed to start/configure network.
Time for NANDFLASH to load: 0 ms.
Time for SNANDFLASH to load: 0 ms.
Time for USB Hard Disk Drive to load: 0 ms.
Starting ProcessStartupFolder
ProcessStartupFolder: \usb\Startup\
                                   running \usb\Startup\infiniivision.lnk...

any clue?

is it because perhaps the version on the unit does not match 2.35?

wraper · « **Reply #10 on:** February 05, 2021, 09:38:45 pm »

Keysight repairs these scopes with NAND corruption for free even with expired warranty by replacing main board, as it's a widespread issue. Trying repairing this issue yourself is lame and might end with a very large expense, as it may end with you paying a full repair price to keysight. Not to say you will be left with old crappy NAND

TheSteve · « **Reply #11 on:** February 05, 2021, 10:32:32 pm »

The original corruption is likely preventing it from booting all of the way. It could also be a version mismatch.

analogRF · « **Reply #12 on:** February 06, 2021, 12:15:41 am »

Quote from: TheSteve on February 05, 2021, 10:32:32 pm

The original corruption is likely preventing it from booting all of the way. It could also be a version mismatch.

Can the network method work then?

is it possible that the dead 23V voltage (see the first post) is the reason?
so far i though maybe that voltage will come alive after certain point in boot process
but maybe it should always be there?

I wish someone could be kind enough to check when that VP23V line comes on after turn on

TheSteve · « **Reply #13 on:** February 06, 2021, 02:13:03 am »

Quote from: analogRF on February 06, 2021, 12:15:41 am

Quote from: TheSteve on February 05, 2021, 10:32:32 pm
The original corruption is likely preventing it from booting all of the way. It could also be a version mismatch.

Can the network method work then?

is it possible that the dead 23V voltage (see the first post) is the reason?
so far i though maybe that voltage will come alive after certain point in boot process
but maybe it should always be there?

I wish someone could be kind enough to check when that VP23V line comes on after turn on

I am quite sure with a network card we'll get it to work. Send me a PM when you get it and we'll take care of it.

Jwalling · « **Reply #14 on:** February 06, 2021, 09:56:17 am »

The document that Keysight did not make public for some reason.

analogRF · « **Reply #15 on:** February 06, 2021, 11:34:59 am »

Quote from: Jwalling on February 06, 2021, 09:56:17 am

The document that Keysight did not make public for some reason.

Thanks, this can really be helpful if I want to send it to Keysight for repair

well well well...according to this document, they may not consider my scope as having a NAND corruption after all
I dont have a boot loop and the LEDs dont "continually flash through the boot sequence"
what happens is that first a bunch of LEDs very quickly flash simultaneously and then MATH and REF LEDs come on and stay on forever.

If they really stick to their flowchart, then I guess they will consider this as a normal repair procedure = $4026 CAD + TAX

which is a non starter for me

analogRF · « **Reply #16 on:** February 06, 2021, 01:05:27 pm »

even though there is no doubt that this is a NAND corruption issue but I am beginning to think that not having that 23V rail
could also be a secondary problem that prevented from booting after I uploaded the image through serial port

does anybody know if that 23V rail should always be ON after power is switched on or if it comes alive after a while?

Pinkus · « **Reply #17 on:** February 06, 2021, 01:40:50 pm »

Quote from: analogRF on February 06, 2021, 11:34:59 am

well well well...according to this document, they may not consider my scope as having a NAND corruption after all
I dont have a boot loop and the LEDs dont "continually flash through the boot sequence"
what happens is that first a bunch of LEDs very quickly flash simultaneously and then MATH and REF LEDs come on and stay on forever.

If they really stick to their flowchart, then I guess they will consider this as a normal repair procedure = $4026 CAD + TAX
which is a non starter for me

a) As Keysight is replacing the main board when the NAND problem occurs, it seems just to re-install the firmware through the UART interface is not the best/preferred solution. If this would be an acceptable long term solution, Keysight would do it by themselves. Instead they are always changing the expensive board, lets assume they know why.
b) My scope did NOT show the usual LED-cycle boot loop too. Nevertheless it was repaired for free.
c) A check through Keysight is free of charge. You may send it in and IF they decide that it is not a NAND problem (=you would have to pay a new board), then you still can decline the repair and you will get your unit back free of charge.

Thus a) + b) + c) shows: they is NO REASON for messing with this by yourself before Keysight had a look at it. Otherwise this might end in an expensive experience.
This is what I did and a I got a scope with a brand new and freshly calibrated main board back. If not, I would have tried to replace the NAND chip.

So my advise: send to Keysight, add a printout of the UBoot prototcol and point to the NAND corruption service note.

Pinkus · « **Reply #18 on:** February 06, 2021, 01:49:06 pm »

Mmmmhhh. I was just reading the service note.
At page 1 it says: "NO CHARGE AVAILABLE UNTIL: 31-Oct-2019".
I am wondering if this means that DSOX/MSOX 2K/3K with NAND corruption will not be repaired for free anymore?

analogRF · « **Reply #19 on:** February 06, 2021, 02:03:00 pm »

Quote from: Pinkus on February 06, 2021, 01:49:06 pm

Mmmmhhh. I was just reading the service note.
At page 1 it says: "NO CHARGE AVAILABLE UNTIL: 31-Oct-2019".
I am wondering if this means that DSOX/MSOX 2K/3K with NAND corruption will not be repaired for free anymore?

yes I saw that too

Still it is a bit hard to believe Keysight will keep replacing the board of these scopes for free until all NAND corrupted boards out there are replaced!
this particular scope is almost 8 years old...but since this line of scopes has not ended yet, maybe they still do that repair for free...I'll call them on Monday.
I will get my LAN board o Tuesday I think and if I dont reach an agreement with Keysight, I'll try that network method

However, that missing 23V rail is still bugging me

Pinkus · « **Reply #20 on:** February 06, 2021, 02:42:17 pm »

Quote from: analogRF on February 06, 2021, 02:03:00 pm

...I'll call them on Monday.

Been there .... you will not get a service technician on the line, only administrative people and they will not give you any helpful answers. They will only tell you, you will have to send in the scope.
Good luck!!

Bud · « **Reply #21 on:** February 06, 2021, 03:39:37 pm »

You were too quick to load a random replacement image... The log gives you information on the image length and expected checksum (likely crc32 checksum). Get a few firmware versions nb0 files and compare their length and checksum against the ones from the log and see if you can find a match. That will be your replacement image to load via Ymodem.

Quote from: analogRF on February 05, 2021, 03:34:13 pm

Code: [Select]
... Loading image 1 from memory at 0xD0600000 O BL_IMAGE_TYPE_BIN X XXXXOOOOXOOOOOOOOXOXXOOOOOOOOXOOXOXOOOOXXXOOOOOOOOOXOOOOXOXXOXXOXOOOXOXXXXXXOOXXOOOOOOXOOXXOXXOOOERROR: Checksum failure (expected=0x1217115 computed=0x1217126) ****** Checksum failure on record 36, ABORT!!! ****** Completed file(s): ------------------------------------------------------------------------------- [0]: Address=0x80361000 Length=0x12F9870 Name="" Target=RAM

Bud · « **Reply #22 on:** February 06, 2021, 03:45:07 pm »

Code: [Select]

 doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETBOOTMENAME
Failed to start/configure network.
Time for NANDFLASH to load: 0 ms.
Time for SNANDFLASH to load: 0 ms.
Time for USB Hard Disk Drive to load: 0 ms.
Starting ProcessStartupFolder
ProcessStartupFolder: \usb\Startup\
                                   running \usb\Startup\infiniivision.lnk...

Based on the log, the FPGA was initialized fine, and Windows loaded as well. There was an error configuring the LAN so you may not be able to use a LAN card.

analogRF · « **Reply #23 on:** February 06, 2021, 04:00:54 pm »

Quote from: Bud on February 06, 2021, 03:39:37 pm

You were too quick to load a random replacement image... The log gives you information on the image length and expected checksum (likely crc32 checksum). Get a few firmware versions nb0 files and compare their length and checksum against the ones from the log and see if you can find a match. That will be your replacement image to load via Ymodem.

Quote from: analogRF on February 05, 2021, 03:34:13 pm

Code: [Select]
... Loading image 1 from memory at 0xD0600000 O BL_IMAGE_TYPE_BIN X XXXXOOOOXOOOOOOOOXOXXOOOOOOOOXOOXOXOOOOXXXOOOOOOOOOXOOOOXOXXOXXOXOOOXOXXXXXXOOXXOOOOOOXOOXXOXXOOOERROR: Checksum failure (expected=0x1217115 computed=0x1217126) ****** Checksum failure on record 36, ABORT!!! ****** Completed file(s): ------------------------------------------------------------------------------- [0]: Address=0x80361000 Length=0x12F9870 Name="" Target=RAM

excellent observation ! thanks

it does not match V2.35
since it is smaller than the size of 2.35, I guess it must be 2.30 perhaps?
I'll try that

EDIT: it matches the size of nk.nb0 file for V2.30 (which also makes sense based on the manufacturing date of this scope if we assume the owner never bothered to upgrade firmware)
I'll try that...but i have my doubts...

analogRF · « **Reply #24 on:** February 06, 2021, 04:02:58 pm »

Quote from: Bud on February 06, 2021, 03:45:07 pm

Code: [Select]
doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETBOOTMENAME Failed to start/configure network. Time for NANDFLASH to load: 0 ms. Time for SNANDFLASH to load: 0 ms. Time for USB Hard Disk Drive to load: 0 ms. Starting ProcessStartupFolder ProcessStartupFolder: \usb\Startup\ running \usb\Startup\infiniivision.lnk...
Based on the log, the FPGA was initialized fine, and Windows loaded as well. There was an error configuring the LAN so you may not be able to use a LAN card.

i am still thinking it h~~as something to do with that missing 23V rail~~. which is coincidentally an inch above the LAN card connector!
not saying that means anything but...

EDIT: no, the 23V rail comes to life later on

analogRF · « **Reply #25 on:** February 06, 2021, 04:15:22 pm »

one problem with this method is that the python tool that is used in place of wince cab manager to create the correct file names from the extracted infiniivisionSetup.cab leaves out one file (INFINI~1.000) and it is because this name does not actually exist in the _setup.xml file
so I think an important component of the infiniivisionSetup might be missing on the USB

I hope PA0PBZ could shed some light on this.

PA0PBZ · « **Reply #26 on:** February 06, 2021, 04:40:32 pm »

Hi,

I'm surely not the creator of the python file, if I posted it I did this to help someone. I am however the creator of the TFTP program where you can boot the scope from an image file on your pc instead of the flash, I guess you already found the details of that. Maybe (I never tried) you can then update the scope the normal way. However if your flash is damaged this will be a lost case.

analogRF · « **Reply #27 on:** February 06, 2021, 05:20:10 pm »

OMG!
I tried the same procedure with V2.30 and this is what happened:

Code: [Select]

p500> loady 0x0361000 115200
## Ready for binary (ymodem) download to 0x00361000 at 115200 bps...
CCxyzModem - CRC mode, 1(SOH)/19431(STX)/0(CAN) packets, 6 retries
## Total Size      = 0x012f9870 = 19896432 Bytes
p500> go 0x00362000
## Starting application at 0x00362000 ...
Windows CE Kernel for ARM (Thumb Enabled) Built on May  7 2012 at 12:47:43
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 26 2013)
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
ERROR: C:\WINCE600\PLATFORM\COMMON\SRC\SOC\STM\SPEARHEAD600\DRIVERS\GPIO\.\sh600_gpio_hw.cpp line 170: GPB driver, RegQueryDword('ISTPriority') failed, status:2
ERROR: C:\WINCE600\PLATFORM\COMMON\SRC\SOC\STM\SPEARHEAD600\DRIVERS\GPIO\.\sh600_gpio_hw.cpp line 170: GPB driver, RegQueryDword('ISTPriority') failed, status:2
++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:DA:4C
Phy found addr 31 (ticks=2700)
WaitForLink Start (ticks=2702)
No Link (ticks=3704)
<--EDeviceInitialize

GMAC DMA status register = 0x0
BALDWIN_DDI: cBaldwinHwIf::Init: Initializing...
BALDWIN_DDI: cBaldwinHwIf::Init: Scope successfully identified.
BALDWIN_DDI: cBaldwinHwIf::Init: Success!
Running infiniiVisionInstallHelper
ERROR: OALIoCtlHalGetDeviceInfo: Device doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETBOOTMENAME
Failed to start/configure network.
Starting ProcessStartupFolder
ProcessStartupFolder: \usb\Startup\
                                   running \usb\Startup\infiniivision.lnk...
Ending ProcessStartupFolder
                           Our command line is
Performing Startup
Released build, Mar 26 2013, 02:17:15
Initializing FPGA...
****
FPGA Type: Wyoming
Ver: 1.094 Released
Build Time: Thu Nov 08 15:08:20 2012
Build Machine: DW3647M2
****
No option module detected
Keyboard firmware version 32... ok
Keyboard Info: Board id 1, Board rev 3
Keyboard Info: Board id 1, Board rev 3
Startup sequence is complete.
System has been running 52.940346 seconds
Start Up Sequence 38.887882
Memory Load 50%
   System Physical Memory 39.098 / 79.133 MB
   Process Virtual Memory 48.188 / 1024.000 MB
-----> InfiniiVision is running <-----

BUT THERE IS NO DISPLAY
scope is clearly working, I can turn on/off channels, relays click when I do Autoset, etc....but there is no display !!
I am not sure if the backlight is dead or something else...

I cannot upgrade the firmware to make it permanent so I have to let it running for now to figure out what to do

any ideas folks??

analogRF · « **Reply #28 on:** February 06, 2021, 05:34:24 pm »

there are a couple of error messages in the log, could they be related to the Display being blank?
can someone decipher what those mean?

that 23V rail came to life by the way, after I give the "go" command to run the image. so that 's not a problem

analogRF · « **Reply #29 on:** February 06, 2021, 05:45:48 pm »

Quote from: tv84 on February 06, 2021, 05:06:58 pm

Quote from: analogRF on February 06, 2021, 04:15:22 pm
one problem with this method is that the python tool that is used in place of wince cab manager to create the correct file names from the extracted infiniivisionSetup.cab leaves out one file (INFINI~1.000) and it is because this name does not actually exist in the _setup.xml file so I think an important component of the infiniivisionSetup might be missing on the USB

If that is the case even the official tool wouldn't be able to recreate the filename! I find that strange.

yes, but that's how it is. I checked multiple times with multiple firmware images, that file's name does not exist in the _setup.xml
but it think it must be a needed component...i don;t know how the system could decipher its name...it's a binary file but by looking at some of the words that appear in the content it seems to me it's a important component....maybe it belongs to 2000A scopes??
or maybe it the source of my display problem??

analogRF · « **Reply #30 on:** February 06, 2021, 05:47:41 pm »

Quote from: Bud on February 06, 2021, 03:45:07 pm

Code: [Select]
doesn't support IOCTL_HAL_GET_DEVICE_INFO::SPI_GETBOOTMENAME Failed to start/configure network. Time for NANDFLASH to load: 0 ms. Time for SNANDFLASH to load: 0 ms. Time for USB Hard Disk Drive to load: 0 ms. Starting ProcessStartupFolder ProcessStartupFolder: \usb\Startup\ running \usb\Startup\infiniivision.lnk...
Based on the log, the FPGA was initialized fine, and Windows loaded as well. There was an error configuring the LAN so you may not be able to use a LAN card.

yes, I also think that there might be a problem with the Network interface and LAN card will not work

Bud · « **Reply #31 on:** February 06, 2021, 08:16:33 pm »

Perhaps the Windows Registry is corrupted elsewhere in NAND. You may need to reinstall Infiniivision application (the nb0 file only contains windows kernel). But it is difficult because the scope is blind (no display) and LAN may not work either.
I would suggest trying making a USB stick with infiniivisionStartupOverride.txt (just an empty file) in the root folder and put the application files on it. The scope then will boot from USB. Try following this post:

https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg366721/#msg366721

Bud · « **Reply #32 on:** February 06, 2021, 08:19:58 pm »

Quote from: analogRF on February 06, 2021, 05:45:48 pm

Quote from: tv84 on February 06, 2021, 05:06:58 pm
Quote from: analogRF on February 06, 2021, 04:15:22 pm
one problem with this method is that the python tool that is used in place of wince cab manager to create the correct file names from the extracted infiniivisionSetup.cab leaves out one file (INFINI~1.000) and it is because this name does not actually exist in the _setup.xml file so I think an important component of the infiniivisionSetup might be missing on the USB

If that is the case even the official tool wouldn't be able to recreate the filename! I find that strange.

yes, but that's how it is. I checked multiple times with multiple firmware images, that file's name does not exist in the _setup.xml
but it think it must be a needed component...i don;t know how the system could decipher its name...it's a binary file but by looking at some of the words that appear in the content it seems to me it's a important component....maybe it belongs to 2000A scopes??
or maybe it the source of my display problem??

The .000 file has the description of the CAB folder structure, registry keys and stuff. It is not an application file and is only needed to unpack the CAB.

analogRF · « **Reply #33 on:** February 06, 2021, 09:36:25 pm »

Scope is fixed and up and running

Now go back to the long thread and look for option enabling methods

here is the story
Thanks to "Bud" I was sure the firmware on the unit was 2.30 so I prepared the USB and nk.nb0 based on "titiris" instructions here (msg # 2092)
https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg2136181/?topicseen#msg2136181

well, it didn't work. Behaved exactly like the 2.35 that I posted the log before.
so I realized that perhaps I should modify the \usb\Startup\infiniivision.lnk file to have this line 51#\usb\Secure\infiniiVision\infiniivisionLauncher.exe instead of what 'titiris' had said (48#\Secure\infiniiVision\infiniivisionLauncher.exe) (by the way 48 must be 47 but it didnt help anyway)

after that, I uploaded the nk.nb0 again and ran the go command and scope started

but no display

I knew the scope was functioning but screen was dark.
to my embarrassment I found that the small ribbon cable (see the attached picture) was slightly out and was not making conneciton

so I fixed that and again took me 30 minutes to upload the nk.nb0 again with YMODEM and BINGOOOOO

scope worked - see the picture

I think I made a huge mistake and upgraded the firmware to 2.60 (well first to 2.35 and then to 2.41 and then to 2.50 and then to 2.60)
scope boots perfectly fine now and works except two of the softkey buttons under the screen (number 3 and 6)

but now I realize to hack the options I should have stayed with V2.35, am I right??

can someone point me to a method to enable the options with 2.60 FW please?

by the way I have the console logs of all booting from various firmwares and also console logs during firmware upgrades. I post two of them here
but if someone is looking for console logs let me know

Code: [Select]

================  scope is running with V2.50 and I start FW upgrade to 2.60 here===========================================
============================================================================================================================

** BEGIN ** ExtractFileFromCabFile: RECIPE.XML
** END   ** ExtractFileFromCabFile: RECIPE.XML: 51 ms
PRE: "" -> ""
** BEGIN ** ExtractFileFromCabFile: infiniiVisionSetup.cab
** END   ** ExtractFileFromCabFile: infiniiVisionSetup.cab: 16652 ms
** BEGIN ** ExtractFileFromCabFile: _setup.xml
** END   ** ExtractFileFromCabFile: _setup.xml: 45 ms
** BEGIN ** ExtractFileFromCabFile: INFINI~1.176
** END   ** ExtractFileFromCabFile: INFINI~1.176: 42 ms
SHIM DLL, LoadRealDll [PalSStorage.dll] for [AgilentPalSStorage.dll]
SHIM [AgilentPalSStorage.dll] Get Process Addresses

** BEGIN ** ExtractFileFromCabFile: RECIPE.XML
** END   ** ExtractFileFromCabFile: RECIPE.XML: 25 ms
PRE: "" -> ""
SHIM DLL, LoadRealDll [PalSStorage.dll] for [AgilentPalSStorage.dll]
SHIM [AgilentPalSStorage.dll] Get Process Addresses

** BEGIN ** ExtractFileFromCabFile: RECIPE.XML
** END   ** ExtractFileFromCabFile: RECIPE.XML: 19 ms
PRE: "" -> ""
** BEGIN ** ExtractFileFromCabFile: updateSplashImage.wvga.bin
** END   ** ExtractFileFromCabFile: updateSplashImage.wvga.bin: 8 ms
GetNextUsbEvent, bOpenContextClosing
EventThread, ERROR ABORTED or INVALID HANDLE, exiting
GetSetupPacket, tmcDriverClosing 2
** BEGIN ** ExtractFileFromCabFile: auxInstallStep.exe
** END   ** ExtractFileFromCabFile: auxInstallStep.exe: 404 ms
** BEGIN ** ProcessRecipeStep: \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\auxInstallStep.exe -v
=== Aux Step: -v ===
Skipped.
** END   ** ProcessRecipeStep: \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\auxInstallStep.exe -v: 22 ms
** BEGIN ** ExtractFileFromCabFile: nk.bin.comp
** END   ** ExtractFileFromCabFile: nk.bin.comp: 7128 ms
** BEGIN ** ProcessRecipeStep: \windows\loadP500Flash -u ceImage2 \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\nk.bin.comp
SHIM DLL, LoadRealDll [PalSysManagement.dll] for [AgilentPalSysManagement.dll]
SHIM [AgilentPalSysManagement.dll] Get Process Addresses
FWUpdate: image 3 value not defined
                                   0.000000 complete (Erasing)
100.000000 complete (Erasing)
0.000000 complete (Writing)
2.545321 complete (Writing)
5.090642 complete (Writing)
7.635963 complete (Writing)
10.181284 complete (Writing)
12.726605 complete (Writing)
15.271926 complete (Writing)
17.817247 complete (Writing)
20.362568 complete (Writing)
22.907889 complete (Writing)
25.453210 complete (Writing)
27.998531 complete (Writing)
30.543852 complete (Writing)
33.089173 complete (Writing)
35.634494 complete (Writing)
38.179815 complete (Writing)
40.725136 complete (Writing)
43.270457 complete (Writing)
45.815778 complete (Writing)
48.361099 complete (Writing)
50.906420 complete (Writing)
53.451741 complete (Writing)
55.997062 complete (Writing)
58.542383 complete (Writing)
61.087704 complete (Writing)
63.633025 complete (Writing)
66.178346 complete (Writing)
68.723667 complete (Writing)
71.268988 complete (Writing)
73.814309 complete (Writing)
76.359630 complete (Writing)
78.904951 complete (Writing)
81.450272 complete (Writing)
83.995593 complete (Writing)
86.540914 complete (Writing)
89.086235 complete (Writing)
91.631556 complete (Writing)
94.176877 complete (Writing)
96.722198 complete (Writing)
99.267519 complete (Writing)
100.000000 complete (Writing)
0.000000 complete (Verifying)
2.545321 complete (Verifying)
5.090642 complete (Verifying)
7.635963 complete (Verifying)
10.181284 complete (Verifying)
12.726605 complete (Verifying)
15.271926 complete (Verifying)
17.817247 complete (Verifying)
20.362568 complete (Verifying)
22.907889 complete (Verifying)
25.453210 complete (Verifying)
27.998531 complete (Verifying)
30.543852 complete (Verifying)
33.089173 complete (Verifying)
35.634494 complete (Verifying)
38.179815 complete (Verifying)
40.725136 complete (Verifying)
43.270457 complete (Verifying)
45.815778 complete (Verifying)
48.361099 complete (Verifying)
50.906420 complete (Verifying)
53.451741 complete (Verifying)
55.997062 complete (Verifying)
58.542383 complete (Verifying)
61.087704 complete (Verifying)
63.633025 complete (Verifying)
66.178346 complete (Verifying)
68.723667 complete (Verifying)
71.268988 complete (Verifying)
73.814309 complete (Verifying)
76.359630 complete (Verifying)
78.904951 complete (Verifying)
81.450272 complete (Verifying)
83.995593 complete (Verifying)
86.540914 complete (Verifying)
89.086235 complete (Verifying)
91.631556 complete (Verifying)
94.176877 complete (Verifying)
96.722198 complete (Verifying)
99.267519 complete (Verifying)
100.000000 complete (Verifying)
** END   ** ProcessRecipeStep: \windows\loadP500Flash -u ceImage2 \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\nk.bin.comp: 8084 ms
** BEGIN ** ExtractFileFromCabFile: updateBootLoaders2.exe
** END   ** ExtractFileFromCabFile: updateBootLoaders2.exe: 317 ms
** BEGIN ** ExtractFileFromCabFile: pboot_rel.bin
** END   ** ExtractFileFromCabFile: pboot_rel.bin: 352 ms
** BEGIN ** ProcessRecipeStep: \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\updatebootloaders2.exe
Update XLOADER at address f8000000.
XLOADER is up to date. Skipping
Update UBOOT at address f8010000.
UBOOT is up to date. Skipping
Update PBOOT at address f8050000.
PBOOT is up to date. Skipping
** END   ** ProcessRecipeStep: \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\updatebootloaders2.exe: 95 ms
** BEGIN ** ExtractFileFromCabFile: nk.bin.comp
** END   ** ExtractFileFromCabFile: nk.bin.comp: 7103 ms
** BEGIN ** ProcessRecipeStep: \windows\loadP500Flash -u ceImage1 \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\nk.bin.comp
SHIM DLL, LoadRealDll [PalSysManagement.dll] for [AgilentPalSysManagement.dll]
SHIM [AgilentPalSysManagement.dll] Get Process Addresses
0.000000 complete (Erasing)
100.000000 complete (Erasing)
0.000000 complete (Writing)
2.545321 complete (Writing)
5.090642 complete (Writing)
7.635963 complete (Writing)
10.181284 complete (Writing)
12.726605 complete (Writing)
15.271926 complete (Writing)
17.817247 complete (Writing)
20.362568 complete (Writing)
22.907889 complete (Writing)
25.453210 complete (Writing)
27.998531 complete (Writing)
30.543852 complete (Writing)
33.089173 complete (Writing)
35.634494 complete (Writing)
38.179815 complete (Writing)
40.725136 complete (Writing)
43.270457 complete (Writing)
45.815778 complete (Writing)
48.361099 complete (Writing)
50.906420 complete (Writing)
53.451741 complete (Writing)
55.997062 complete (Writing)
58.542383 complete (Writing)
61.087704 complete (Writing)
63.633025 complete (Writing)
66.178346 complete (Writing)
68.723667 complete (Writing)
71.268988 complete (Writing)
73.814309 complete (Writing)
76.359630 complete (Writing)
78.904951 complete (Writing)
81.450272 complete (Writing)
83.995593 complete (Writing)
86.540914 complete (Writing)
89.086235 complete (Writing)
91.631556 complete (Writing)
94.176877 complete (Writing)
96.722198 complete (Writing)
99.267519 complete (Writing)
100.000000 complete (Writing)
0.000000 complete (Verifying)
2.545321 complete (Verifying)
5.090642 complete (Verifying)
7.635963 complete (Verifying)
10.181284 complete (Verifying)
12.726605 complete (Verifying)
15.271926 complete (Verifying)
17.817247 complete (Verifying)
20.362568 complete (Verifying)
22.907889 complete (Verifying)
25.453210 complete (Verifying)
27.998531 complete (Verifying)
30.543852 complete (Verifying)
33.089173 complete (Verifying)
35.634494 complete (Verifying)
38.179815 complete (Verifying)
40.725136 complete (Verifying)
43.270457 complete (Verifying)
45.815778 complete (Verifying)
48.361099 complete (Verifying)
50.906420 complete (Verifying)
53.451741 complete (Verifying)
55.997062 complete (Verifying)
58.542383 complete (Verifying)
61.087704 complete (Verifying)
63.633025 complete (Verifying)
66.178346 complete (Verifying)
68.723667 complete (Verifying)
71.268988 complete (Verifying)
73.814309 complete (Verifying)
76.359630 complete (Verifying)
78.904951 complete (Verifying)
81.450272 complete (Verifying)
83.995593 complete (Verifying)
86.540914 complete (Verifying)
89.086235 complete (Verifying)
91.631556 complete (Verifying)
94.176877 complete (Verifying)
96.722198 complete (Verifying)
99.267519 complete (Verifying)
100.000000 complete (Verifying)
** END   ** ProcessRecipeStep: \windows\loadP500Flash -u ceImage1 \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\nk.bin.comp: 8081 ms
** BEGIN ** ExtractFileFromCabFile: fpga2000a.bin
** END   ** ExtractFileFromCabFile: fpga2000a.bin: 102 ms
** BEGIN ** ProcessRecipeStep: \windows\loadP500Flash -u fpga --target economy \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\fpga2000a.bin
Hardware does not match the specified target (-t).
FPGA update failed!
** END   ** ProcessRecipeStep: \windows\loadP500Flash -u fpga --target economy \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\fpga2000a.bin: 392 ms
** BEGIN ** ExtractFileFromCabFile: fpga3000a.bin
** END   ** ExtractFileFromCabFile: fpga3000a.bin: 231 ms
** BEGIN ** ProcessRecipeStep: \windows\loadP500Flash -u fpga --target performance \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\fpga3000a.bin
SHIM DLL, LoadRealDll [PalSysManagement.dll] for [AgilentPalSysManagement.dll]
SHIM [AgilentPalSysManagement.dll] Get Process Addresses
** END   ** ProcessRecipeStep: \windows\loadP500Flash -u fpga --target performance \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\fpga3000a.bin: 681 ms
** BEGIN ** ExtractFileFromCabFile: cleanupFileSystem.exe
** END   ** ExtractFileFromCabFile: cleanupFileSystem.exe: 285 ms
** BEGIN ** ProcessRecipeStep: \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\cleanupFileSystem.exe
**** CleanupInfiniiVisionFolder ****
**** CleanupInfiniiVisionFolder ****
**** CleanupInfiniiVisionFolder ****
**** CleanupInfiniiVisionFolder ****
**** CleanupInfiniiVisionFolder ****
   DELETED: \secure\infiniiVision\web\Lxi\Identification\Default.asp
   DELETED: \secure\infiniiVision\web\Lxi\Identification\LXIIdentification.xsd
   DELETED: \secure\infiniiVision\web\Lxi\Identification\
   DELETED: \secure\infiniiVision\web\Lxi\
**** CleanupInfiniiVisionFolder ****
**** CleanupInfiniiVisionFolder ****
   DELETED: \secure\infiniiVision\web\include\web-socket-js\WebSocketMain.swf
   DELETED: \secure\infiniiVision\web\include\web-socket-js\swfobject.js
   DELETED: \secure\infiniiVision\web\include\web-socket-js\web_socket.min.js
   DELETED: \secure\infiniiVision\web\include\web-socket-js\
   DELETED: \secure\infiniiVision\web\include\vnc.min.js
   DELETED: \secure\infiniiVision\web\include\
**** CleanupInfiniiVisionFolder ****
   DELETED: \secure\infiniiVision\web\css\AGBD____.TTF
   DELETED: \secure\infiniiVision\web\css\KeysightSansBold.ttf
   DELETED: \secure\infiniiVision\web\css\default.min.css
   DELETED: \secure\infiniiVision\web\css\
**** CleanupInfiniiVisionFolder ****
   DELETED: \secure\infiniiVision\web\help\helpBrowserWebControl.asp
   DELETED: \secure\infiniiVision\web\help\helpGetImage.asp
   DELETED: \secure\infiniiVision\web\help\helpHome.asp
   DELETED: \secure\infiniiVision\web\help\helpHomeAdv.asp
   DELETED: \secure\infiniiVision\web\help\helpInfoCal.html
   DELETED: \secure\infiniiVision\web\help\helpInfoOptions.html
   DELETED: \secure\infiniiVision\web\help\helpInfoVersion.asp
   DELETED: \secure\infiniiVision\web\help\helpModifyConfig.asp
   DELETED: \secure\infiniiVision\web\help\helpNav.asp
   DELETED: \secure\infiniiVision\web\help\helpRecall.asp
   DELETED: \secure\infiniiVision\web\help\helpRemoteFrontPanel.asp
   DELETED: \secure\infiniiVision\web\help\helpRemoteSCPICommands.asp
   DELETED: \secure\infiniiVision\web\help\helpSave.asp
   DELETED: \secure\infiniiVision\web\help\helpSaveRecall.asp
   DELETED: \secure\infiniiVision\web\help\helpStyle.css
   DELETED: \secure\infiniiVision\web\help\helpVar.asp
   DELETED: \secure\infiniiVision\web\help\helpViewConfig.asp
   DELETED: \secure\infiniiVision\web\help\
**** CleanupInfiniiVisionFolder ****
   DELETED: \secure\infiniiVision\web\image\IEstep1.png
   DELETED: \secure\infiniiVision\web\image\IEstep2.png
   DELETED: \secure\infiniiVision\web\image\IEstep3.png
   DELETED: \secure\infiniiVision\web\image\IEstep4.png
   DELETED: \secure\infiniiVision\web\image\bottomKbLabelWeb.png
   DELETED: \secure\infiniiVision\web\image\brand.png
   DELETED: \secure\infiniiVision\web\image\down-over.gif
   DELETED: \secure\infiniiVision\web\image\down.gif
   DELETED: \secure\infiniiVision\web\image\entryLed.png
   DELETED: \secure\infiniiVision\web\image\filltrans.gif
   DELETED: \secure\infiniiVision\web\image\instrumentBanner.gif
   DELETED: \secure\infiniiVision\web\image\instrumentImage.jpg
   DELETED: \secure\infiniiVision\web\image\kbLabel2ChanWeb.png
   DELETED: \secure\infiniiVision\web\image\kbLabel4ChanWeb.png
   DELETED: \secure\infiniiVision\web\image\keyboard.gif
   DELETED: \secure\infiniiVision\web\image\labelPanelWeb.png
   DELETED: \secure\infiniiVision\web\image\line-heading.gif
   DELETED: \secure\infiniiVision\web\image\lxi.jpg
   DELETED: \secure\infiniiVision\web\image\m2XX2A.jpg
   DELETED: \secure\infiniiVision\web\image\m2XX4A.jpg
   DELETED: \secure\infiniiVision\web\image\m3XX2A.jpg
   DELETED: \secure\infiniiVision\web\image\m3XX4A.jpg
   DELETED: \secure\infiniiVision\web\image\popupMenu.jpg
   DELETED: \secure\infiniiVision\web\image\popupMenu_wvga.jpg
   DELETED: \secure\infiniiVision\web\image\rightKbLabelWeb.png
   DELETED: \secure\infiniiVision\web\image\runStop.png
   DELETED: \secure\infiniiVision\web\image\single.png
   DELETED: \secure\infiniiVision\web\image\softkey.jpg
   DELETED: \secure\infiniiVision\web\image\softkey_wvga.jpg
   DELETED: \secure\infiniiVision\web\image\splash.png
   DELETED: \secure\infiniiVision\web\image\splashLoad.png
   DELETED: \secure\infiniiVision\web\image\splashSorry.png
   DELETED: \secure\infiniiVision\web\image\touchIcon.png
   DELETED: \secure\infiniiVision\web\image\up-over.gif
   DELETED: \secure\infiniiVision\web\image\up.gif
   DELETED: \secure\infiniiVision\web\image\waveNarrow.png
   DELETED: \secure\infiniiVision\web\image\waveShort.png
   DELETED: \secure\infiniiVision\web\image\waveTall.png
   DELETED: \secure\infiniiVision\web\image\waveWide.png
   DELETED: \secure\infiniiVision\web\image\web-enable.png
   DELETED: \secure\infiniiVision\web\image\zoom.png
   DELETED: \secure\infiniiVision\web\image\
**** CleanupInfiniiVisionFolder ****
   DELETED: \secure\infiniiVision\web\lib\edtftpj.jar
   DELETED: \secure\infiniiVision\web\lib\plugin.jar
   DELETED: \secure\infiniiVision\web\lib\
**** CleanupInfiniiVisionFolder ****
   DELETED: \secure\infiniiVision\web\navbar\PantherTabs.psd
   DELETED: \secure\infiniiVision\web\navbar\bluebar.gif
   DELETED: \secure\infiniiVision\web\navbar\config-down.gif
   DELETED: \secure\infiniiVision\web\navbar\config-over.gif
   DELETED: \secure\infiniiVision\web\navbar\config.gif
   DELETED: \secure\infiniiVision\web\navbar\help-down.gif
   DELETED: \secure\infiniiVision\web\navbar\help-over.gif
   DELETED: \secure\infiniiVision\web\navbar\help.gif
   DELETED: \secure\infiniiVision\web\navbar\image-down.gif
   DELETED: \secure\infiniiVision\web\navbar\image-over.gif
   DELETED: \secure\infiniiVision\web\navbar\image.gif
   DELETED: \secure\infiniiVision\web\navbar\printpage-down.gif
   DELETED: \secure\infiniiVision\web\navbar\printpage-over.gif
   DELETED: \secure\infiniiVision\web\navbar\printpage.gif
   DELETED: \secure\infiniiVision\web\navbar\remote-down.gif
   DELETED: \secure\infiniiVision\web\navbar\remote-only.gif
   DELETED: \secure\infiniiVision\web\navbar\remote-over.gif
   DELETED: \secure\infiniiVision\web\navbar\saverecall-down.gif
   DELETED: \secure\infiniiVision\web\navbar\saverecall-over.gif
   DELETED: \secure\infiniiVision\web\navbar\saverecall.gif
   DELETED: \secure\infiniiVision\web\navbar\status-down.gif
   DELETED: \secure\infiniiVision\web\navbar\status-over.gif
   DELETED: \secure\infiniiVision\web\navbar\status.gif
   DELETED: \secure\infiniiVision\web\navbar\utilities-down.gif
   DELETED: \secure\infiniiVision\web\navbar\utilities-over.gif
   DELETED: \secure\infiniiVision\web\navbar\utilities.gif
   DELETED: \secure\infiniiVision\web\navbar\welcome-down.gif
   DELETED: \secure\infiniiVision\web\navbar\welcome-over.gif
   DELETED: \secure\infiniiVision\web\navbar\welcome.gif
   DELETED: \secure\infiniiVision\web\navbar\
   DELETED: \secure\infiniiVision\web\ClickFix.js
   DELETED: \secure\infiniiVision\web\CookieUtils.js
   DELETED: \secure\infiniiVision\web\InfiniiVision_Quick_Reference.html
   DELETED: \secure\infiniiVision\web\appletInstall.jar
   DELETED: \secure\infiniiVision\web\appletScpi.jar
   DELETED: \secure\infiniiVision\web\appletsVersion.asp
   DELETED: \secure\infiniiVision\web\constant.asp
   DELETED: \secure\infiniiVision\web\doModifyConfig.asp
   DELETED: \secure\infiniiVision\web\doSave.asp
   DELETED: \secure\infiniiVision\web\download.asp
   DELETED: \secure\infiniiVision\web\enumConst.asp
   DELETED: \secure\infiniiVision\web\frontpanel.min.js
   DELETED: \secure\infiniiVision\web\getImage.asp
   DELETED: \secure\infiniiVision\web\home.html
   DELETED: \secure\infiniiVision\web\homeBottom.asp
   DELETED: \secure\infiniiVision\web\homeMiddle.asp
   DELETED: \secure\infiniiVision\web\homeTop.asp
   DELETED: \secure\infiniiVision\web\ieCompat.html
   DELETED: \secure\infiniiVision\web\index.asp
   DELETED: \secure\infiniiVision\web\infoCal.asp
   DELETED: \secure\infiniiVision\web\infoLicense.asp
   DELETED: \secure\infiniiVision\web\infoNav.asp
   DELETED: \secure\infiniiVision\web\infoVersion.asp
   DELETED: \secure\infiniiVision\web\information.html
   DELETED: \secure\infiniiVision\web\lanInfo.asp
   DELETED: \secure\infiniiVision\web\modifyConfig.asp
   DELETED: \secure\infiniiVision\web\navigation.asp
   DELETED: \secure\infiniiVision\web\networkStatus.asp
   DELETED: \secure\infiniiVision\web\pwdEnum.asp
   DELETED: \secure\infiniiVision\web\pwdPrompt.asp
   DELETED: \secure\infiniiVision\web\pwdVerify.asp
   DELETED: \secure\infiniiVision\web\recall.asp
   DELETED: \secure\infiniiVision\web\remoteApplet.asp
   DELETED: \secure\infiniiVision\web\remoteSCPICommands.asp
   DELETED: \secure\infiniiVision\web\rfp.html
   DELETED: \secure\infiniiVision\web\rfp.mf
   DELETED: \secure\infiniiVision\web\save.asp
   DELETED: \secure\infiniiVision\web\saveFrame.asp
   DELETED: \secure\infiniiVision\web\saveRecall.asp
   DELETED: \secure\infiniiVision\web\scopeInfo.asp
   DELETED: \secure\infiniiVision\web\style.css
   DELETED: \secure\infiniiVision\web\toolbarHelp.asp
   DELETED: \secure\infiniiVision\web\top.asp
   DELETED: \secure\infiniiVision\web\utils.js
   DELETED: \secure\infiniiVision\web\viewConfig.asp
   DELETED: \secure\infiniiVision\web\
**** CleanupInfiniiVisionFolder ****
   DELETED: \secure\infiniiVision\fpga\FPGA2000A.bin
   DELETED: \secure\infiniiVision\fpga\FPGA3000A.bin
   DELETED: \secure\infiniiVision\fpga\N2750A.bin
   DELETED: \secure\infiniiVision\fpga\N2820A.bin
   DELETED: \secure\infiniiVision\fpga\gpibFPGA.bin
   DELETED: \secure\infiniiVision\fpga\lanFPGA.bin
   DELETED: \secure\infiniiVision\fpga\
   DELETED: \secure\infiniiVision\SetupConverter.exe
   DELETED: \secure\infiniiVision\splashImage.bin
   DELETED: \secure\infiniiVision\dnssd_CE.dll
   DELETED: \secure\infiniiVision\libcups2.dll
   DELETED: \secure\infiniiVision\libcups2backend.dll
   DELETED: \secure\infiniiVision\networkPrintFile.exe
   DELETED: \secure\infiniiVision\websockify.exe
   DELETED: \secure\infiniiVision\infiniiVisionLauncher.exe
   DELETED: \secure\infiniiVision\infiniiVisionWebCom.dll
   DELETED: \secure\infiniiVision\
**** CleanupInfiniiVisionFolder ****
   DELETED: \secure\Startup\infiniivision.lnk
   DELETED: \secure\Startup\
**** CleanupInfiniiVisionFolder ****
   DELETED: \secure\help\lpkChineseS.lpk
   DELETED: \secure\help\lpkChineseT.lpk
   DELETED: \secure\help\lpkCzech.lpk
   DELETED: \secure\help\lpkFrench.lpk
   DELETED: \secure\help\lpkGerman.lpk
   DELETED: \secure\help\lpkItalian.lpk
   DELETED: \secure\help\lpkJapanese.lpk
   DELETED: \secure\help\lpkKorean.lpk
   DELETED: \secure\help\lpkPolish.lpk
   DELETED: \secure\help\lpkPortuguese.lpk
   DELETED: \secure\help\lpkRussian.lpk
   DELETED: \secure\help\lpkSpanish.lpk
   DELETED: \secure\help\lpkThai.lpk
   DELETED: \secure\help\lpkTurkish.lpk
   DELETED: \secure\help\
**** CleanupInfiniiVisionFolder ****
   DELETED: \secure\bin\
** END   ** ProcessRecipeStep: \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\cleanupFileSystem.exe: 2899 ms
** BEGIN ** ExtractFileFromCabFile: infiniivisionSetup.cab
** END   ** ExtractFileFromCabFile: infiniivisionSetup.cab: 9776 ms
** BEGIN ** ProcessRecipeStep: \windows\wceldcmd.exe /delete 0 \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\infiniivisionSetup.cab
** END   ** ProcessRecipeStep: \windows\wceldcmd.exe /delete 0 \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\infiniivisionSetup.cab: 7903 ms
** BEGIN ** ExtractFileFromCabFile: splashImage.png
** END   ** ExtractFileFromCabFile: splashImage.png: 436 ms
** BEGIN ** ProcessRecipeStep: \windows\compileImageForSplashScreen.exe \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\SplashImage.png \Secure\InfiniiVision

\splashImage.bin
** END   ** ProcessRecipeStep: \windows\compileImageForSplashScreen.exe \TEMP\{6A9868B0-CBCE-9EDE-AF1B-E43FEE72A8BA}\SplashImage.png \Secure\InfiniiVision

\splashImage.bin: 3003 ms
WMT: "", ""
** BEGIN ** ProcessRecipeStep: \windows\rebootInfiniivision.exe





===================================== scope restarts itself with new firmware=======================================================
======================================================================================================================================






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: 2021-2-6   16:49:58.2 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: 2021-2-6   16:49:58.5 UTC
 Loading image 1 from memory at 0xD0600000
O
BL_IMAGE_TYPE_BIN

X
XXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOOXOOOOXXXOOOOOOOOOXOOOOXOXXOXOXXOXOXOXOXXXXOOXXXOOOOOOXXOXXOXXXXXXOOOXXXOOXXOOXXXOOOXOOXOOXXOOXOXOOOOXOXOOOOOXOOOXOOOXXXOXOXXXXXXOXXXX

OOOXOOOXOXOOOOXOOOOXOXOXOOOOOOX
OOOXOOXOOOOXXXOOOOXOOXXOOXOOOOOOOOOXOXOOOXOOOOOOXOXOOOOXOXOOOOOOOXOXOXXOOXOXOOOXOOOXOOXXOXOXOOOXOXXXXXOXOXXXOXXXOXOXXOOOXXXOXXXXXXOXXXXXXXOXXXXOXOXOXOOOXXXXOXXXXXOOOX

XOXX
OOXXOXXXOOXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXXXXOXOO

XOXOOOXOXXXXXXXXXXXXXrom_offset=0x0.
XXImageStart = 0x80361000, ImageLength = 0x1ACF7FC, LaunchAddr = 0x80362000

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x1ACF7FC  Name="" Target=RAM
 Loading image 1 succeeded.
ROMHDR at Address 80361044h
Preparing launch...
RTC: 2021-2-6   16:50:1.40 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 Oct 11 2020)
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:DA:4C
Phy found addr 31 (ticks=3337)
WaitForLink Start (ticks=3339)
No Link (ticks=4341)
<--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: 0 ms
   SNANDFLASH: 0 ms
Summary of scan:

All FATs on volume agree

Percent Fragmentation: 0
Invalid Directories: 0
Invalid Files: 0
Invalid Clusters: 0
Lost Cluster Chains: 0

ScanVolume \Agilent Flash (NANDFLASH) 0.288000
Summary of scan:

All FATs on volume agree

Percent Fragmentation: 0
Invalid Directories: 0
Invalid Files: 0
Invalid Clusters: 0
Lost Cluster Chains: 0

ScanVolume \Secure (SNANDFLASH) 0.344000
SHIM DLL, LoadRealDll [PalIO.dll] for [AgilentPalIO.dll]
SHIM [AgilentPalIO.dll] Get Process Addresses
Our command line is
Performing Startup
SHIM DLL, LoadRealDll [PalSStorage.dll] for [AgilentPalSStorage.dll]
SHIM [AgilentPalSStorage.dll] Get Process Addresses

      creating \Secure\bin\Released build, Oct 11 2020, 11:14:27
Initializing FPGA...
****
FPGA Type: Wyoming
Ver: 2.011 Released
Build Time: Tue May 27 16:03:14 2014
Build Machine: TS2404M
****
No option module detected
Keyboard firmware version 32... ok
Keyboard Info: Board id 1, Board rev 3
Startup sequence is complete.
SHIM DLL, LoadRealDll [PalSysManagement.dll] for [AgilentPalSysManagement.dll]
SHIM [AgilentPalSysManagement.dll] Get Process Addresses
SHIM DLL, LoadRealDll [PalCaps.dll] for [AgilentPalCaps.dll]
SHIM [AgilentPalCaps.dll] Get Process Addresses
System has been running 23.350714 seconds
Start Up Sequence 12.064940
Memory Load 54%
   System Physical Memory 38.949 / 73.230 MB
   Process Virtual Memory 48.750 / 1024.000 MB
-----> InfiniiVision is running <-----
failed open \Secure\InfiniiVision\LudicrousSpeed.usb
                                                    no workaround for USB phy



===================  another normal restart in V2.60================================================================
===================================================================================================================






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: 2021-2-6   16:52:3.48 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: 2021-2-6   16:52:3.51 UTC
 Loading image 1 from memory at 0xD0600000
O
BL_IMAGE_TYPE_BIN

X
XXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOOXOOOOXXXOOOOOOOOOXOOOOXOXXOXOXXOXOXOXOXXXXOOXXXOOOOOOXXOXXOXXXXXXOOOXXXOOXXOOXXXOOOXOOXOOXXOOXOXOOOOXOXOOOOOXOOOXOOOXXXOXOXXXXXXOXXXX

OOOXOOOXOXOOOOXOOOOXOXOXOOOOOOX
OOOXOOXOOOOXXXOOOOXOOXXOOXOOOOOOOOOXOXOOOXOOOOOOXOXOOOOXOXOOOOOOOXOXOXXOOXOXOOOXOOOXOOXXOXOXOOOXOXXXXXOXOXXXOXXXOXOXXOOOXXXOXXXXXXOXXXXXXXOXXXXOXOXOXOOOXXXXOXXXXXOOOX

XOXX
OOXXOXXXOOXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXXXXOXOO

XOXOOOXOXXXXXXXXXXXXXrom_offset=0x0.
XXImageStart = 0x80361000, ImageLength = 0x1ACF7FC, LaunchAddr = 0x80362000

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x1ACF7FC  Name="" Target=RAM
 Loading image 1 succeeded.
ROMHDR at Address 80361044h
Preparing launch...
RTC: 2021-2-6   16:52:6.86 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 Oct 11 2020)
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:DA:4C
Phy found addr 31 (ticks=3332)
WaitForLink Start (ticks=3334)
No Link (ticks=4336)
<--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: 0 ms
   SNANDFLASH: 0 ms
SHIM DLL, LoadRealDll [PalIO.dll] for [AgilentPalIO.dll]
SHIM [AgilentPalIO.dll] Get Process Addresses
Our command line is
Performing Startup
SHIM DLL, LoadRealDll [PalSStorage.dll] for [AgilentPalSStorage.dll]
SHIM [AgilentPalSStorage.dll] Get Process Addresses
Released build, Oct 11 2020, 11:14:27
Initializing FPGA...
****
FPGA Type: Wyoming
Ver: 2.011 Released
Build Time: Tue May 27 16:03:14 2014
Build Machine: TS2404M
****
No option module detected
Keyboard firmware version 32... ok
Keyboard Info: Board id 1, Board rev 3
Startup sequence is complete.
SHIM DLL, LoadRealDll [PalSysManagement.dll] for [AgilentPalSysManagement.dll]
SHIM [AgilentPalSysManagement.dll] Get Process Addresses
SHIM DLL, LoadRealDll [PalCaps.dll] for [AgilentPalCaps.dll]
SHIM [AgilentPalCaps.dll] Get Process Addresses
System has been running 20.651762 seconds
Start Up Sequence 10.129452
Memory Load 53%
   System Physical Memory 38.742 / 73.230 MB
   Process Virtual Memory 48.500 / 1024.000 MB
-----> InfiniiVision is running <-----
failed open \Secure\InfiniiVision\LudicrousSpeed.usb
                                                    no workaround for USB phy

analogRF · « **Reply #34 on:** February 06, 2021, 09:46:48 pm »

I think this recovery method using the serial console and YMODEM is pretty good and I never had problem uploading the kernel but it takes time (30-40 minutes depending on the version/size)
I am now pretty sure that even 2.35 would have worked from the beginning and the problem was that \usb\Startup\infiniivision.lnk should have been modified to force the scope to execute the infiniivisionLauncher.exe from the USB and not from the scope's NAND flash because it was corrupted

analogRF · « **Reply #35 on:** February 06, 2021, 09:49:04 pm »

two of the softkeys under the screen (# 3 and # 6) do not work at all.
Any idea, why? Everything else works perfectly but those two buttons do not register no matter how hard I push...

Bud · « **Reply #36 on:** February 06, 2021, 09:49:19 pm »

I do not think buttons have anything to do with firmware, try resitting the keypad cable maybe, if this scope has one.

tv84 · « **Reply #37 on:** February 06, 2021, 09:58:44 pm »

Quote from: analogRF on February 06, 2021, 09:36:25 pm

Scope is fixed and up and running

That surely was not a lame attempt!

Quote from: analogRF on February 06, 2021, 09:36:25 pm

can someone point me to a method to enable the options with 2.60 FW please?[/b]

Go to the usual place.

analogRF · « **Reply #38 on:** February 06, 2021, 11:35:47 pm »

All done

many thanks to tv84 and specially 10^6 thanks to PhillyFlyers who made it so easy and hassle free

I used this line in my infiniivision.lnk on the root of USB along with the patched 2.60 firmware and simply
asked the scope to upgrade and that's it. Nothing more you need to do except sit back until it restarts and all the scope's power is released

Code: [Select]

65#infiniiVisionLauncher.exe -l D3000BDLA -l MEMUP -l MSO -l WAVEGEN

the scope's About page does not show individual license like EMBD, PWR, ADVMATH, etc....it shows D3000BDLA plus the WAVEGEN and MEMUP and MSO and the standard features EDK, SGM, RML

TheSteve · « **Reply #39 on:** February 07, 2021, 06:37:01 am »

Did you get all of the front panel buttons working?
There is a small ribbon cable for the front - check that.

analogRF · « **Reply #40 on:** February 07, 2021, 11:36:14 am »

Quote from: TheSteve on February 07, 2021, 06:37:01 am

Did you get all of the front panel buttons working?
There is a small ribbon cable for the front - check that.

yes the problem is that small flex cable

I cannot figure out what exactly the problem is with it but as soon as I bend it in a certain shape
(pull it up near the connector) all buttons work. So I ordered a cable from Digikey (732-3555-ND) which I hope it will fit. It's 3mm longer but it shouldn't be a problem. I have to wait until Tuesday I think...

analogRF · « **Reply #41 on:** February 07, 2021, 04:03:18 pm »

Now that the scope is MSO, can I get the front label (badge) changed to MSO-X? is it possible to replace that label?
has anybody done that before here?

I guess since they officially sell MSO option to DSO owners, they should probably include a new badge in the kit, no?

analogRF · « **Reply #42 on:** February 07, 2021, 04:26:25 pm »

Quote from: blueskull on February 07, 2021, 04:08:26 pm

Quote from: analogRF on February 07, 2021, 04:03:18 pm
I guess since they officially sell MSO option to DSO owners, they should probably include a new badge in the kit, no?

They should have. The front panel overlay is user replaceable.

My scope came in the box with a spare Chinese overlay and a preinstalled English overlay.

that does not include the ID label on the top of screen. front panel overlay is a different thing

analogRF · « **Reply #43 on:** February 09, 2021, 09:43:16 pm »

Quote from: analogRF on February 07, 2021, 11:36:14 am

Quote from: TheSteve on February 07, 2021, 06:37:01 am
Did you get all of the front panel buttons working?
There is a small ribbon cable for the front - check that.

yes the problem is that small flex cable
I cannot figure out what exactly the problem is with it but as soon as I bend it in a certain shape
(pull it up near the connector) all buttons work. So I ordered a cable from Digikey (732-3555-ND) which I hope it will fit. It's 3mm longer but it shouldn't be a problem. I have to wait until Tuesday I think...

Just to be complete here, I replaced the small flex cable with the part I got from Digikey and the softkeys are all working now

The scope just passed user Cal

Last user Cal was June 2013, the same time the scope was manufactured

:o and yet there was like <1mV offset on channels which is now gone.

TheSteve · « **Reply #44 on:** February 09, 2021, 11:38:00 pm »

Please post the part # of the cable you used, maybe it will help someone else out down the road.

analogRF · « **Reply #45 on:** February 10, 2021, 12:10:28 am »

Quote from: TheSteve on February 09, 2021, 11:38:00 pm

Please post the part # of the cable you used, maybe it will help someone else out down the road.

Digikey P/N was already given in my previous post
but here it is again: 732-3555-ND

analogRF · « **Reply #46 on:** February 15, 2021, 05:11:06 pm »

I have a question about the upgrades on Agilent 3000A:
now that I am on FW 2.6 and upgraded, what happens if a next firmware is released and I want to update the firmware?
Do the options disappear and need a patched firmware or I can install future firmwares with no issue?

tv84 · « **Reply #47 on:** February 15, 2021, 08:17:03 pm »

Disappear.

eugen_m2 · « **Reply #48 on:** July 18, 2022, 02:23:03 pm »

Dear all,

i am trying since some time to get my DSO-X 3024A back
i followed Titiris's explanations but unfortunately i could not boot it
i think i do something wrong in the file structure of the USB, but until now i cannot tell what
i get the following :

Starting ProcessStartupFolder
running \Secure\Startup\infiniivision.lnk...
System.MissingMethodException: Can't find an Entry Point 'RegisterNativeCompactL icensingCallbacks' in a PInvoke DLL 'Agilent.Cdf.Api.Unmanaged.dll'.
at Agilent.Cdf.Api.Licensing.Compact.LicenseSupervisor.g.a.c()
at Agilent.Cdf.Api.NativeInterop.RegisterNativeCallbacks()
at Agilent.InfiniiVision.infiniiVisionLauncher.Main(String[] args)

Ending ProcessStartupFolder

O::SPI_GETBOOTMENAME
Failed to start/configure network.
Time for NANDFLASH to load: 0 ms.
Time for SNANDFLASH to load: 0 ms.
Starting ProcessStartupFolder
running \Secure\Startup\infiniivision.lnk...
System.MissingMethodException: Can't find an Entry Point 'RegisterNativeCompactL icensingCallbacks' in a PInvoke DLL 'Agilent.Cdf.Api.Unmanaged.dll'.
at Agilent.Cdf.Api.Licensing.Compact.LicenseSupervisor.g.a.c()
at Agilent.Cdf.Api.NativeInterop.RegisterNativeCallbacks()
at Agilent.InfiniiVision.infiniiVisionLauncher.Main(String[] args)

Ending ProcessStartupFolder

dimmog · « **Reply #49 on:** March 29, 2024, 01:45:14 am »

Quote from: eugen_m2 on July 18, 2022, 02:23:03 pm

Dear all,

i am trying since some time to get my DSO-X 3024A back
i followed Titiris's explanations but unfortunately i could not boot it
i think i do something wrong in the file structure of the USB, but until now i cannot tell what
i get the following :

Starting ProcessStartupFolder
running \Secure\Startup\infiniivision.lnk...
System.MissingMethodException: Can't find an Entry Point 'RegisterNativeCompactL icensingCallbacks' in a PInvoke DLL 'Agilent.Cdf.Api.Unmanaged.dll'.
at Agilent.Cdf.Api.Licensing.Compact.LicenseSupervisor.g.a.c()
at Agilent.Cdf.Api.NativeInterop.RegisterNativeCallbacks()
at Agilent.InfiniiVision.infiniiVisionLauncher.Main(String[] args)

Ending ProcessStartupFolder

I have the same errors. Did you manage to fix this issue?

dimmog · « **Reply #50 on:** March 29, 2024, 04:32:18 am »

Quote from: dimmog on March 29, 2024, 01:45:14 am

I have the same errors. Did you manage to fix this issue?

Fixed. The scope was originally with ver 2.10 and I tried to resurrect it with ver 2.35 which in this case was incompatible.
Then I prepared a flash drive with the 2.20 version and it worked immediately. One more DSOX3034A saved


EEVblog Main Site	EEVblog on Youtube	EEVblog on Twitter	EEVblog on Facebook	EEVblog on Odysee

Author Topic: Agilent DSOX3054A not booting possible NAND corruption HELP! (RESOLVED) (Read 8675 times)

Share me