Author Topic: DSOX2000 and 3000 series - licence , have anyone tried to hack that scope ?  (Read 1311200 times)

0 Members and 1 Guest are viewing this topic.

Offline onesystem

  • Regular Contributor
  • *
  • Posts: 61
  • Country: us
Thanks! I tried the pre-made .exe version and it was giving usblib error, so I built one from source on my pc, usblb error stopped, but this one is coming up:
Code: [Select]
C:\spearload>spearload -t spear600 p500_ddrdriver.bin u-boot_image.bin
spearload: opening device...
spearload: st_find: could not find suitable USB device for VID = 0483, PID = 7261
spearload: device not found, is it powered on and in recovery?

I checked my computer settings and it does list the usb device with VID = 0483, PID = 7261. Is there something else I need to do? - I tried every USB port, and made sure nothing else is plugged in.
 

Offline onesystem

  • Regular Contributor
  • *
  • Posts: 61
  • Country: us
Ok. So with help of ShQ I was able to get the spearloader.exe to work, but I am unable to get into u-boot prompt no matter how much I keep that space bar pressed.

Really, what I am trying to handle - is the error at the end of this log:
Code: [Select]
U-Boot 2010.03 (May 18 2017 - 11:28:22)Agilent P500                             
                                                                               
CPU:   SPEAr600                                                                 
DRAM:  128 MiB                                                                 
Flash: 512 KiB                                                                 
NAND:  internal ecc 128 MiB                                                     
                                                                               
Debug serial initialized ........OK                                             
RTC: 2022-2-8   1:40:39.69 UTC                                                 
                                                                               
Microsoft Windows CE Bootloader Common Library Version 1.4 Built Oct 29 2015 01:
39:04                                                                           
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: 2022-2-8   1:40:39.73 UTC                                                 
 Loading image 1 from memory at 0xD0600000                                     
O                                                                               
BL_IMAGE_TYPE_BIN                                                               
                                                                               
X                                                                               
XXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOOXOOOOXXXOOOOOOOOOXOOOOXOXXOXOXXOXOXOXOXXXXOOXXX
OOOOOOXXOXXOXXXXXXOOOXXXOXXOOOXXXOOOXOOXOOXXOOXOXOOOOXOXOOOOOXOOOXOOXOXOXOXXXXXO
XXXXOOOXOOOXOXOOOOXOOOOXOXOXOOOOOOXOOOXOOX                                     
OOOOXXXOOOOXOOXOOXOOOOOOOOOXOXOOOXOOOOOOXOXOOOOOXXOOOOOOOXOXOXXOOXOXOOOXOOOXOOXO
XXXOXOOOXOXXXXOXOXXOXXXXXOXOXXOOOXXXOXXXXXXOXXXXXXOXXXXOXOXOXOOOXXXXOXXXXXOOOXXO
XXOOXXOX                                                                       
XXOOXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO               
OOOOOOOOOOOOOOOOOOOOOOOOOOOXXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXXXOXOOOXOXOOXOOXXXXXXXXXXXXOXrom_offset=0x0.
XXImageStart = 0x80361000, ImageLength = 0x1ACA724, LaunchAddr = 0x80362000

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x1ACA724  Name="" Target=RAM
 Loading image 1 succeeded.
ROMHDR at Address 80361044h
Preparing launch...
RTC: 2022-2-8   1:40:43.19 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 Feb 27 2019)
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:21:F2:AD
Phy found addr 31 (ticks=3387)
WaitForLink Start (ticks=3389)
No Link (ticks=4391)
<--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, Feb 27 2019, 20:34:05
Initializing FPGA...
****
FPGA Type: Idaho
Ver: 2.027 Released
Build Time: Tue Oct 13 16:48:05 2015
Build Machine: TS2404M
****
No option module detected
Keyboard firmware version 32... ok
Keyboard Info: Board id 7, Board rev 2
Startup sequence is complete.
Saved configuration invalid
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 24.192625 seconds
Start Up Sequence 13.443283
Memory Load 55%
   System Physical Memory 39.816 / 73.277 MB
   Process Virtual Memory 46.125 / 1024.000 MB
