Products > Test Equipment
Agilent DSOX3054A not booting possible NAND corruption HELP! (RESOLVED)
<< < (6/11) > >>
analogRF:
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:
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:
OMG!
I tried the same procedure with V2.30 and this is what happened:  ;D ;D >:( >:(

--- Code: ---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 <-----

--- End code ---

BUT THERE IS NO DISPLAY  >:D |O :-// :-//
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:
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:

--- 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

--- End quote ---

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

--- End quote ---

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??
Navigation
Message Index
Next page
Previous page
There was an error while thanking
Thanking...

Go to full version
Powered by SMFPacks Advanced Attachments Uploader Mod