Electronics > Repair
Agilent 34461A corrupted flash
<< < (20/41) > >>
analogRF:
"nand bad" shows no bad blocks
analogRF:

--- Quote from: ElectronMan on July 30, 2023, 09:14:00 pm ---

From what I can see in the uboot help, the commands should be similar to the read command.

Have you tried the "nand bad" command to see if any bad blocks are known?

You could also try writing this to the NEXT block assuming it is completely blank already. If you noticed during bootup, it does try the next block all the way to the end of flash.

--- End quote ---

the errors in the log start from

--- Code: ---Reading NAND configuration
FMD_DirectRead: Invalid block at sector 0x180 bumping by 0x40 sectors
FMD_DirectRead: Invalid block at sector 0x1c0 bumping by 0x40 sectors
FMD_DirectRead: Invalid block at sector 0x200 bumping by 0x40 sectors
FMD_DirectRead: Invalid block at sector 0x240 bumping by 0x40 sectors
--- End code ---

and it keeps bumping by 0x40 sectors whatever that means until the last error which is

--- Code: ---FMD_DirectRead: Invalid block at sector 0xff80 bumping by 0x40 sectors
FMD_DirectRead: Invalid block at sector 0xffc0 bumping by 0x40 sectors
--- End code ---

how is sector related to page? how long is it?

"nand info" commands says "sector size 128 KiB" but seems way too large to me
ElectronMan:

--- Quote from: analogRF on July 30, 2023, 09:32:50 pm ---
--- Quote from: ElectronMan on July 30, 2023, 09:14:00 pm ---

From what I can see in the uboot help, the commands should be similar to the read command.

Have you tried the "nand bad" command to see if any bad blocks are known?

You could also try writing this to the NEXT block assuming it is completely blank already. If you noticed during bootup, it does try the next block all the way to the end of flash.

--- End quote ---



the errors in the log start from

--- Code: ---Reading NAND configuration
FMD_DirectRead: Invalid block at sector 0x180 bumping by 0x40 sectors
FMD_DirectRead: Invalid block at sector 0x1c0 bumping by 0x40 sectors
FMD_DirectRead: Invalid block at sector 0x200 bumping by 0x40 sectors
FMD_DirectRead: Invalid block at sector 0x240 bumping by 0x40 sectors
--- End code ---

and it keeps bumping by 0x40 sectors whatever that means until the last error which is

--- Code: ---FMD_DirectRead: Invalid block at sector 0xff80 bumping by 0x40 sectors
FMD_DirectRead: Invalid block at sector 0xffc0 bumping by 0x40 sectors
--- End code ---

how is sector related to page? how long is it?

"nand info" commands says "sector size 128 KiB" but seems way too large to me

--- End quote ---
They are using sector size = 2048 bytes, so the same thing as a page. Multiply that # by 2048 to get offset.
It is effectively starting from c0000 and going to the end of flash.
ElectronMan:
So I just tested this from uboot, which reads out the page, and places it in the next block (the next block was empty in mine).

It seems to work without any issue for me. But YMMV.

The MD was just to check that memory area was mostly empty.

--- Code: ---md 0x800000 0x20000
nand read 0x800000 0xc0000 0x20000
nand write 0x800000 0xe0000 0x20000
--- End code ---
analogRF:

--- Quote from: ElectronMan on July 30, 2023, 09:39:42 pm ---

They are using sector size = 2048 bytes, so the same thing as a page. Multiply that # by 2048 to get offset.
It is effectively starting from c0000 and going to the end of flash.

--- End quote ---

yes I just figured that out but it is strange because when the unit boots
I am 100% it reads a lot from the flash and never complains for example about cal data being corrupted etc...
cannot be bad all the way to 128MB

I was just looking at the dumps of some random pages after 0xC0800 and they are all 00 (with identical oob data which has 4 rows of data and 4 rows of FF alternating) until 0xC4000 when all data become FF including all the oob and that continues for very long length....

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