• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 98 subscribers
  • Views 597 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.

RBL can not find UBL

Rain Peng
Intellectual 620 points

Hi All,

I am using DM6441 for custom board. I have tested DDR2, NAND flash, UART using JTAG and CCS3.3, and all these tests are passed.

So I change NANDWrite project to write UBL and Uboot into NAND flash via CCS3.3, it passed too.

But when I start the board, it still outputs "BOOTME BOOTME".  I have also tried to use the same UBL and Uboot which customed for DM6441 to reflash DM6441EVM board, the DM6441EVM board can boot up. DM6446EVM shows:

DM6441 initialization passed!
TI UBL Version: 1.50
Booting Catalog Boot Loader
BootMode = NAND
Starting NAND Copy...
Valid magicnum, 0xA1ACED66, found in block 0x00000006.
   DONE
Jumping to entry point at 0x81080000.


U-Boot 1.2.0 (Jun 13 2010 - 00:36:49)

I2C:   ready
DRAM:  256 MB
unknown vendor=0 Flash:  0 kB
*** Warning - bad CRC, using default environment

In:    serial
Out:   serial
Err:   serial
ARM Clock :- 256MHz
DDR Clock :- 162MHz
MSP430 Firmware supports AM/PM Feature
Hit any key to stop autoboot:  0

The differences between DM6446EVM board and our custom board are CPU and Nand flash, our Nandflash is K9K1G08B0B.

I also checked the boot mode, the COUT[0-3] is 0000, YOUT[0-4] is 00000.

Now I have no idea about this. Why does it always output "BOOTME"?

Can anyone help me on this issue?

Thanks,

Rain

  • 0
    TI__Expert 5170 points

    Rain,

    "BOOTME" messages appear whevever the board resets. May be the UBL/U-Boot image is causing the board to reset.

    Regards, Sudhakar

  • 0 in reply to Sudhakar Rajashekhara
    Intellectual 620 points

    Sudhakar,

    Thanks for your reply.

    I have tested the UBL/Uboot on DM6446 evm board, they are working, so I don't think they caused the board to reset.

    I have double checked the data that written in Nand, both the data and ECC are right.

    The problem seems that UBL is never executed, maybe RBL even doesn't find the UBL.

    I have no idea now.

    By the way, I saw the schematic of DM6446EVM board, the RN28 shows NO-POP, which means that when I select Nand boot mode, the COUT[0-4] are hung in the air, why?  In my custom board, I pull them low by connecting 10k resistances. Is it right? or I need to remove these resistances to let them hang in the air?

    Best regards,

    Rain

  • 0 in reply to Rain Peng
    Intellectual 620 points

    I just boot my board in the below way:

    First I use CCS to burn uboot to nand flash, then I use slh_DM644x.exe to load ubl to IRAM, in this case, I can get u-boot up.

    so both the ubl and uboot code are maybe right, and ubl can find uboot in nand flash and can boot uboot. So now the problem is RBL can not read and copy ubl to RAM and start UBL.

    Does anyone have ideas?

    Best regards,

    Rain

  • 0 in reply to Rain Peng
    TI__Expert 5170 points

    Rain,

    I think there is some problem with the NAND Writer you are using. NAND writer may be writing the UBL to some offset but RBL is looking at some other offset for UBL. When you are using slh_DM644x.exe, it is writing the UBL to proper offset where RBL will look for. Modifying your NAND writer should solve the issue for you.

    Regards, Sudhakar

  • 0 in reply to Sudhakar Rajashekhara
    Intellectual 620 points

    Sudhakar,

    NAND writer can work on DM6446EVM board, and the uboot is also written by NAND writer, so I think the NAND writer program maybe is right.

    I know the reason that our HW engineer made a mistake. he chose a nandflash that RBL didn't support. its device ID is not in the RBL table.

    Thanks,

    Rain