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

[Bud]

Agreed.

[tv84]

Here is the mapping:

Code: [Select]

00000000 - XLOADER  (contents up to aprox. offset 0x1540)
00010000 - UBOOT (contents up to aprox. offset 0x3F90C)
00040000 - Environment variables  (contents up to aprox. offset 0x40520)
00050000 - PBOOT (contents up to aprox. offset 0x593B8)
00060000 - Environment variables  (contents up to aprox. offset 0x60520)  2ND COPY
00070000 - MAC address

[sajsoni]

I tried to flash with the existing settings in SPEAr flashing Utilities. As you can see in the attached screenshots, the size of one sector is 0x10000, and I can only change the number of sectors. The files I loaded are from 3000KSSeries.02.65.20210307001.cab are (kloader_image.bin, u-boot_image.bin, pboot_rel.bin).
After flashing in SPEAr 600, Uboot appeared on UART lines, but with the error FPGA programming failed! (picture Uboot attached)
However I tried to load nk.nb0 and run it from address 0x00362000 from the USB drive but it stopped (picture Uboot2 attached). Only the Agilent logo appeared on the screen.
What to do now? Should I delete the flash again and load it with new offsets or can something be done with p500>?
Are these .bin files really appropriate?

[Bud]

@sajsoni you are moving too fast....please hold on.

First, Pboot was only one sector long, not 44 , not sure how and if that might have caused  anything you are experiencing now.
What it tells you is your fpga image is corrupted in NAND. Do not attempt to boot until you fix this issue. The good news is you can upload the fpga image the same way using y modem. It is a separate bin file in the firmware package. I have done that once and i recall i uploaded to RAM and from there wrote into NAND - i need to check my records if i have any notes left.
What you can do in the meanwhile is to run printenv from Uboot and compare the output against tv84's post right above this one.

[Bud]

I found what I did was I loaded FPGA bin file to RAM using ymodem, but did not write into NAND then. Instead I just sent the uploaded blob from RAM directly to FPGA and started the kernel image. Once the scope booted successfully,  I ran firmware update and it updated the FPGA image in NAND.

This is an excerpt from the log:

First, load the existing fpga image from NAND to RAM address 0x800000 (to compare later with the good image)

Code: [Select]

p500> nand read 800000 60000 45480

NAND read: device 0 offset 0x60000, size 0x45480
 283776 bytes read: OK

Load a copy of the good fpga image using Ymodem to RAM address 0x900000

Code: [Select]

p500> loady 900000 115200
## Ready for binary (ymodem) download to 0x00900000 at 115200 bps...
CCxyzModem - CRC mode, 1(SOH)/278(STX)/0(CAN) packets, 7 retries
## Total Size      = 0x00045480 = 283776 Bytes

Check the loaded image's CRC

Code: [Select]

p500> crc 900000 45480
CRC32 for 00900000 ... 0094547f ==> 5f15252c

Compare the two fpga  images

Code: [Select]

p500> cmp 800000 900000 45480
word at 0x00801070 (0x00008000) != word at 0x00901070 (0x00000000)
Total of 1052 words were the same
As can be seen, one byte (actually one bit!) in the existing fpga image was corrupted.

Program the FPGA using the uploaded good image in RAM

Code: [Select]

p500> fpga 900000 45480
Start the scope

Code: [Select]

p500> run bootcmd
## Booting kernel from Legacy Image at f8050000 ...
   Image Name:   PBOOT
   Created:      2015-05-07   8:18:27 UTC
.....
...And run firmware update as usual from the scope application.
Note that the length of the fpga image will be different in your case - look in the environment variables tv84 posted above , so you have to replace it in the Uboot commands:

fpgasize=0x75394

Alternatively, I guess you could try loading the FPGA binary using the USB Flasher program, my guess the load offset in NAND would be 0x60000, and the length woudl be 0x75394 converted to number of sectors. Or use nand write command in Uboot to overwrite the image in NAND with the uploaded image at RAM address 0x900000. I have not tried that. The method I used seems to be a lower risk though as it does not modify the NAND by itself.

[Bud]

What you can do in the meanwhile is to run printenv from Uboot and compare the output against tv84's post right above this one.

Make sure you check the environment variables , do not try to boot until they are in place.

[sajsoni]

