• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 96 subscribers
  • Views 352 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.

Problems with u-boot in DVSDK 4.02 for dm368

dm368 user100948
Prodigy 50 points

After flashing the UBL and u-boot that comes with the ti-dvsdk_dm368-evm_4_02_00_06 package, the u-boot doesn't have the "mii" command.

This command was in previous u-boot versions (that came with previous versions of the dm365 dvsdk), and I need it.

Why was the command removed? Can I bring it back? Is there another command that replaces it?

If not, can I use the u-boot from a previous dvsdk version and the rest from this (latest) dvsdk?

---

Another problem of this new u-boot is that I get a lot of the following messages at boot time, and it takes about 20 seconds to print them all:

nand_read_bbt: Bad block at 0x000001000000
nand_read_bbt: Bad block at 0x000001020000
nand_read_bbt: Bad block at 0x000001040000

...

...

nand_read_bbt: Bad block at 0x00004f280000

Thanks.

  • 0
    Prodigy 50 points

    I just did a little more testing and the problems I mentioned also exist in dvsdk 4.01, but not in dvsdk 4.00 and dvsdk 2.

    Also, I've noticed the u-boot bin file of dvsdk 4.01 (u-boot-dm368-evm-2010.12-rc2-psp03.01.01.38-r2.bin) is more than twice the size of the u-boot bin file of dvsdk 4.00 (u-boot-dm365-evm-2009.05+2009.06-rc0-psp03.01.00.37-r1.bin).

  • 0 in reply to dm368 user100948
    Prodigy 50 points

    The lack of the mii command is less important for me now.

    Apparently, it's not just printing the bad blocks messages for nothing - it actually marks almost all of the nand blocks as bad!

    I had to use the "nand scrub" command to delete the bad blocks, but now the real factory bad blocks are also deleted.

    1. Why is the u-boot doing this and how can I prevent it?

    2. Can I use dvsdk 4.02 with the u-boot from dvsdk 4.00 without any problem later on?

    3. Is there a way to check the nand for real bad blocks after using "nand scrub"?