-----> InfiniiVision is running <-----
failed open \Secure\InfiniiVision\LudicrousSpeed.usb
no workaround for USB phy
Exception 'Data Abort' (4): Thread-Id=04b000a6(pth=841ab178), Proc-Id=04ae00a6(pprc=841ab628) 'websockify.exe', VM-active=04ae00a6(pprc=841ab628) 'websockify.exe'
PC=40255064(ws2.dll+0x00005064) RA=00013410(websockify.exe+0x00003410) SP=0002fb7c, BVA=0003fffc
Exception 'Data Abort' (4): Thread-Id=04b000a6(pth=841ab178), Proc-Id=04ae00a6(pprc=841ab628) 'websockify.exe', VM-active=04ae00a6(pprc=841ab628) 'websockify.exe'
PC=40255064(ws2.dll+0x00005064) RA=00013410(websockify.exe+0x00003410) SP=0002fb7c, BVA=0003fffc

Originally I was thinking to reload firmware using TTL, but since I cannot get into u-boot prompt - can I replace that websockify.exe file directy? Not even sure if that's a problem here.
 

Offline ShQ

  • Contributor
  • Posts: 12
  • Country: nl
  • nonplussed
Glad at least spearload works!

That's odd, U-Boot should drop into a prompt automatically if invoked through spearload. What firmware version did you take the U-Boot and DDR image from?
I verified the setup to at least work on files from version 2.65 for me.
 
The following users thanked this post: onesystem

Offline onesystem

  • Regular Contributor
  • *
  • Posts: 61
  • Country: us
Glad at least spearload works!

That's odd, U-Boot should drop into a prompt automatically if invoked through spearload. What firmware version did you take the U-Boot and DDR image from?
I verified the setup to at least work on files from version 2.65 for me.

I used them from 2.66 and also 2.20 (tried both). spearload loaded them in less then a second - that's normal speed, correct?
 

Offline derZockerMP

  • Regular Contributor
  • *
  • Posts: 94
  • Country: de
Hello, has anyone the hacked firmware and workflow for installation to an DSO-X 3024A with firmware 2.36 on it. Is it possible to upgrade it too?
A link to a post where it is already described would be also nice. But didnĀ“t found it yet.

Thanks in advants.
 

Offline derZockerMP

  • Regular Contributor
  • *
  • Posts: 94
  • Country: de
I think i found somthing. But I need the original version 2.41 to update it first. Did anyone has this firmware and could send me please?
 

Offline PioB

  • Regular Contributor
  • *
  • Posts: 105
  • Country: ch
 
The following users thanked this post: derZockerMP

Offline onesystem

  • Regular Contributor
  • *
  • Posts: 61
  • Country: us
This is a step-by-step of everything that I did with oscilloscope to revive it. I am in need of some smart people here. Please help!

Oscilloscope model: DSOX2024A

Bought it on eBay with a note that its power supply was blown. It sure was blown, I replaced it with meanwell PSU - so that was handled.

While connecting to TTL header I noticed that whoever owned it before did solder work on it - one of the front end metal covers is missing (signs of resoldering are visible on each of the metal covers of all channels, with one missing). I tried to get more data from seller - they are liquidator aquisition place - have no data on where it came from or who worked on it.

Current SW version - unknown, but based on teraterm log, it is probably 2.66 or some other version that was bloated with additional files - I do not rule out that someone played with sofware since they knew what to do with hardware.

Here is what terraterm shows me if I turn on oscilloscope as is, without trying to do anything:

Code: [Select]
U-Boot 2010.03 (May 18 2017 - 11:28:22)Agilent P500                             
                                                                               
CPU:   SPEAr600                                                                 
DRAM:  128 MiB                                                                 
Flash: 512 KiB                                                                 
NAND:  internal ecc 128 MiB                                                     
                                                                               
Debug serial initialized ........OK                                             
RTC: 2022-2-8   1:40:11.70 UTC                                                 
                                                                               
Microsoft Windows CE Bootloader Common Library Version 1.4 Built Oct 29 2015 01:
39:04                                                                           
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: 2022-2-8   1:40:11.73 UTC                                                 
 Loading image 1 from memory at 0xD0600000                                     
O                                                                               
BL_IMAGE_TYPE_BIN                                                               
                                                                               