@Bud @ tv84 Thanks for the answers!

Now it's not all clear to me about environment variables ... this is a printout of the printenv command:

Code: [Select]

U-Boot 2010.03 (May 18 2017 - 11:28:22) 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
BMP data is not valid. Use splash bmp
Press space to stop autoboot: 2
p500> printenv
bootcmd = tftp 0x4000000 nk.bin; bootm 0xf8050000
ramboot = dhcp 0x4000000 nk.bin; bootm 0xf8050000
bootdelay = 3
baudrate = 115200
serverip = 192.168.1.10
preboot = splash load; fpga; expi
gatewayip = 192.168.1.10
netmask = 255.255.255.0
usbtty = cdc_acm
fpgadata = 0xd0060000
fpgasize = 0x75394
splashdata = 0xd0000000
dispParm1 = 0x300 0x400 0x2625A00 0x1 0x3
dispParm2 = 0x20 0x4c 0x1 0x2 0x3
boardversion = 4
ps = 0
rtc = 0
erase_env = protect off 1: 4, erase 1: 4
store_uboot = protect off 1: 1-3; erase 1: 1-3; cp.b 0x800000 0xF8010000 $ {filesize}; protect on 1: 1-3; imi 0xF8010000
get_uboot_eth = dhcp 0x800000 u-boot_image.bin; run store_uboot
get_uboot_uart = loadb 0x800000 115200; run store_uboot
ethaddr = 00: 03: d3: 04: 10: 00
serialnum = serial number not programmed
chipversion = BD
nimages = 1
image1 = 0xd0400000
fsstart = 0x2c00000
numfilesystems = 1
lengthfilesystem1 = 0x5400000
lengthfilesystem2 = 0x0
ecc = 1
verify = n
ipaddr = 192.168.1.100
ethact = smsc

Environment size: 893/16380 bytes
p500>

I compared the FPGA images, but I didn't try to boot. I loaded FPGA3000A.bin (469kB), is that the appropriate bin file? The result is as follows:

Code: [Select]

p500> nand read 800000 60000 45480
NAND read: device 0 offset 0x60000, size 0x45480
 283776 bytes read: OK
p500> loady 900000 115200
## Ready for binary (ymodem) download to 0x00900000 at 115200 bps ...
CCxyzModem - CRC mode, 2 (SOH) / 469 (STX) / 0 (CAN) packets, 4 retries
## Total Size = 0x00075394 = 480148 Bytes
p500> crc 900000 45480
CRC32 for 00900000 ... 0094547f ==> 3733a6e1
p500> cmp 800000 900000 45480
word at 0x00800144 (0x0000a000)! = word at 0x00900144 (0x0000a402)
Total of 81 words were the same
p500>

[Bud]

I believe there is only one fpga bin file in the firmware package.

You should be using Your fpga bin file's length when doing Uboot cpmmands, 45480 was for my EDUX1000x scope. Look at fpgasize variable in your printenv and it also must match the fpga bin file length in Hex.

@t84 what scope model your printenv was from? Seems there are differences with sajsoni's one.

[tv84]

Mine was a pure 3000A.

But without any previous erasures... 

Since sajsoni provided his MAC address, here is a FULL dump of the NOR mem for sajsoni to flash.

This includes all the bootloaders and the env. vars and the correct MAC address, as taken from a 3000A dump.

I think it can't get any simpler. Use the SPEAR600 app to flash only this file from offset 0.

[sajsoni]

The problem is that I don't have a connection between the PC and the oscilloscope now. I can't run SPEar 600 flash utilites. Maybe because Uboot loaded? Should I do erase flash again?

[Bud]

Do not do it. There are differences in image offsets and filesystem size between your environment and tv84's. Also you are going to lose access to Uboot. And the scary thing that ecc environment variable is missing in tv84's SPI printenv list - that may totally screw up your scope including the filesystem and calibration.

I recommend you run through my procedure again but with proper fpga size parameter and see if your resident fpga image and the original one produce a match or mismatch.

[tv84]

Bud, I have no way to certify my statements but the env vars are in the NOR flash (that is guaranteed).

So, all the contents of his printenv were taken from his NOR flash after a reconstruction by the SPEAR tool (using defaults values).

I think those default values are not better than my dump taken from a working machine.

