• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 100 subscribers
  • Views 776 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.

Keystone II NAND EMIF Boot

Justin Henderson
Expert 1085 points

Greetings,

I have a K2EVM and I'm using u-boot as a bootloader to get SPI NOR and NAND EMIF booting to work. I've gotten NOR booting to work very easily by building the http://arago-project.org/git/projects/u-boot-keystone.git uboot source and specifying user@host:/u-boot-keystone$make u-boot-spi.gph CROSS_COMPILE=arm-linux-gnueabi-

However, I am having difficulty getting this to work on the NAND. I am trying to put the NOR aside and just use the NAND as the bootloader, as a proof of concept. I've trying different combinations of #defines in the 6638_evm.h config header to no avail.

  • 0
    Expert 1085 points

    After loading NAND and booting with all DIP switches at 0 (NAND boot), I connect to the target and observe the PC and some register values. The PC stays around 0x00005xxx and some register values loaded are in 0x0C59xxxx. It remains here, looping.

  • 0 in reply to Justin Henderson
    TI__Guru** 116170 points

    Hi Justin,

    Sorry for the delayed response on this one. The current version of the MCSDK 3.x on K2H, doesn`t supports the NAND  boot use case due to boot issue that was discovered in PG1.0. We are currently working on the errata update to reflect this issue and will post an update when it is available.

    Thanks and Regards,

    Rahul

    due to having cache enabled during NAND boot

  • 0 in reply to Rahul Prabhu
    Mastermind 7560 points
    Hi Rahul,

    I'd like to know the latest information.

    Is there any NAND writer that support the boot issue? One of my customer is trying NAND booting on K2E.
    Could you please let me know, if you have any?

    Thank you in advance for your cooperation.
    Best regards,
    j-breeze
  • 0 in reply to j-breeze
    TI__Guru** 116170 points

    J-breeze,

    the issue discussed in the thread only applies to K2H devices. NAND boot has no known issues on K2E devices.

    If the usecase is uboot, then flashing the uboot binary to NAND is described here:

    If you don`t plan to use uboot then in mcsdk_bios, we provide a nand_writer under the directory path :

    C:\ti\mcsdk_3_1_3\mcsdk_bios_3_01_03_06\tools\writer 

    the writer is a DSP based writer project, that you can import and run from CCS. Instruction to use this for booting are provided here:

     

    Hope this helps.

    Regards,

    Rahul