| Electronics > Repair |
| Agilent 34461A corrupted flash |
| << < (29/41) > >> |
| analogRF:
--- Quote from: ElectronMan on July 31, 2023, 05:01:56 pm --- It gets the 0xd0400000 and 0xd1700000 and 0x84000000 addresses from defaults it loads in the binary. I PMed you a copy of the xloader you can try, where I changed the defaults to the correct ones. This is normally in flash @0x320000 but I would recommend writing it somewhere empty and then: nand read 0x600000 <New Address> 0x10000;bootm 0x600000 to boot and test it. --- End quote --- Thanks :-+ looks very promising. I'll try that. I will write it somewhere maybe after the current one in the nand or I can write it at that 0xe0000 no? it's empty |
| ElectronMan:
--- Quote from: analogRF on July 31, 2023, 05:06:55 pm --- --- Quote from: ElectronMan on July 31, 2023, 05:01:56 pm --- It gets the 0xd0400000 and 0xd1700000 and 0x84000000 addresses from defaults it loads in the binary. I PMed you a copy of the xloader you can try, where I changed the defaults to the correct ones. This is normally in flash @0x320000 but I would recommend writing it somewhere empty and then: nand read 0x600000 <New Address> 0x10000;bootm 0x600000 to boot and test it. --- End quote --- Thanks :-+ looks very promising. I'll try that. I will write it somewhere maybe after the current one in the nand or I can write it at that 0xe0000 no? it's empty --- End quote --- Yes, that should work. |
| analogRF:
I uploaded the modified pboot into NAND at 0xe0000 (after erasing and made sure it is all 0xFF before writing) and then loaded from there into memory at 0x600000 and issued bootm 0x600000 pboot ran exactly the same way it used to and stopped after all those error messages when I press space bar to enter the bootloader menu, Now I get the correct addresses 0xd0620000 and 0xd2120000 for image locations however when I choose any of them, the unit simply says "loading image 1 from memory at 0xd0620000" and stops there and hangs I know there is a Nk.bin (compressed exactly as it is in the firmware package) at d0620000 and d2120000 and it is the same on my good meter. it seems pboot cannot read the nand or it cannot decompress the XPRS Nk.bin so it hangs in there |
| analogRF:
it seems the only way is to bypass the pboot by writing the extracted nk.nb0 directly and using the "go" command but I will give that JTAG a try and see if you guys can decipher anything from memory content |
| ElectronMan:
--- Quote from: analogRF on July 31, 2023, 07:15:48 pm ---I uploaded the modified pboot into NAND at 0xe0000 (after erasing and made sure it is all 0xFF before writing) and then loaded from there into memory at 0x600000 and issued bootm 0x600000 pboot ran exactly the same way it used to and stopped after all those error messages when I press space bar to enter the bootloader menu, Now I get the correct addresses 0xd0620000 and 0xd2120000 for image locations however when I choose any of them, the unit simply says "loading image 1 from memory at 0xd0620000" and stops there and hangs I know there is a Nk.bin (compressed exactly as it is in the firmware package) at d0620000 and d2120000 and it is the same on my good meter. --- End quote --- So, this uses the same exact function to verify block status when loading the nkbin as it uses when trying to read the uboot configuration. It may be failing that part too. It is also possible I missed something. Either way, we can rule out a bad copy of the xloader as the cause, if you are still seeing the same block defects showing up. Theoretically I could nix the part of that binary that does the bad block check, but that's not a good idea long-term. If you manage to get connected via JTAG, we can query the flash chip to make sure it is outputting the correct parameters. The flash chips in these devices are not natively supported by the PBOOT, they are supported by OFNI-standard parameters read from the chip. If something is bad there, it could cause what we're seeing. |
| Navigation |
| Message Index |
| Next page |
| Previous page |