BUT, I'm in no position to guarantee all of this since I don't have your experience in this scope.

[Bud]

I am not saying they are incorrect. The difference is likely because of the scopes' model variation.

Edit: what I am trying to understand is if sajsoni's env variables are default ones or specific to his scope.

@sajsoni - do you know the firmware version your scope had before the incident ?

[sajsoni]

I hurried again and loaded the .bin file uploaded by tv84. First I deleted the flash and loaded only one file starting from 0 to 8 sectors (one size 0x10000). After a successful flash when I turn on the oscliscope sometimes it boots successfully and sometimes not. I tracked across the UART where the boot fits

One example of a boot. Interrupts on kernel loading ...

Code: [Select]

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:      2015-05-07   8:18:27 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    37749 Bytes = 36.9 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Uncompressing Kernel Image ... OK

Starting kernel ...

An example of another boot. unsuccessful loading of all images .....

Code: [Select]

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:      2015-05-07   8:18:27 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    37749 Bytes = 36.9 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Uncompressing Kernel Image ... OK

Starting kernel ...


Debug serial initialized ........OK
RTC: 2021-3-7   23:26:40.8 UTC

Microsoft Windows CE Bootloader Common Library Version 1.4 Built May  7 2015 01:38:03
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: 2021-3-7   23:26:40.11 UTC
 Loading image 1 from memory at 0xD0600000
O
BL_IMAGE_TYPE_BIN

X
XXXXOOOOXXOOOOOOOOERROR: Checksum failure (expected=0x31D2860  computed=0x31BA795)
****** Checksum failure on record 7, ABORT!!! ******

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x1ACB780  Name="" Target=RAM
 Loading image 1 failed, trying next one
 Loading image 2 from memory at 0xD1600000
O
BL_IMAGE_TYPE_BIN

X
XXXXOOOOXXOOOOOOOOERROR: Checksum failure (expected=0x31D2860  computed=0x31BBD0F)
****** Checksum failure on record 7, ABORT!!! ******

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x1ACB780  Name="" Target=RAM
 Loading image 2 failed, trying next one
 All images failed

Press r to reset


An example of a successful (at least I think it is) boot. All channels appear and everything looks good.

Code: [Select]

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:      2015-05-07   8:18:27 UTC
   Image Type:   ARM Linux Kernel Image (gzip compressed)
   Data Size:    37749 Bytes = 36.9 KiB
   Load Address: 00000000
   Entry Point:  00000000
   Uncompressing Kernel Image ... OK

Starting kernel ...


Debug serial initialized ........OK
RTC: 2017-5-19   23:17:58.87 UTC

Microsoft Windows CE Bootloader Common Library Version 1.4 Built May  7 2015 01:38:03
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: 2017-5-19   23:17:58.91 UTC
 Loading image 1 from memory at 0xD0600000
O
BL_IMAGE_TYPE_BIN

X
XXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOOXOOOOXXXOOOOOOOOOXOOOOXOXXOXOXXOXOXOXOXXXXOOXXXOOOOOOXXOXXOXXXXXXOOOXXXOXXOOOXXXOOOXOOXOOXXOOXOXOOOOXOXOOOOOXOOOXOOOXXXOXOXXXXXXOXXXXOOOXOOOXOXOOOOXOOOOXOXOXOOOOOOX
OOOXOOXOOOOXXXOOOOXOOXXOOXOOOOOOOOOXOXOOOXOOOOOOXOXOOOOXOXOOOOOOOXOXOXOOXOXOOOXOOOXOOXOXXOXOOOXOXXXXXOXOXXOXXXXOXOXXOOOXXOXXXXXXXOXXXXXXXOXXXXOXOXXOXOOOXXXXOXXXXXOOOXXOXX
OOXXOXXXOOXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXXXOXOOOXOXOOXOOXXXXXXXXXXXXXrom_offset=0x0.
XXImageStart = 0x80361000, ImageLength = 0x1ACB780, LaunchAddr = 0x80362000

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x1ACB780  Name="" Target=RAM
 Loading image 1 succeeded.
