Electronics > Repair
Lecroy wavesurfer 3024 fail to boot
peter-h:
I had the same boot problem with a 3034 about 2 years ago; 1 year from new. They fixed it under the warranty, but next time it will be expensive; AFAIK their fixed repair charge is about 1k.
ollopa:
The WS3K (non-Z) uses the TI DM3730 OMAP3 SoC, for which there is no such thing as a "BIOS". By watching the serial console output during boot I can see that what this "BIOS" update actually does is upgrade the NAND flash ECC algorithm. I think they were using the default Hamming correction which can only correct for 1 bit error. The DM3730 is capable of hardware computed BCH-4 and BCH-8 however the silicon errata says that BCH-4 is completely broken. I think we can assume they are upgrading to BCH-8. The MT29F4G16ABBDA3W NAND flash used also has OOB size 64 which is large enough for BCH-8.
The nature of NAND flash is to have a high probability of bit errors and it requires error correction. I think we can assume that the initial ECC algorithm used was too weak and eventually all scopes will need this recovery process and the "BIOS upgrade" which actually just re-computes NAND flash ECC data.
First boot after confirming the "BIOS :-DD upgrade" (The screen shows four colored squares and updates the block number during each ScreenPrint call logged)
--- Quote ---Lecroy NAND XLDR, Jun 26 2020 at 23:39:17 Version BSP_WINCE_ARM_A8 2.30.00.03...............JMP
Lecroy EBOOT 0.0, BSP BSP_WINCE_ARM_A8 2.30.00.03
TPS659XX Version 0x10 (ES1.1)
>>>>> EBoot Boot Perf timer 1
Preparing for download...
ECC 0
Checking bootloader blocks are marked as reserved (Num = 32). Min:29
IsFlashBlockConfiguredForInternalEccCorrection 4, ff,ff, rc:0
ECC 0
INFO: Boot CFG ... OK
>>>>>Boot configuration Duration 21ms
ECC 0
ECC 0
IsValidMBR: MBR sector = 0x800 (valid MBR)
OpenPartition: Partition Exists=0x1 for part 0x20.
ECC 0
>>>>>LCD.BIN extracted from NAND Duration 71ms
>>>>>>>spi load fpga start time=93
>>>>>>>-SPI_WriteRead(rc = 465028)
>>>>>>>spi load fpga end time=372
>>>>>LCD.BIN written to FPGA Duration 279ms
ECC 0
>>>>>Logo displayed Duration 356ms
>>>>>Partitions checked Duration 0ms
>>> Forcing cold boot (non-persistent registry and other data will be wiped) <<<
>>>>>Reset checked Duration 9ms
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
SDCard: menu.bin not found
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
SDCard: format.bin not found
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
SDCard: recovery.bin not found
>>>>>BLShowInitLogo displayed Duration 621ms
ScreenPrint
Reconfiguring flash for 0 to 3 ECC correction
ECC 0
ReconfigureFlashIntToExtECC - Updating block:4
ScreenPrint
ECC 0
ECC 3
FMD_EraseBlock 4
ReconfigureFlashIntToExtECC - Updating block:5
ScreenPrint
ECC 0
ECC 3
.
.
.
FMD_EraseBlock 4094
ReconfigureFlashIntToExtECC - Updating block:4095
ScreenPrint
ECC 0
ECC 3
FMD_EraseBlock 4095
ECC 3
ECC 3
FMD_EraseBlock 5
ScreenPrint
ECC 3
FMD_EraseBlock 5
>>>>>Special files checked Duration 175580ms
>>>>>Logo displayed Duration 0ms
ECC 3
IsValidMBR: MBR sector = 0x800 (valid MBR)
OpenPartition: Partition Exists=0x1 for part 0x20.
BP_SetDataPointer at 0x0
>>>>>OS Image loaded Duration 21960ms
Launch Windows CE image by jumping to 0x81002000...
--- End quote ---
And then on the next boot post-upgrade:
--- Quote ---Lecroy NAND XLDR, Jun 26 2020 at 23:39:17 Version BSP_WINCE_ARM_A8 2.30.00.03...............JMP
Lecroy EBOOT 0.0, BSP BSP_WINCE_ARM_A8 2.30.00.03
TPS659XX Version 0x10 (ES1.1)
>>>>> EBoot Boot Perf timer 1
Preparing for download...
ECC 0
Checking bootloader blocks are marked as reserved (Num = 32). Min:29
IsFlashBlockConfiguredForInternalEccCorrection 4, 3,fc, rc:1
ECC 3
ECC 3
INFO: Boot CFG ... OK
>>>>>Boot configuration Duration 22ms
ECC 3
ECC 3
IsValidMBR: MBR sector = 0x800 (valid MBR)
OpenPartition: Partition Exists=0x1 for part 0x20.
ECC 3
>>>>>LCD.BIN extracted from NAND Duration 82ms
>>>>>>>spi load fpga start time=105
>>>>>>>-SPI_WriteRead(rc = 465028)
>>>>>>>spi load fpga end time=383
>>>>>LCD.BIN written to FPGA Duration 279ms
ECC 3
>>>>>Logo displayed Duration 377ms
>>>>>Partitions checked Duration 0ms
>>> Forcing cold boot (non-persistent registry and other data will be wiped) <<<
>>>>>Reset checked Duration 9ms
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
SDCard: menu.bin not found
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
SDCard: format.bin not found
Init HW: controller RST
SDCardInit: No media!
BLSDCardFileExists: fileio init failed
SDCard: recovery.bin not found
>>>>>Special files checked Duration 371ms
>>>>>Logo displayed Duration 4ms
ECC 3
IsValidMBR: MBR sector = 0x800 (valid MBR)
OpenPartition: Partition Exists=0x1 for part 0x20.
BP_SetDataPointer at 0x0
>>>>>OS Image loaded Duration 21969ms
Launch Windows CE image by jumping to 0x81002000...
Windows CE Kernel for ARM (Thumb Enabled)
OAL: CPU revision 0x12:DM3730
OAL: CPU L2 Aux register 0x400042
****Profiler Build****
---High Performance Frequency is 26000847 hz---
--- End quote ---
eevChrissy:
Hello,
I have similar issue with a WS3024.
After doing recovery, it hangs now in the screen with the 4 colours in each quadrant.
May, I am missing something!?
How can I watch that nice "serial console output during boot"?
And, as a last option, is it possible to recover to a SIGLENT SDS3000? Guess the calibration would be lost...?
Very Best Thanks, for any help!
ollopa:
It is supposed to update the flash block number on the screen as it rewrites the ECC data. The operation can take a while.
If you don't see the screen updating and you have patiently waited several minutes then there is probably an error it can not automatically fix.
My WS3K still had trouble writing to flash after the recovery. I had to boot under Linux and erase the NAND flash, then perform the recovery. Afterwards it has been operating fine. I don't know if you will lose cal data because mine had calibration issues to begin with. It was, and in some ways still is, a very sick scope.
If you want serial output you have to disassemble the scope until you have access to the main board, then solder a header or some wires to three pads and connect a 3.3V FTDI or equivalent. I don't have a picture right now and my scope is partially reassembled so I cannot just go snap one. If you want to go that far, however, I can pull the shielding back off and take pictures sometime in the next few days.
eevChrissy:
@ollopa
Very Best Thanks for that help...
Think, I can open it, and create a serial COM connection over FTDI...
But, right now, I didn't understand the second step...
How to Boot Linux and erase the NAND flash ???
Thanks for further help... and Best regards
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version