X                                                                               
XXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOOXOOOOXXXOOOOOOOOOXOOOOXOXXOXOXXOXOXOXOXXXXOOXXX
OOOOOOXXOXXOXXXXXXOOOXXXOXXOOOXXXOOOXOOXOOXXOOXOXOOOOXOXOOOOOXOOOXOOXOXOXOXXXXXO
XXXXOOOXOOOXOXOOOOXOOOOXOXOXOOOOOOXOOOXOOX                                     
OOOOXXXOOOOXOOXOOXOOOOOOOOOXOXOOOXOOOOOOXOXOOOOOXXOOOOOOOXOXOXXOOXOXOOOXOOOXOOXO
XXXOXOOOXOXXXXOXOXXOXXXXXOXOXXOOOXXXOXXXXXXOXXXXXXOXXXXOXOXOXOOOXXXXOXXXXXOOOXXO
XXOOXXOX                                                                       
XXOOXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOO
OOOOOOOOOOOXXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXXXOXOOO
XOXOOXOOXXXXXXXXXXXXOXrom_offset=0x0.                                           
XXImageStart = 0x80361000, ImageLength = 0x1ACA724, LaunchAddr = 0x80362000     
                                                                               
Completed file(s):                                                             
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x1ACA724  Name="" Target=RAM                   
 Loading image 1 succeeded.                                                     
ROMHDR at Address 80361044h                                                     
Preparing launch...                                                             
RTC: 2022-2-8   1:40:15.19 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 Feb 27 2019)                     
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:21:F2:AD                                           
Phy found addr 31 (ticks=3377)                                                 
WaitForLink Start (ticks=3379)                                                 
No Link (ticks=4381)                                                           
<--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, Feb 27 2019, 20:34:05                                           
Initializing FPGA...                                                           
****                                                                           
FPGA Type: Idaho                                                               
Ver: 2.027 Released                                                             
Build Time: Tue Oct 13 16:48:05 2015                                           
Build Machine: TS2404M                                                         
****                                                                           
No option module detected                                                       
Keyboard firmware version 32... ok                                             
Keyboard Info: Board id 7, Board rev 2                                         
Startup sequence is complete.                                                   
Saved configuration invalid                                                     
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 24.210651 seconds                                       
Start Up Sequence 13.471923                                                     
Memory Load 55%                                                                 
   System Physical Memory 39.805 / 73.277 MB                                   
   Process Virtual Memory 46.125 / 1024.000 MB                                 
-----> InfiniiVision is running <-----                                         
failed open \Secure\InfiniiVision\LudicrousSpeed.usb                           
                                                    no workaround for USB phy   
Exception 'Data Abort' (4): Thread-Id=04b000a6(pth=87f8a140), Proc-Id=04ae00a6(p
prc=87f8a5f0) 'websockify.exe', VM-active=04ae00a6(pprc=87f8a5f0) 'websockify.ex
e'                                                                             
PC=40255064(ws2.dll+0x00005064) RA=00013410(websockify.exe+0x00003410) SP=0002fb
7c, BVA=0003fffc                                                               
Exception 'Data Abort' (4): Thread-Id=04b000a6(pth=87f8a140), Proc-Id=04ae00a6(p
prc=87f8a5f0) 'websockify.exe', VM-active=04ae00a6(pprc=87f8a5f0) 'websockify.ex
e'                                                                             
PC=40255064(ws2.dll+0x00005064) RA=00013410(websockify.exe+0x00003410) SP=0002fb
7c, BVA=0003fffc                                                               

As far as I can see - there is no corruption signs during the boot, until the very end, referencing websockify.exe and ws2.dll. Those two could be a problem or they could be trying to access something that is a problem.

Next - my reasoning was to get the oscilloscope to boot from usb, and then upload the 2.66 firmware. I bought the Sandisk flash drive referenced on this forum, formatted it FAT, places files in sequence recommended, and here is the output I get on teraterm while oscilloscope is booting with flash drive incerted:

Code: [Select]
U-Boot 2010.03 (May 18 2017 - 11:28:22)Agilent P500

CPU:   SPEAr600
DRAM:  128 MiB
Flash: 512 KiB
NAND:  internal ecc 128 MiB

Debug serial initialized ........OK
RTC: 2022-2-21   6:44:13.1 UTC

Microsoft Windows CE Bootloader Common Library Version 1.4 Built Oct 29 2015 01:39:04
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: 2022-2-21   6:44:13.4 UTC
 Loading image 1 from memory at 0xD0600000
O
BL_IMAGE_TYPE_BIN