ROMHDR at Address 80361044h
Preparing launch...
RTC: 2017-5-19   23:18:2.34 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 Mar  7 2021)
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:03:D3:04:10:00
Phy found addr 31 (ticks=3044)
WaitForLink Start (ticks=3045)
No Link (ticks=4048)
<--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

      creating \Agilent Flash\selftest\
      creating \Agilent Flash\wfmMem\
      creating \Agilent Flash\LxiMdns\Released build, Mar  7 2021, 23:23:02
Initializing FPGA...
****
FPGA Type: Wyoming
Ver: 2.011 Released
Build Time: Tue May 27 16:03:14 2014
Build Machine: TS2404M
****
No option module detected
Keyboard firmware version 32... ok
Keyboard Info: Board id 1, Board rev 3
Startup sequence is complete.
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 23.916475 seconds
Start Up Sequence 13.584780
Memory Load 55%
   System Physical Memory 39.672 / 73.277 MB
   Process Virtual Memory 49.500 / 1024.000 MB
-----> InfiniiVision is running <-----
failed open \Secure\InfiniiVision\LudicrousSpeed.usb
                                                    no workaround for USB phy


What to do next? Now the oscilloscope sometimes boots from the first attempt and sometimes from the 20th ...
Before deleting the flash via UART I was able to load version 3000XSeries.02.35.2013061800. Later, I upgraded to 3000XSeries.02.65.20210307001 via USB according to the procedure on Keysight

[Bud]

As I warned you, you now can't access  Uboot...
Regarding inconsistent boot I can't recall people having this problem. Maybe the memory is indeed faulty, but i would check the power supply voltages quality and  power supply connectors for oxidation. Also if the PS electrolytics are of a junk brand i would look at replacing them.

[sajsoni]

I can with space break boot and get p500 ...
The only thing is that now I can't read the data from USB ...

[Bud]

From p500 prompt what is your printenv output now ?

[sajsoni]

Code: [Select]

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> printenv
ramboot=dhcp 0x4000000 nk.bin;bootm 0xf8050000
baudrate=115200
usbtty=cdc_acm
fpgasize=0x75394
splashdata=0xd0000000
dispParm1=0x300 0x400 0x2625A00 0x1 0x3
dispParm2=0x20 0x4c 0x1 0x2 0x3
boardversion=4
ps=0
rtc=0
erase_env=protect off 1:4;erase 1:4
store_uboot=protect off 1:1-3;erase 1:1-3;cp.b 0x800000 0xF8010000 ${filesize};protect on 1:1-3;imi 0xF8010000
get_uboot_eth=dhcp 0x800000 u-boot_image.bin;run store_uboot
get_uboot_uart=loadb 0x800000 115200;run store_uboot
serialnum=serial number not programmed
ethact=smsc
bootdelay=0
bootaddr=0x700
loadaddr=0x00800000
chipversion=BD
nimages=2
image1=0xd0600000
image2=0xd1600000
fpgadata=0xd0060000
fimage=1
pbootdelay=0
numfilesystems=2
lengthfilesystem1=0x2800000
lengthfilesystem2=0x2800000
fsstart=0x2c00000
bootCeFlash=bootm 0xf8050000
uart2=115200
bootcmd=run keyrst;run bootCeFlash
preboot=fpga; expi 62500
keyrst=mw d8100400 6 1;mw d8100008 0 1;mw d8100008 2 1
bootfile=nk.bin.comp
filesize=C72BF2
blocksize=0xc80000
fileaddr=800000
gatewayip=146.223.241.1
netmask=255.255.255.0
serverip=146.223.241.68
stdout=serial
stdin=serial
stderr=serial
infiniiVisionCabFile=
infiniiVisionHostname=
infiniiVisionNetworkAdapter=
infiniiVisionInstallStatus=installing cab file
ethaddr=00:03:d3:04:10:00
manufacturer=
verify=n
ipaddr=192.168.1.100

Environment size: 1299/16380 bytes
p500>

[Bud]

It looks ok. I am puzzled how it still gives access to Uboot with bootdelay=0.
Try bootcmd command  and hit space right away. You should see Pboot menu from which you can verify images. Try verifying a few times and see if results are good or inconsistent.

[sajsoni]

I tried three times and the result is always like this:

Code: [Select]

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
>
********* Image 1  *******************O
BL_IMAGE_TYPE_BIN

