Only change bootdelay and pbootdelay to ,say, 3, but only in the env var section 0x00040000 - 0x00043FFF. Do not change anything before 0x00040000.
U-Boot 2010.03 (Oct 18 2011 - 14:28:06)Agilent P500
CPU: SPEAr600
DRAM: 128 MiB
Flash: 512 KiB
NAND: internal ecc 128 MiB
U-Boot 2010.03 (Oct 18 2011 - 14:28:06)Agilent P500
CPU: SPEAr600
DRAM: 128 MiB
Unknown id: 0x13409d. Using ST_M23P40
Flash: 64 KiB
NAND: internal ecc 128 MiB
U-Boot 2010.03 (Oct 18 2011 - 14:28:06)Agilent P500
CPU: SPEAr600
DRAM: 128 MiB
Flash: 512 KiB
NAND: internal ecc 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: 4 0 3
p500>
## 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: 2024-20-12 6:103:32.30 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
Press [ENTER] to launch image stored in flash or [SPACE] to cancel.
Initiating image launch in 3 seconds 2 seconds 1 seconds
P500 Boot Loader Configuration :
Mac address .......... (00:30:D3:20:D7:70)
Ip address ........... (192.168.1.212)
Subnet Mask address .. (255.255.255.0)
DHCP ................. (Enabled)
Boot delay (seconds).. (3)
Load image 1 at startup
Image addresses. (0xdxxxxxxx for NAND, 0x8xxxxxxx for RAM)
1 (0xd0600000)
2 (0xd1e00000)
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
Hold on a sec. This was your log in your reply #985:Code: [Select]U-Boot 2010.03 (Oct 18 2011 - 14:28:06)Agilent P500
CPU: SPEAr600
DRAM: 128 MiB
Flash: 512 KiB
NAND: internal ecc 128 MiB
Now you are not getting NOR identified:Code: [Select]U-Boot 2010.03 (Oct 18 2011 - 14:28:06)Agilent P500
CPU: SPEAr600
DRAM: 128 MiB
Unknown id: 0x13409d. Using ST_M23P40
Flash: 64 KiB
NAND: internal ecc 128 MiB
What is going on here?
Ok. Yes you have to use a proper chip, all sort of funny things may be happening with Uboot making its guesses.
U-Boot 2010.03 (Oct 18 2011 - 14:28:06)Agilent P500
CPU: SPEAr600
DRAM: 128 MiB
Flash: 512 KiB
NAND: internal ecc 128 MiB
Debug serial initialized ........OK
RTC: 2024-19-6 3:84:41.49 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
PHY not found.
Press [ENTER] to launch image stored in flash or [SPACE] to cancel.
Initiating image launch in 3 seconds
P500 Boot Loader Configuration :
Mac address .......... (00:03:D3:04:10:00)
Ip address ........... (192.168.1.100)
Subnet Mask address .. (255.255.255.0)
DHCP ................. (Enabled)
Boot delay (seconds).. (3)
Load image 1 at startup
Image addresses. (0xdxxxxxxx for NAND, 0x8xxxxxxx for RAM)
1 (0xd0600000)
2 (0xd1e00000)
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
>
I guess you could attach the NOR bin dump for us to take a look.
I guess you could attach the NOR bin dump for us to take a look.
Oh sure, here it is. Though, the forum doesn't seem to like files ending with .bin, so I renamed it .bin.py
edit:
looks like the attachment messed up anyways, 1sec, I'll upload it to my VPS to make a download link
I guess you could attach the NOR bin dump for us to take a look.
Oh sure, here it is. Though, the forum doesn't seem to like files ending with .bin, so I renamed it .bin.py
edit:
looks like the attachment messed up anyways, 1sec, I'll upload it to my VPS to make a download linkJust add a .txt extension and it will upload here. Then mention to remove the .txt extension.
You were talking about using JTAG at some point. Did you do anything to enable JTAG ? If so, you'd need to roll that back if want to boot from NOR.
You have to change this variable value. Note the Offset.
Do not forget to update the checksum.
You have to change this variable value. Note the Offset.
Do not forget to update the checksum.
<p500> crc 0xf8000000 0x80000
CRC32 for f8000000 ... f807ffff ==> c7bc2d68
which matches what I get on my desktop:> cat bootdelay.bin | crc32
c7bc2d68
U-Boot 2010.03 (Oct 18 2011 - 14:28:06)Agilent P500
CPU: SPEAr600
DRAM: 128 MiB
Flash: 512 KiB
NAND: internal ecc 128 MiB
Debug serial initialized ........OK
RTC: 2024-19-6 6:85:19.21 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
PHY not found.
P500 Boot Loader Configuration :
Mac address .......... (00:03:D3:04:10:00)
Ip address ........... (192.168.1.100)
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 (0xd1e00000)
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
>
Great. So your jorney is a demonstration that Keysight 1000x scopes can be restored even if the firmware was completely gone. Pretty impressive.