• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 97 subscribers
  • Views 355 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

UBL Start up

Loris Ciferni
Prodigy 70 points

Hi all,

we are working with a DM368 TI device in Nand boot mode and we are trying to use a MT29F16G08ABACA Micron Nand flash memory which parameters are:

– Page size x8: 4320 bytes (4096 + 224 bytes)
– Block size: 128 pages (512K + 28K bytes)
– Plane size: 2 planes x 2048 blocks per plane
– Device size: 16Gb: 4096 blocks.

At the first time we erase and program the Nand with the following commands:

sfh_DM36x.exe -v -p COM1 -nanderase

sfh_DM36x.exe -v -p COM1 -nandflash UBL_DM36x_NAND_150_432MHz.bin u-boot_alex4.bin

where the UBL was recompiled in order to meet the 432MHz PLL requirements and the u-Boot to recognize the nand device ID.

After these operations we perform the boot from nand but almost always we receive the message

DM36x initialization passed!
TI UBL Version: 1.50 - SELTA - 432MHz
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x0000001A.
Valid magicnum, 0xA1ACED66, found in block 0x0000001C.
   DONE
Jumping to entry point at 0x81080000.

 

or the following:


DM36x initialization passed!
TI UBL Version: 1.50 - SELTA - 432MHz
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000019.
Valid magicnum, 0xA1ACED66, found in block 0x0000001A.
Valid magicnum, 0xA1ACED66, found in block 0x0000001C.
   DONE
Jumping to entry point at 0x81080000.

After which the software hangs up and we have to reset the board, but we cant see the u-Boot console. It seems the UBL hasn't witten correctly the u-Boot? It seems very strange that the magic number is read several times, or not?

Is there anyone that can help us on this topic?

Thank you in advance.

Loris

  • 0 in reply to Jeff Hayes
    Prodigy 70 points

    Hi Jeff,

    thank you for your prompt reply. We have already made the suggested modifications in the past and tried them on a different nand device and the patched UBL runs correctly.
    The problem is with the already cited new Nand flash because only changing the Nand device (from the old to the newer) that we have the mentioned problem. Moreover after many and many bootstrapping operations we finally were able to assist to the u-Boot console and, in this condition, both the u-Boot and the Kernel are able to read and write the new Nand device, but the correct boot happens only sometimes.
    The hardware signals seems to be datasheet compliant and if we try to reprogram the nand device with the sfh tool we notice some bad block from the 24 programmed (we assist to the message "Verify failed"); in some cases after some erase operation with the sfh tool the u-Boot console appears.
    Could be that the UBL doesn't recognize that the device has pages of 4k? Could be the UBL doesn't correctly program and/or erase the new Nand Flash?

    Thank you for your cooperation.

    Loris