I think you have a problem with FPGA initialization. After Net: smsc the scope tries to initialize the FPGA, and maybe failing because never even getting to it due to corrupt NOR or other reason. My this guess is also consistent with where boot stops when you trying to boot manually from USB port.
You should probably go ahead with flashing the NOR by either desoldering and using a programmer or in-place using ST Flasher Util. Normally if FPGA programming failed there is a message in the log saying this.
Ok, reloaded the FPGA code with the FPGA2000A.BIN file. Size was the same.
Now boot works like this:
Windows CE Kernel for ARM (Thumb Enabled) Built on Jun 16 2009 at 10:08:15
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 Jan 13 2011)
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
Exception 'Data Abort'(4) Thread-Id=00570002(pth=87fdd9cc) PC=8036b6fc BVA=00000
003, dwInfo = 00000001
R0=84973960 R1=000006a0 R2=815a6a60 R3=00000020
R4=00001000 R5=84973000 R6=00000004 R7=815a6a60
R8=815a6238 R9=00000000 R10=00000000 R11=00000000
R12=00000000 SP=d00afe44 Lr=8036b45c Psr=2000001f
Exception 'Data Abort'(4) Thread-Id=00570002(pth=ffffc65c) PC=8038dc10 BVA=00000
003, dwInfo = 00000001
R0=815aa520 R1=00000001 R2=ffffffff R3=815aa468
R4=03f3f000 R5=83f3f000 R6=83f3f000 R7=d00afe64
R8=d00afe60 R9=00000000 R10=00000000 R11=00000000
R12=8038db98 SP=ffffc7ac Lr=8038dbec Psr=80000013
Exception 'Data Abort' (4): Thread-Id=00570002(pth=87fdd9cc), Proc-Id=00400002(p
prc=815a8308) 'NK.EXE', VM-active=01e00002(pprc=87f53000) 'udevice.exe'
PC=8038dc10(kernel.dll+0x0001bc10) RA=8038dbec(kernel.dll+0x0001bbec) SP=ffffc7a
c, BVA=00000000
Exception 'Data Abort'(4) Thread-Id=014c0002(pth=87f76000) PC=8038fd64 BVA=00000
003, dwInfo = 00000001
R0=00000000 R1=87f76000 R2=6000001f R3=ffffc800
R4=815aa704 R5=7fff0000 R6=00000000 R7=00000000
R8=00100000 R9=d02be740 R10=d0292980 R11=00000000
R12=8038fd64 SP=d02be4e4 Lr=8038fd64 Psr=6000001f
Exception 'Data Abort'(4) Thread-Id=014c0002(pth=ffffc46c) PC=8038d5d0 BVA=00000
003, dwInfo = 00000001
R0=83f3f000 R1=00000001 R2=ffffffff R3=815aa468
R4=83f3f000 R5=00000000 R6=00000001 R7=815aa704
R8=d05726a0 R9=00000001 R10=00000004 R11=00000000
R12=8038d504 SP=ffffc5bc Lr=ffffc800 Psr=80000013
Exception 'Data Abort' (4): Thread-Id=014c0002(pth=87f76000), Proc-Id=00400002(p
prc=815a8308) 'NK.EXE', VM-active=00400002(pprc=815a8308) 'NK.EXE'
PC=8038d5d0(kernel.dll+0x0001b5d0) RA=ffffc800(
+0xffffc800) SP=ffffc5bc, BVA=
00000000
Exception 'Data Abort'(4) Thread-Id=00f30006(pth=8694a9e4) PC=8038fd64 BVA=00000
003, dwInfo = 00000001
R0=00000000 R1=8694a9e4 R2=6000001f R3=ffffc800
R4=815aa704 R5=7fff0000 R6=00000001 R7=0000fffe
R8=00000001 R9=002a0000 R10=00000000 R11=00000000
R12=8038fd64 SP=d072fe20 Lr=8038fd64 Psr=6000001f
Exception 'Data Abort'(4) Thread-Id=00f30006(pth=ffffc27c) PC=8038d5d0 BVA=00000
003, dwInfo = 00000001
R0=83f3f000 R1=00000001 R2=ffffffff R3=815aa468
R4=83f3f000 R5=00000000 R6=00000001 R7=815aa704
R8=00000000 R9=00000001 R10=00000000 R11=00000000
R12=8038d504 SP=ffffc3cc Lr=ffffc800 Psr=80000013
Exception 'Data Abort' (4): Thread-Id=00f30006(pth=8694a9e4), Proc-Id=00400002(p
prc=815a8308) 'NK.EXE', VM-active=00400002(pprc=815a8308) 'NK.EXE'
PC=8038d5d0(kernel.dll+0x0001b5d0) RA=ffffc800(
+0xffffc800) SP=ffffc3cc, BVA=
00000000
I *STILL* cannot boot automatically. If I turn off and on the scope, the same happens:
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
Then, if I go to the USB serial channel and type BOOT, the boot starts and stops on these lots of exception errors.
Did I went forward?
Thanks you all for all the support, recovering this scope is VERY important to me