• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 102 subscribers
  • Views 576 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

Have you ever seen succeed of EMIF16 boot in C665x?

RY9983
Guru 10570 points


Hello,
I am evaluating EMIF16 boot using TMDXEVM6657LS.

I understand that EMIF16 boot just set Program counter as 0x70000000.
And, I put there the code like following to expect loop forever.
But, I have never seen PC at the 0x70000000.


Question:

- Have you ever seen succeed of EMIF16 boot in C665x?

- Is there any restriction to evaluate EMIF16 boot by TMDXEVM6657LS ?

BTW,
- Have you ever seen succeed of NAND flash boot in C665x?
(Because, I need to consider other method to boot up if EMIF16 boot has some restrictions.)

Best regards, RY

  • 0
    TI__Guru** 114410 points

    Hi RY,

    Yes, EMIF16 boot has been validated on the EVM and we have have customers who have also been able to get this working on custom boards so we don`t expect any issues with this boot mode. Can you please provide the value of DEVSTAT after you configure EMIF16 boot. You may want to consider the tips on EMIF16 boot that are given on the thread below :

    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/t/367102.aspx 

    There are no restrictions to evaluate EMIF16 boot on the EVM. We don`t have a NOR flash on the C6657 EVM on the C6657 port so you can`t try booting form NOR flash connected to EMIF16 but we do have a NAND connected to the EVM. Details of NAND flash are provided here with an example.

    http://e2e.ti.com/support/dsp/c6000_multi-core_dsps/f/639/p/335996/1177713.aspx#1177713

    Regards,

    Rahul

  • 0 in reply to Rahul Prabhu
    Guru 10570 points

    Rahul-san,
    I am very grateful to the valuable advice.

    I accomplished the NAND boot with your example.
    And, FPGA firmware update from V2 to V3 made me the result to jumping the program counter to 0x70000000 with NOR boot configuration.
    I attach the capture image.  (I don't connect the NOR flash daughter board in the exam below.) 

    Question:

    I think there is any restriction in C6657EVM with FPGA firmware V2.
    Do you know the detail of FPGA firmware update?

    Answer:

    Rahul Prabhu said:
    Can you please provide the value of DEVSTAT after you configure EMIF16 boot.

    DEVSTAT is 0x00001A41.  Thanks.

    Best regards, RY

  • 0 in reply to RY9983
    TI__Guru** 114410 points

    the FPGA firmware is released by the board manufacturer so I don`t have the complete details. Also I tried to find the release documentation but could find the complete chnage log. I am chekcing with our hardware team to see if they have these details.

  • 0 in reply to Rahul Prabhu
    Guru 10570 points

    Rahul-san

    Thank you so much for your support!
    I found FPGA firmware in eInfo chips site. Sorry for my not enough pre-searching.

    I read the EVM's TRM. But, there is no directions to update FPGA firmware.
    Since there is no detail about reason to update it, I can not understand why the DSP boot succeed by FPGA firmware update.

    Do you know below?
    - What is firmware v02 for?

    - What is the meaning of FPGA firmware update as for NAND boot?

    I would like to confirm that FPGA firmware version depends on all the causing.
    And, I would like to confirm it is true that C665x have no restriction to boot from EMIF16 boot.

    Best regards, RY

  • 0 in reply to RY9983
    TI__Guru** 114410 points

    The Gauss EVM comes with a secondary bootloadxer (IBL) that is written on the I2C EEPROM that is on the EVM. The FPGA firmware v2 forces the device to execute the IBL before it can execute any other code. This is a requiremnt for most of the Out of box demos on the EVM.

    Firmware upgrade to v03 allows user to bypass the IBL and boot natively from the boot media using the Rom code on the device.

  • 0 in reply to Rahul Prabhu
    Guru 10570 points

    Rahul-san,

    Thanks for your comment!!
    I understand the mechanism below.

    Is my understanding correct?

    Best regards, RY

  • 0 in reply to RY9983
    TI__Guru** 114410 points

    Yes, your understanding is correct.