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.

Linux/TDA2EVM5777: What should I do if I want change the SD boot to nor flash boot ? The ROM code will not run? I am using the TDA2x EVM.

Part Number: TDA2EVM5777

Tool/software: Linux

HI, this is the sysboot description:

What should I do if I want change the SD boot to nor flash boot?

  • Hi Lucas,

    Please follow the subsequent tables, most important of them:

    Table 29-5. MMC2 Configuration (SR2.0)(1)

    Table 29-6. GPMC for XIP/NAND Configuration

    and

    Table 29-9. Booting Devices Order

    to enable NOR (XIP) flash boot.

    Regards,

    Stan

  • Hi, Stan
    I have the XDS100v2 . Could I use the CCS7 to load the uboot.bin from VSDK(03.00.00)? How to load the uboot.bin? And what address to load? 0x0000 0000? What could I do in details?
    Regards,
    Lucas
  • Hi Lucas,

    I'm copying here the contents from the TRM about XIP boot. I think loading uboot to 0x0800 000 and setting proper sysboot pins should be enough.

    32.3.7.3 XIP Memory
    The ROM code can boot directly from XIP devices, such as NOR flash memories, that have the following
    characteristics:
    • The GPMC is the communication interface.
    • Memories up to 1Gibit (128MiB) can be connected.
    • 8-bit or 16-bit data bus width, configured through sysboot[13] (=1 for 16-bit)
    • Non-muxed or address/data multiplexed mode, configured through sysboot[12:11] (=0x1 for A/D mux)
    • The GPMC clock is 133 MHz.
    • The device is connected to CS0 mapped to address 0x0800 0000.
    • The wait pin gpmc_wait0 signal is monitored according to the sysboot[10] configuration pin (=1 is
    enabled)
    • For an XIP memory booting, no user intervention is required; the following debugging steps are
    described. Only the CH, which is not mandatory, lets users change clock settings and GPMC
    parameters. Failure in CH copying causes a return to the main booting procedure, which selects the
    next device for booting.


    Booting from an XIP device consists of the following ROM code steps:

    1. Configure the GPMC for XIP device access.
    2. Verify that the CH is present at address 0x0800 0000. If the CH is present, copy the entire sector (512
    bytes) to internal RAM and execute the CH.
    3. Set the image location:
    • 0x0800 0000 if the CH is not found
    • 0x0800 0200 if the CH is found
    4. Verify that a bootable image is at the image location.
    5. If the image is found, execute it.
    6. If the image is not found, return from XIP booting to the main booting loop.

  • Hi.
    But what should I use to download the uboot.bin to the norflash? CCS? Or other softwares. How to download it in detail?

    Regards,
    Lucas
  • Vision SDK binaries can be build from the source files. There is also a ready binary only download. You load them through CCS. Download link here: www.ti.com/.../PROCESSOR-SDK-TDAX

    thanks
    Alex
  • Hi, Alex

    Is "load program" correct? But I can not  the address of download! Do you have some files about download .bin files?

  • Lucas,

    You really need get to know the Vision SDK, we cannot explain or comment every possible step you need to do here. Please start with the initial user guide, everything is explained there.

    Thanks
    Alex
  • Lucas,

    NOR flashing procedure can also be found in SBL user guide (path below). It's for TI-RTOS but you can still take it as reference.

    \PROCESSOR_SDK_VISION_03_01_00_00\ti_components\drivers\pdk_01_08_00_16\packages\ti\boot\sbl_auto\docs\SBL_UserGuide.pdf

    For Linux related questions, you can refer Processor SDK Linux Automotive. But I don't see NOR boot is supported.

    http://processors.wiki.ti.com/index.php?title=Processor_SDK_Linux_Automotive_Software_Developers_Guide#Booting_EVM_with_different_modes

    Best Regards,