| Electronics > Repair |
| Agilent 34461A corrupted flash |
| << < (28/41) > >> |
| analogRF:
I did the erase and re-write at the empty block at 0xe0000 as was suggested everything is exactly the same including the oob data looks identical to what i have at 0xc0000 which is what i saw also on my good meter i really dont think it's the NAND chip physical problem. it is still a software issue can it have something to do with those "preboot" commands/variables in the uboot? |
| analogRF:
I also have a crazy idea which may not completely solve the problem but at least might let the meter boot on its own what if I write the extracted nk.nb0 file in the nand (need to decide in what location) and then using those preboot commands I load it into memory and change the bootcmd to just start the WInce and therefore bypass the damn pboot altogether the same way that I boot it now using CEloader or YMODEM. obviously FW update will not be possible but other than that it seems it should be a solution? no? |
| ElectronMan:
--- Quote from: analogRF on July 31, 2023, 12:42:14 pm ---I also have a crazy idea which may not completely solve the problem but at least might let the meter boot on its own what if I write the extracted nk.nb0 file in the nand (need to decide in what location) and then using those preboot commands I load it into memory and change the bootcmd to just start the WInce and therefore bypass the damn pboot altogether the same way that I boot it now using CEloader or YMODEM. obviously FW update will not be possible but other than that it seems it should be a solution? no? --- End quote --- Could work in theory. Might also be worth a try to modify the default settings in that PBOOT to the correct ones, so it proceeds anyway. You could write it to a different location in flash, and load it from there via uboot, so you don't have to overwrite the current one. It is a lot smaller, and probably safer to try than decompressing the entire image. |
| analogRF:
--- Quote from: ElectronMan on July 31, 2023, 03:58:17 pm --- --- Quote from: analogRF on July 31, 2023, 12:42:14 pm ---I also have a crazy idea which may not completely solve the problem but at least might let the meter boot on its own what if I write the extracted nk.nb0 file in the nand (need to decide in what location) and then using those preboot commands I load it into memory and change the bootcmd to just start the WInce and therefore bypass the damn pboot altogether the same way that I boot it now using CEloader or YMODEM. obviously FW update will not be possible but other than that it seems it should be a solution? no? --- End quote --- Could work in theory. Might also be worth a try to modify the default settings in that PBOOT to the correct ones, so it proceeds anyway. You could write it to a different location in flash, and load it from there via uboot, so you don't have to overwrite the current one. It is a lot smaller, and probably safer to try than decompressing the entire image. --- End quote --- I thought about that first but the problem is I dont know where it gets those default values from to change them and also the first option that it follows automatically if user does not interfere is loading from 0x84000000 which leads to boot fail. I dont know where it gets that address from and what is supposed to be loaded in there (nk.bin??) and when was it supposed to be loaded there that;s when I thought I can just write the uncompressed nk.bin in NAND and load it to memory before the pboot... |
| ElectronMan:
--- Quote from: analogRF on July 31, 2023, 04:54:17 pm --- --- Quote from: ElectronMan on July 31, 2023, 03:58:17 pm --- --- Quote from: analogRF on July 31, 2023, 12:42:14 pm ---I also have a crazy idea which may not completely solve the problem but at least might let the meter boot on its own what if I write the extracted nk.nb0 file in the nand (need to decide in what location) and then using those preboot commands I load it into memory and change the bootcmd to just start the WInce and therefore bypass the damn pboot altogether the same way that I boot it now using CEloader or YMODEM. obviously FW update will not be possible but other than that it seems it should be a solution? no? --- End quote --- Could work in theory. Might also be worth a try to modify the default settings in that PBOOT to the correct ones, so it proceeds anyway. You could write it to a different location in flash, and load it from there via uboot, so you don't have to overwrite the current one. It is a lot smaller, and probably safer to try than decompressing the entire image. --- End quote --- I thought about that first but the problem is I dont know where it gets those default values from to change them and also the first option that it follows automatically if user does not interfere is loading from 0x84000000 which leads to boot fail. I dont know where it gets that address from and what is supposed to be loaded in there (nk.bin??) and when was it supposed to be loaded there that;s when I thought I can just write the uncompressed nk.bin in NAND and load it to memory before the pboot... --- End quote --- 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. |
| Navigation |
| Message Index |
| Next page |
| Previous page |