Electronics > Repair
Agilent 34461A corrupted flash
<< < (12/41) > >>
analogRF:

--- Quote from: tv84 on July 30, 2023, 10:52:37 am ---@ElectronMan or @TheSteve might give you a hand here.

--- End quote ---
I hope they come here and have a look

FWIW here is the .bin file of the P-Boot taken from my good 34461A and it is identical to the one from the bad meter
and also identical to those posted earlier in this thread by others
I am not able to figure out where it is getting its boot parameters from. Certainly not from the environment variables
because they are ok. Unless there is another hidden copy of them which is bad?
ElectronMan:

--- Quote from: analogRF on July 30, 2023, 12:29:28 pm ---
--- Quote from: tv84 on July 30, 2023, 10:52:37 am ---@ElectronMan or @TheSteve might give you a hand here.

--- End quote ---
I hope they come here and have a look

FWIW here is the .bin file of the P-Boot taken from my good 34461A and it is identical to the one from the bad meter
and also identical to those posted earlier in this thread by others
I am not able to figure out where it is getting its boot parameters from. Certainly not from the environment variables
because they are ok. Unless there is another hidden copy of them which is bad?

--- End quote ---

This looks like a problem with the CE bootloader (the stage after Uboot) or the flash. It could be that part of the NAND flash is completely unusable.

Do you happen to have the output when updating firmware? Are there any errors while writing the image?
analogRF:

--- Quote from: ElectronMan on July 30, 2023, 04:05:51 pm ---
--- Quote from: analogRF on July 30, 2023, 12:29:28 pm ---
--- Quote from: tv84 on July 30, 2023, 10:52:37 am ---@ElectronMan or @TheSteve might give you a hand here.

--- End quote ---
I hope they come here and have a look

FWIW here is the .bin file of the P-Boot taken from my good 34461A and it is identical to the one from the bad meter
and also identical to those posted earlier in this thread by others
I am not able to figure out where it is getting its boot parameters from. Certainly not from the environment variables
because they are ok. Unless there is another hidden copy of them which is bad?

--- End quote ---

This looks like a problem with the CE bootloader (the stage after Uboot) or the flash. It could be that part of the NAND flash is completely unusable.

Do you happen to have the output when updating firmware? Are there any errors while writing the image?

--- End quote ---

yes the bootloader is reading wrong parameters (image address, mac address, ...are all wrong)
when the unit was updating FW the UART was connected but there were no messages.

as far as I can tell the part of FW update that finished was just copying the Nk.bin (original from the FW pack) into d0620000 and I can see it is there and seems to be correct. But I guess the FW will also do some stuff after rebooting the unit however in this case it does not get there because on the reboot, it reads the wrong addresses and fails to boot.
 
ElectronMan:

--- Quote from: analogRF on July 30, 2023, 04:11:50 pm ---
--- Quote from: ElectronMan on July 30, 2023, 04:05:51 pm ---
--- Quote from: analogRF on July 30, 2023, 12:29:28 pm ---
--- Quote from: tv84 on July 30, 2023, 10:52:37 am ---@ElectronMan or @TheSteve might give you a hand here.

--- End quote ---
I hope they come here and have a look

FWIW here is the .bin file of the P-Boot taken from my good 34461A and it is identical to the one from the bad meter
and also identical to those posted earlier in this thread by others
I am not able to figure out where it is getting its boot parameters from. Certainly not from the environment variables
because they are ok. Unless there is another hidden copy of them which is bad?

--- End quote ---

This looks like a problem with the CE bootloader (the stage after Uboot) or the flash. It could be that part of the NAND flash is completely unusable.

Do you happen to have the output when updating firmware? Are there any errors while writing the image?

--- End quote ---

yes the bootloader is reading wrong parameters (image address, mac address, ...are all wrong)
when the unit was updating FW the UART was connected but there were no messages.

as far as I can tell the part of FW update that finished was just copying the Nk.bin (original from the FW pack) into d0620000 and I can see it is there and seems to be correct. But I guess the FW will also do some stuff after rebooting the unit however in this case it does not get there because on the reboot, it reads the wrong addresses and fails to boot.

--- End quote ---

Yeah, it looks like it loads those parameters from a location that it can't read right now, so loads those incorrect settings instead.:

--- Code: ---CRC does not match for NAND AFFF475B F381A23
ERROR : Bootloader setting load failed
INFO : Loading default bootloader settings
--- End code ---

I am trying to locate this config information
analogRF:
what is interesting is that earlier in the thread where @dc101 had very similar issue as mine, he also reported the pboot is thinking image addresses are d0400000 and d1700000 exactly like my unit! :-// :-//
I have also seen a similar issue in some broken 3000A scopes that also reported image address at d0400000 which again wrong for those scopes.
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