X
XXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOOXOOOOXXXOOOOOOOOOXOOOOXOXXOXOXXOXOXOXOXXXXOOXXXOOOOOOXXOXXOXXXXXXOOOXXXOXXOOOXXXOOOXOOXOOXXOOXOXOOOOXOXOOOOOXOOOXOOXOXOXOXXXXXOXXXXOOOXOOOXOXOOOOXOOOOXOXOXOOOOOOXOOOXOOX
OOOOXXXOOOOXOOXOOXOOOOOOOOOXOXOOOXOOOOOOXOXOOOOOXXOOOOOOOXOXOXXOOXOXOOOXOOOXOOXOXXXOXOOOXOXXXXOXOXXOXXXXXOXOXXOOOXXXOXXXXXXOXXXXXXOXXXXOXOXOXOOOXXXXOXXXXXOOOXXOXXOOXXOX
XXOOXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXXXOXOOOXOXOOXOOXXXXXXXXXXXXOXrom_offset=0x0.
XXImageStart = 0x80361000, ImageLength = 0x1ACA724, LaunchAddr = 0x80362000

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x1ACA724  Name="" Target=RAM
 Loading image 1 succeeded.
ROMHDR at Address 80361044h
Preparing launch...
RTC: 2022-2-21   6:44:16.51 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 Feb 27 2019)
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:21:F2:AD
Phy found addr 31 (ticks=3415)
WaitForLink Start (ticks=3417)
No Link (ticks=4419)
<--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: 171 ms
   SNANDFLASH: 171 ms
   USB Hard Disk Drive: 171 ms


U-Boot 2010.03 (May 18 2017 - 11:28:22)Agilent P500

CPU:   SPEAr600
DRAM:  128 MiB
Flash: 512 KiB
NAND:  internal ecc 128 MiB

Debug serial initialized ........OK
RTC: 2022-2-21   6:45:25.22 UTC

Microsoft Windows CE Bootloader Common Library Version 1.4 Built Oct 29 2015 01:39:04
Microsoft Windows CE 6.0 Ethernet Bootloader for the Agilent P500 board
Adaptation performed by Agilent Technologies (c) 2008

......


Detects USB Hard Disk Drive, hangs on this point for about 1.5 min, then reboots and repeats the cycle. I tried with and without Secure Folder, formatting different ways, doing it with various versions of the firmware, no go so far.

I also tried to access the U-Boot. With oscilloscope turned off, I held space bar, turned on oscilloscope and got the following:

Code: [Select]
U-Boot 2010.03 (May 18 2017 - 11:28:22)Agilent P500

CPU:   SPEAr600
DRAM:  128 MiB
Flash: 512 KiB
NAND:  internal ecc 128 MiB

Debug serial initialized ........OK
RTC: 2022-2-21   6:45:31.83 UTC

Microsoft Windows CE Bootloader Common Library Version 1.4 Built Oct 29 2015 01:39:04
Microsoft Windows CE 6.0 Ethernet Bootloader for the Agilent P500 board
Adaptation performed by Agilent Technologies (c) 2008



P500 Boot Loader Configuration :

Mac address .......... (00:30:D3:21:F2:AD)
Ip address ........... (192.168.1.145)
Subnet Mask address .. (255.255.255.0)
DHCP ................. (Enabled)
Boot delay (seconds).. (0)
Load image 1 at startup

Image addresses. (0xdxxxxxxx for NAND, 0x8xxxxxxx for RAM)
        1 (0xd0600000)
        2 (0xd1600000)

l) Load memory resident image Load image 1 now
1) Load memory resident image 1 now
2) Load memory resident image 2 now
3) Load memory resident image 3 now
d) Download from platform builder now
u) Start u-boot by resetting
v) Verify Images
>

And no matter what USB to TTL I use (FDTI, Prolific, or Silabs CP2102), it only goes to P-Boot as above.

Then I tried loading p500_ddrdriver.bin and u-boot_image.bin using spearload. It seems to work - goes through all of the prompts well, and I also used packet sniffer to see what went on between pc and scope while spearload was running (please see attached log) it seems that everything went well. BUT no matter what - with space bar pressed I only get to P-Boot still.

This covers everything I tried doing with this device. I would like to find out if there is anything else that I can do to revive this scope.
 

Offline Bud

  • Super Contributor
  • ***
  • Posts: 7301
  • Country: ca
Detects USB Hard Disk Drive, hangs on this point for about 1.5 min, then reboots and repeats the cycle.

