DSOX2000 and 3000 series - licence , have anyone tried to hack that scope ?

[Blue]

I have a DSOX3014A.

I cannot get -l CABLE to be sticky.
If I telnet into the scope:

Pocket CMD v 6.00
\> ProcessMgr.exe kill infiniivisionLauncher.exe
\> \secure\infiniivision\infiniiVisionLauncher.exe -l ALL -l BW20 -l SCPIPS -l CABLE --perf
Our command line is -l ALL -l BW20 -l SCPIPS -l CABLE --perf
*** Installing License: All Licenses
*** Installing License: 200MHz Bandwidth
*** Installing License: Cable Calibration
*** Installing License: Infiniium Mode
System has been running 91.553528 seconds

I get the cable menu in the analyze submenu. But if I put
65#infiniivisionLauncher.exe -l ALL -l BW20 -l SCPIPS -CABLE --perf
 into a file called \usb\infiniivision.lnk and copy it to \Secure\Startup then it does not register.

Does anyone know why?
Does --perf do anything in this scope?

[PlainName]

Our command line is -l ALL -l BW20 -l SCPIPS -l CABLE --perf

65#infiniivisionLauncher.exe -l ALL -l BW20 -l SCPIPS -CABLE --perf

Your programmed command line isn't the same as your manually entered one

[Blue]

Hi Dunkemhigh,

You are absolutely right. I made a stupid mistake. Thanks.

My scope:

[dougberc]

Well, after sitting on my hands a bit I took the plunge and.... IT WORKS!!

Absolutely amazing and I really cannot thank everyone in this forum enough! Just WOW!!

I followed my previous post as far as flashing the firmware goes but I didn't add the infiniivision.lnk. I went ahead and rebooted the scope and it came up like normal with the default options that it shipped with. So I telnet'd in, and killed the process and started experimenting with launcher commands. For my scope - a Keysight DSOX4034A - I ended up settling on this for the infiniivision.lnk:

73#infiniivisionLauncher.exe -l DIS -l MSO -l BW50 -l SCPIPS -l CABLE -l VID

The "-l DIS" and "-l PLUS" seem to replicate each other to a large extent, and "-l DIS" seemed to include more by itself. Also the "--perf" that some people have added causes my scope to barf. Along those same lines, if you add any parameter to that string of options that causes an error it will stop parsing the line right there. For example, if I were to use: "73#infiniivisionLauncher.exe -l MSO --perf -l BW50 -l SCPIPS -l CABLE -l VID" then the parser would error out on the "--perf" part and the only option installed would be the MSO one. This was probably mentioned in the 80+ pages somewhere but I'll repeat it here just in case.

So again,

THANK YOU!! THANK YOU!! THANK YOU!!

[Blue]

I've been playing with the lnk file.
Now it contains: 68#infiniivisionLauncher.exe -l ALL -l BW20 -l SCPIPS -l CABLE -l TOM

and the result is:

Suddenly I get Tomotherapy and SGMC as additions.
Does anyone know what these are?

[Blue]

Does anyone knows where to get the 64997A Oscilloscope Spectrum Visualizer (OSV) Software software?

https://www.keysight.com/en/pd-2118936-pn-64997A/agilent-spectrum-visualizer-asv-software?nid=-32448.1011140&cc=NL&lc=dut



Or is there a newer version?
This software is used with the ASV option.

[Sparky]

Does anyone knows where to get the 64997A Oscilloscope Spectrum Visualizer (OSV) Software software?

Or is there a newer version?
This software is used with the ASV option.

It's obsolete now, but you can try this.

[Blue]

Download does not work.
Any other options?

[Sparky]

Download does not work.
Any other options?

It downloads just fine for me; "Keysight_OSV_1_9_20.zip" 129MB

[Blue]

Thanks for the update.
I had to register before I could download it. Duh...

[Sparky]

Thanks for the update.
I had to register before I could download it. Duh...