X
XXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOOXOOOOXXXOOOOOOOOOXOOOOXOXXOXOXXOXOXOXOXXXXOOXXXOOOOOOXXOXXOXXXXXXOOOXXXOXXOOOXXXOOOXOOXOOXXOOXOXOOOOXOXOOOOOXOOOXOOOXXXOXOXXXXXXOXXXXOOOXOOOXOXOOOOXOOOOXOXOXOOOOOOX
OOOXOOXOOOOXXXOOOOXOOXXOOXOOOOOOOOOXOXOOOXOOOOOOXOXOOOOXOXOOOOOOOXOXOXOOXOXOOOXOOOXOOXOXXOXOOOXOXXXXXOXOXXOXXXXOXOXXOOOXXOXXXXXXXOXXXXXXXOXXXXOXOXXOXOOOXXXXOXXXXXOOOXXOXX
OOXXOXXXOOXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXXXOXOOOXOXOOXOOXXXXXXXXXXXXXrom_offset=0x0.
XXImageStart = 0x80361000, ImageLength = 0x1ACB780, LaunchAddr = 0x80362000

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x1ACB780  Name="" Target=RAM
******************************************************
Valid Image at 0xd0600000
*******************************************************

********* Image 2  *******************O
BL_IMAGE_TYPE_BIN

X
XXXXOOOOXXOOOOOOOOXOXOOOOOOOOXOOOXOOOOXXXOOOOOOOOOXOOOOXOXXOXOXXOXOXOXOXXXXOOXXXOOOOOOXXRewrite recommended, internal ECC corrected data at 0x2ff1
OXXOXXXXXXOOOXXXOXXOOOXXXOOOXOOXOOXXOOXOXOOOOXOXOOOOOXOOOXOOOXXXOXOXXXXXXOXXXXOOOXOOOXOXOOOOXOOOOXOXOXOOOOOOX
OOOXOOXOOOOXXXOOOOXOOXXOOXOOOOOOOOOXOXOOOXOOOOOOXOXOOOOXOXOOOOOOOXOXOXOOXOXOOOXOOOXOOXOXXOXOOOXOXXXXXOXOXXOXXXXOXOXXOOOXXOXXXXXXXOXXXXXXXOXXXXOXOXXOXOOOXXXXOXXXXXOOOXXOXX
OOXXOXXXOOXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOOXXXXOXOOOXOXOOXOOXXXXXXXXXXXXXrom_offset=0x0.
XXImageStart = 0x80361000, ImageLength = 0x1ACB780, LaunchAddr = 0x80362000

Completed file(s):
-------------------------------------------------------------------------------
[0]: Address=0x80361000  Length=0x1ACB780  Name="" Target=RAM
******************************************************
Valid Image at 0xd1600000
*******************************************************

P500 Boot Loader Configuration :

Mac address .......... (00:03:D3:04:10:00)
Ip address ........... (192.168.1.176)
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
>


What should the partition name be when doing flash SPEar 600? I put the offered name "Partition 1" ...
Does it matter?

[TheSteve]

If the scope boots then perform a firmware update while watching the UART data. You should see it re-locate bad sectors. When you've done an update do it again and see if it relocates further bad sectors. Make sure when booting it no longer shows any issues.

[sajsoni]

I tried to do an update but I can't read the USB flash ... there is some problem with USB, this is the log when the boot is complete:

Code: [Select]

   System Physical Memory 39.680 / 73.277 MB
   Process Virtual Memory 49.500 / 1024.000 MB
-----> InfiniiVision is running <-----
will do USB phy workaround: CheckCRC

[tv84]

Didn't you already had problems in USB?

Look at your previous "successfull log":

Code: [Select]

   System Physical Memory 39.672 / 73.277 MB
   Process Virtual Memory 49.500 / 1024.000 MB
-----> InfiniiVision is running <-----
failed open \Secure\InfiniiVision\LudicrousSpeed.usb
                                                    no workaround for USB phy
After restoring the machine didn't you say that you were able to upgrade the FW?

[sajsoni]

I was able to do an update but before the incident with erasing the flash memory. Now after the flash with the complete dump a USB error occurs

[Bud]

Your photo shows the USB port is fine. Uncheck the Compatibility Mode. And use a smaller capacity USB drive or different USB drive. I've seen both messages in serial output and they were not indicative of USB access problems.