flash_utils error while writing nand flash(K9F1208)

it seems the number of block is not corrent.

for K9F1208, it has 4096 blocks, but the erasing function just found 0x31 blocks. i should check the sft code :(

it's really very strange.

Liu,

From the logs it appears that the flash_utils is not able to talk to NAND.

The first step is to make sure that the NAND is supported. Can you please refer to Section 11.2.1.2 (http://focus.ti.com/lit/ug/sprufb3/sprufb3.pdf) to confirm if this NAND is supported by ROM bootloader (RBL).

The latest version of flash_utils works for the NANDs supported by RBL. What is the version of the flash_utils you are using. From where is it downloaded?

Can you provide details about the NAND and I can help you identify if the NAND is supported:
1. Part no.
2. Device ID, Page size, Block size, Address cycles (from the datasheet)

Thanks,
Gaurav

hi,Gaurav:

Liu,

Device ID 0x76 indicates the following (Section 11.2.1.2, ARM SS guide) about the NAND geometry:

Number of pages per block:32
Page size:512+16
Block Shift value:13
Address cycles: 4

If this information matches with the information in the datasheet, then the NAND is supported.
In that case, the next step is to verify the hardware connection on the board. All the required pins should be connected properly.

The block is declared BAD by the flash utility if:
1. The block is marked BAD, or
2. The read (after write) doesn't return the expected data (which was written).

Please use debug techniques (printf etc in flash utility) to figure out if the problem is 1 or 2. If the problem is 2, and given that the NAND is supported, the problem is likely to be with the layout/hardware connection.

I would like to also suggest trying mutiple NANDs (in case one particualr NAND is BAD). Also if you have access to DM35x socketed EVM, you can try the NAND on the EVM.

Thanks,
Gaurav

hi,Gaurav .

the K9F1208 is support by the SFH. and now it has no connection with RBL. I use SFT to erase and write NAND flash.

From SFT, i printf something. The SFT can recognize the flash ID and params. Most important is , the ID I printf through UART is correct.(the SFT will first recognize nand flash ID ,and determine it's timing. So sending cmd and address and reading data will be not a hardware problem.)

I use the command: sfh.exe -nanderase , and it operates successfully.

but everytime after i wirte the data(not 0xff) to the page , and i read it, the 0xFF will return :( .

I checked the hardware connection, and it is OK (every nand signal is valid).

So i think it is the software problem.

I reconfigure the A1CR register:

AEMIF->A1CR = (1<<30)|

finally ,it does not work as before.

"The CE input is the device selection control. When CE goes high during a read operation the device is returned to standby mode." This is from K9F1208 Datasheet. Tie CE to ground and try again. Had this problem with K9F5608. But remember, as long as CE is low, the nand device is active and will occupy the EMIF.

Thanks Josef.

Liu,

Is your issue resolved?

Regards,
Gaurav

Josef Kohler said:

"The CE input is the device selection control. When CE goes high during a read operation the device is returned to standby mode." This is from K9F1208 Datasheet. Tie CE to ground and try again. Had this problem with K9F5608. But remember, as long as CE is low, the nand device is active and will occupy the EMIF.

I really appreciate Josef.

It is really the damn reason of CE pin. why nobody fix the error? s-h-i-t!

Thank you both for helping me . In this situation, will the DM355 boot stably ?

well ,that is a terrible news.

1GBit is too expensive for my application .i checked APPRO's DM355_IPNC solution, and found it also used K9F5608 :)

datasheet said it support device id "0x76", could you recommend a cheap one for me ? 

K9F5608 has same problem with CE-dont-care. Appro drives CE pin with GPIO. The other problem of K9F5608, production will exprie within this year. If device cost is realy that critical in your applicatin, i think you are going to sell many systems. In this case talk to Samsung Semiconductor, perhaps you get access to FPGA NAND.

thanks.

Now i am tracing u-boot, it will restart sometimes. I have drive CS0 to low as a GPIO. when it runs to nand_scan(), the uart has no response anymore. Don't know why yet.

Hi,

Could it be the GPIO pin used to drive the CS low one of the UART pins? Would you double check?

Thanks.