Glad you figured it out!  You also need the Keysight IO Libraries Suite, and make sure your scope is detected and listed in the Connection Expert utility, and then start the OSV program.  Its a bit clunky operationally...

[Blue]

Very clunky is an understatement.
Pretty useless.

[rizal5478]

The Steve, I've my MSO-X 3012A hang and no display during start up. After read the thread I've done extracting through serial on the board and result as below. By the way I've no idea what is the version before the scope spoilts.

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
failed: 597 0
Could not copy from NAND offset 0x60000. Error -74 With ECC
failed: 1192 597
Could not copy from NAND offset 0x60000. Error -74 NO ECC
FPGA programming FAILED!
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
ODeCompressFlash: CeCompressDecode() failed
 EBOOT_ReadFlash failed

ERROR: Unable to read image signature.

BL_IMAGE_TYPE_UNKNOWN

 Loading image 1 failed, trying next one
 Loading image 2 from memory at 0xD1600000
ODeCompressFlash: CeCompressDecode() failed
 EBOOT_ReadFlash failed

ERROR: Unable to read image signature.

BL_IMAGE_TYPE_UNKNOWN

 Loading image 2 failed, trying next one
 All images failed

Press r to reset

[TheSteve]

Yep, that is the NAND corruption issue. You can try recovering it yourself using a network or serial connection. Or contact Keysight as they should repair it for free for you.

[rizal5478]

The Steve, I've my MSO-X 3012A hang and no display during start up. After read the thread I've done extracting through serial on the board and result as below. By the way I've no idea what is the version before the scope spoilts.

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
failed: 597 0
Could not copy from NAND offset 0x60000. Error -74 With ECC
failed: 1192 597
Could not copy from NAND offset 0x60000. Error -74 NO ECC
FPGA programming FAILED!
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
ODeCompressFlash: CeCompressDecode() failed
 EBOOT_ReadFlash failed

ERROR: Unable to read image signature.

BL_IMAGE_TYPE_UNKNOWN

 Loading image 1 failed, trying next one
 Loading image 2 from memory at 0xD1600000
ODeCompressFlash: CeCompressDecode() failed
 EBOOT_ReadFlash failed

ERROR: Unable to read image signature.

BL_IMAGE_TYPE_UNKNOWN

 Loading image 2 failed, trying next one
 All images failed

Press r to reset

I've done base from the thread using version 2.35 with USB and it show error as below:-

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
failed: 597 0
Could not copy from NAND offset 0x60000. Error -74 With ECC
failed: 1192 597
Could not copy from NAND offset 0x60000. Error -74 NO ECC
FPGA programming FAILED!
Press space to stop autoboot:  0
p500> loady 0x0361000 115200
## Ready for binary (ymodem) download to 0x00361000 at 115200 bps...
CCxyzModem - CRC mode, 6(SOH)/19482(STX)/0(CAN) packets, 8 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:79:89
Phy found addr 31 (ticks=2590)
WaitForLink Start (ticks=2591)
No Link (ticks=3594)
<--EDeviceInitialize

GMAC DMA status register = 0x0
BALDWIN_DDI: cBaldwinHwIf::Init: Initializing...
BALDWIN_DDI: cBaldwinHwIf::Init: Scope successfully identified.

[Jens01]

Not really on-topic, but not worth creating a new topic:

@Daniel, will the FRA plugin become available for the non-T DSOX3k series? In my case that would be a instant-buy. It is a bit strange that the FRA is (default) supported by the cheaper DSOX1200 series, but not on the more expensive serie.

[titiris]

Hi Rizal5478,
just in case, I have the full session saved from my successful recovery. Here is the segment from the loady to the happy end

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:1A:5B
Phy found addr 31 (ticks=2638)
WaitForLink Start (ticks=2640)
No Link (ticks=3643)
<--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.
Starting ProcessStartupFolder
ProcessStartupFolder: \usb\Startup\
                                   running \usb\Startup\infiniivision.lnk...
Ending ProcessStartupFolder
                           Our command line is
