This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
hi all:
I am using uart boot to flash the UBL and Uboot to Nand, type is K9F1G08U0B, I have another board ,which is based on DM355, and it works fine.
But it seems that K9F1G08U0B cannot work on DM365, From the console I saw sfh_DM36x.exe successfully wrote data to flash, but when I change the boot mode pin to NAND Boot, it has nothing from console.
Any advice?
hi, constantine.
I have read sprufg5a.pdf, in page176, indeed DM365 support device ID"0xF1", which is the K9F1G08U0B's ID.
I met such problem before when I used DM355, it's the reason of "CE Don't care". when using DM355, we need a "CE don't care" NAND Chip, although TI said it support device ID which is not "CE don't care"(for example K9F1208), we DO not known how TI test and publish the datasheet.
K9F1G08U0B is a "CE don't care" NAND Chip from SAMSUNG, device id is "0xF1", but DM365 cannot boot normally. has someone tried?
I also use slh_DM36x.exe to download uboot to DDR2, and uboot can read/write K9F1G08 correctly, it seems not the PCB problem.
no one used?
someone verify K9F1G08U0B on DM368 platform:
http://processors.wiki.ti.com/index.php/List_of_NANDs_devices_supported_by_TI_RBLs
but not on DM365 EVM.
Josef, have you used that part?
Can you provide the Revision ID for the working DM355 and the non-working DM365. To determine the Rev ID look at the top the device and see what value of x is
DM365xZCE30
sorry for replying late.
there is no "x" in the Revision ID, I think it's the 1.2 version.