Author Topic: Trying to revive DSO-X-2012A  (Read 1370 times)

0 Members and 1 Guest are viewing this topic.

Offline diablodude64Topic starter

  • Contributor
  • Posts: 13
  • Country: us
Trying to revive DSO-X-2012A
« on: October 07, 2023, 03:18:38 am »
Hey everyone,

I have been following the posts in https://www.eevblog.com/forum/testgear/dsox2000-and-3000-series-licence-have-anyone-tried-to-hack-that-scope/2075/ and everything works up until running the "go 0x00362000" command. This is the log from Tera Term.

Can anyone help point me in the right direction? Is this a lost cause?



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
p500> loady 0x0361000 115200
## Ready for binary (ymodem) download to 0x00361000 at 115200 bps...
CCxyzModem - CRC mode, 1(SOH)/19482(STX)/0(CAN) packets, 6 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:ED:6B
Phy found addr 31 (ticks=2856)
WaitForLink Start (ticks=2857)
No Link (ticks=3860)
<--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
running \Secure\Startup\infiniivision.lnk...
Our command line is
Performing Startup
Ending ProcessStartupFolder
                           Released build, Sep 13 2013, 11:12:41
Initializing FPGA...
****
FPGA Type: Idaho
Ver: 1.099 Released
Build Time: Thu May 02 17:37:58 2013
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
Exception 'Data Abort' (4): Thread-Id=061e0006(pth=853d1a90), Proc-Id=04ee000a(pprc=83c46ba0) 'infiniivisionLauncher.exe', VM-active=04ee000a(pprc=83c46ba0) 'infiniivisionLauncher.exe'
PC=40f71890(infiniivisioncore.dll+0x00281890) RA=40f71884(infiniivisioncore.dll+0x00281884) SP=0247f560, BVA=110fd0ec
The exception 0xC0000005 occurred at address 0x40F71890.


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:      2011-08-24  22:35:34 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    36045 Bytes = 35.2 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 Aug 24 2011 15:15:48
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
XXXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOXOXOOOOXXOOOOOOOOOXOOOOXOXXOXOXXOOOXOXXXXXOOXXXOOOOOOXOOXXXOXXOOOXOXXOOXXOXOOOXOOXOOXXOOOXOOOOXOXOOOOOXOOOXOOXIncorrect Data 3 EccResult: 956699 EccError: cf00ff EccRead: 5a6666
 EBOOT_ReadFlash failed offset 93faf9
 EBOOT_ReadFlash failed location d0940000
ODeCompressFlash: CeCompressDecode() failed
 CeDecompressFlashBlock failed
****** Data record 53 corrupted, ABORT!!! ******

Completed file(s):
-------------------------------------------------------------------------------
  • : Address=0x80361000  Length=0x13064E8  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


Thank you!
 

Offline switchabl

  • Frequent Contributor
  • **
  • Posts: 445
  • Country: de
Re: Trying to revive DSO-X-2012A
« Reply #1 on: October 07, 2023, 07:44:41 am »
I think it is still trying to run the (possibly corrupted or incompatible) application software from NAND. IMHO that's an error in the (otherwise very helpful) guide by titiris and infiniivision.lnk should be
Code: [Select]
44#\usb\infiniiVision\infiniiVisionLauncher.exe
for best chance of success.

If that doesn't help, you could still try to create a boot image from an earlier firmware version than 2.35 (ideally the same one that is currently installed).
« Last Edit: October 07, 2023, 07:49:03 am by switchabl »
 

Offline diablodude64Topic starter

  • Contributor
  • Posts: 13
  • Country: us
Re: Trying to revive DSO-X-2012A
« Reply #2 on: November 26, 2023, 01:53:07 am »
Just wanted to follow up that I was able to get it up and running again. My issue stemmed from the folder structure on the flash drive. Thank you!
 

Offline sebastienjean

  • Newbie
  • Posts: 3
  • Country: fr
Re: Trying to revive DSO-X-2012A
« Reply #3 on: July 10, 2024, 10:08:12 am »
Hi,

Can you explain what was wrong with your folder structure ? I'm stuck nearly at the same point with the same device. But in my case i try to flash 2.66 (could not find any earlier version).

Thx by advance.
S.
 


Share me

Digg  Facebook  SlashDot  Delicious  Technorati  Twitter  Google  Yahoo
Smf