Performing Startup
Released build, Jun 18 2013, 12:31:00
Initializing FPGA...
****
FPGA Type: Idaho
Ver: 1.094 Released
Build Time: Wed Oct 24 15:40:11 2012
Build Machine: DW3647M2
****
No option module detected
Keyboard firmware version 32... ok
Keyboard Info: Board id 7, Board rev 2
Startup sequence is complete.
System has been running 70.717255 seconds
Start Up Sequence 56.031798
Memory Load 54%
   System Physical Memory 42.551 / 79.086 MB
   Process Virtual Memory 45.688 / 1024.000 MB
-----> InfiniiVision is running <-----

I also get the same errors as you, but the scope end running flawlessly.
Hope it helps 

[wrieken]

Hi,

Were you able to fix your problems and also, if you don't mind, could you please let me know what would be a good set of probes without paying the Keysight US 600USD tax for them?

Thanks,

William

[Dwaine]

A little bit off topic...

  I went from the Rigol 4 channel scope to the DSOX2004.  After patching and upgrading it, I can see what people have been saying about the differences between the Rigol and Keysight scopes.   It's really night and day.

[rizal5478]

Thanks Titiris, At least I knew how far that I'm right now.. Do you know this method only can use for certain version of software? As I didn't aware before my existing version.. I just use this 2.35 version for my trial.. Would this able to solve if existig has version higher than 2.35?

[mlloyd1]

 
welcome to the light
 

sorry, i just couldn't help it ...

mlloyd1

[rizal5478]

I just got DSOXLAN module. Anyone did through telnet with unit hang and no display issue?

[Xavier64]

For all Keysight 3000A uses who have the startupmessage:

Firmware OS error detected



this infiniivision.lnk is the solution:


119#\Windows\cmd.exe /c infiniivisionlauncher.exe -l ALL -l BW50 -l SCPIPS -l SGMC -l CABLE -l PERF -l TOM -l CABLE --perf




I assume you followed this steps



0) Install correct Firmware version first (i.e. in this case 2.43)
1) Download Safar's patched_nk_bin.comp file and copy to a USB stick and plug in.
2) Telnet into the scope.
3) Login infiniivision / skywalker1977
4) processmgr kill infiniivisionlauncher.exe
5) \windows\loadP500Flash -u ceImage1 \usb\patched_nk.bin.comp
6) Create a file on the USB stick called infiniivision.lnk with contents (e.g.) "88#infiniivisionLauncher.exe -l MSO -l BW20 -l DIS -l PLUS -l SCPIPS -l VID -l CABLE --perf"
7a) delete (or rename) any other lnk in \secure\startup folder. Should be only one file with lnk extension here.
7b) copy \usb\infiniivision.lnk to \secure\startup
8 ) reboot and good to go



I did it with Firmware 2.43


LAN module is working fine and NO red warning appears.

Thanks to all who made this possible.

[Dwaine]

I just got DSOXLAN module. Anyone did through telnet with unit hang and no display issue?

Hanging happens, just try to connect again.  It will work the second time.

[TheSteve]

Firmware version 2.50 was released today for the 2000A/3000A series.

Major release details:

Bug Fixes for both 2000A and 3000A
- Fixed an issue of an unrelated error message showing when adjusting the UART/CAN/LIN
baud-rate.
- Fixed an issue of the Reference Waveform file (.h5) incorrectly saving data with twice the
timebase delay when there is a non-zero delay on the displayed waveform.
- Fixed an issue of the inverted channel mode not displaying the waveform correctly in
Averaging Mode.

Changes for both 2000A and 3000A
- Due to a lack of browser support for Java-based applications, support for the legacy Javabased remote front panel has been removed. A modern HTML5-based remote front panel is available.
- As of version 2.50, the VNC server software for the remote front panel functionality is no
longer bundled with the scope software by default. Upgrading to 2.50 will not delete the
VNC server software from the scope, but new scopes will no longer ship with the VNC
server software installed. For scopes without the software installed, the Browser Web
Control page will provide a link for installing the software.