Check if it writes anything back to the USB drive. Compare the drive content and size before and after. If it writes some sort of configuration data dump, then likely the firmware version on the scope does not have USB boot feature. Check this to rule out possibility of USB boot.
Facebook-free life and Rigol-free shack.
 

Offline onesystem

  • Regular Contributor
  • *
  • Posts: 61
  • Country: us
Ok - I freshly formatted the USB, loaded files, recorded quantity of files and their size before placing it into scope and after boot - it is identical. So nothing is being written to USB.

Will I gain any additional ways of resurrecting the scope if I get the network card purchased and installed? Or should I not worry about it for now?
« Last Edit: February 05, 2025, 12:13:18 am by onesystem »
 

Online tv84

  • Super Contributor
  • ***
  • Posts: 3356
  • Country: pt
Re: DSOX2000 and 3000 series - licence , have anyone tried to hack that scope ?
« Reply #3460 on: February 01, 2025, 10:39:31 am »
Will I gain any additional ways of resurrecting the scope if I get the network card purchased and installed? Or should I not worry about it for now?

Don't worry for now.
 

Offline onesystem

  • Regular Contributor
  • *
  • Posts: 61
  • Country: us
Re: DSOX2000 and 3000 series - licence , have anyone tried to hack that scope ?
« Reply #3461 on: February 02, 2025, 07:08:04 pm »
Scope is running latest firmware now, not cycling.
EDIT: 25-02-04: Scope is in perfect working order, ever channel works well, no deviations or errors, all digital channels work well, wavegen works great. Compared against the DSOX1202G, which now I am going to sell.

I followed the instructions on this blog:

https://ripitapart.com/2018/10/15/gaining-access-to-the-windows-ce-desktop-and-doom-on-the-keysight-dsox1102g-oscilloscope/

Gained access to windows of the scope. Then in using command prompt navigated to Windows directory, found program called infiniiVisionUpdateService.exe, in command prompt typed infiniiVisionUpdateService.exe \usb\2000XSeries.02.66.20240123001.ksx, and scope updated to the 2.66 firmware and is runnig well now - no errors - serial output shows normal running.

I am not sure how useful this trick will be for anyone else, since my case scenario was quite unique - scope was crashing all the way at the end, already after the final loading of the scope program.

So in summary:
1. FAT formatted USB
2. placed infiniivisionStartupOverride.txt in the root of usb (knowing it will stump scope from booting but looking at usb for some time before rebooting)
3. placed extracted content of ScopeLiberator-Release-2.0.zip into the usb flash drive root (without any folder structure)
4. placed 2000XSeries.02.66.20240123001.ksx file into usb root
5. connected keyboard to the back of the scope, plugged usb in front.
6. Turned on the scope and waited until lights started circling on buttons, then pressed Windows button + R, then typed \usb\a.bat and pressed Enter
7. Windows 98-like desktop showed up. Navigated to usb drive, started command prompt, in there switched to Windows directory, typed infiniiVisionUpdateService.exe \usb\2000XSeries.02.66.20240123001.ksx and update went through.
8. When scope was rebooting, I unplugged the flash drive and got a working scope.

Thank you everyone for assistance and guidance.
« Last Edit: February 05, 2025, 12:11:40 am by onesystem »
 
The following users thanked this post: analogRF

Offline Campus

  • Contributor
  • Posts: 31
Re: DSOX2000 and 3000 series - licence , have anyone tried to hack that scope ?
« Reply #3462 on: February 12, 2025, 11:02:12 am »
I reactivated my 2004A after years in storage and after reading hours in this thread I am wondering what to do. Currently the scope boots up with the boot screen which then goes dark and the button just keep blinking. Is that the NAND problem?

But I have a usb boot stick with a patched 2.39 that still works fine and the scope starts working.

Is there any way to get a patched (PhillyFlyer?) 2.66 booting from usb or is a full install required these days?
 

Offline PioB

  • Regular Contributor
  • *
  • Posts: 105
  • Country: ch
Re: DSOX2000 and 3000 series - licence , have anyone tried to hack that scope ?
« Reply #3463 on: February 12, 2025, 11:58:44 am »
Hi Campus
If I understand correctly, there's no way to boot the new firmwares from usb anymore. You need to install it. (rename .ksx to .cab as the filename changed sometime after 2.4?? and earlier versions didn't recognize ksx yet)

https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/msg5783849/#msg5783849 has the recipe to patch 2.66. (only works with the windows version of (bs)patch, linux versions fail. So cygwin is needed.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf