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.

C6657 FPGA update failed.

Expert 1060 points

Hi, experts.

 

I have a problem with nand boot.

When I power on the EVM with nand boot, it doesn't work.

But strange thing is the nand boot works after reset.

 

I've look through the E2E and found this thread.

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

 

As Rahul recommended I’m trying to update the FPGA version to 0.3.

But I have failed as below.

 

FPGA upgrade tool V0.3 for EVM6678, base on TI MCSDK 2.00.05.17

platform_init successfully

Enter the filename of binary (enter 'none' to skip):

C:\dsp\ccs5\mcsdk_2_01_02_06\C6657_FPGA_firmware\C6657_Gauss_EVM_FPGA_v03.bit

file size 149630 bytes

file read complete!! 149630 / 149630

00 00 0e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 10 00 00 00 00 00

00 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 00 00 00 00 80 00 00 0e 00 00 00 00 00

00 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

disable setctor proctection ok!

ID[0] = 0xff

ID[1] = 0xff

ID[2] = 0xff

ID[3] = 0xff

ID is incorrect!

 

FPGA upgate complete

 

 

FPGA upgrade tool V0.3 for EVM6678, base on TI MCSDK 2.00.05.17

platform_init successfully

Enter the filename of binary (enter 'none' to skip):

C:\dsp\ccs5\mcsdk_2_01_02_06\C6657_FPGA_firmware\C6657_Gauss_EVM_FPGA_v03.bit

file size 149630 bytes

file read complete!! 149630 / 149630

00 00 0e 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 0a 00 00 00 00 00 00 00 10 00 00 00 00 00

00 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 06 00 00 00 00 80 00 00 0e 00 00 00 00 00

00 00 06 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00

00 00 00 00 00 00 00 00

disable setctor proctection ok!

ID[0] = 0xff

ID[1] = 0xff

ID[2] = 0xff

ID[3] = 0xff

ID is incorrect!

 

FPGA upgate complete

 

 

What’s the meaning of “disable setctor proctection ok! “ message?

Please let me know to do something.

  • Jay,

    The Gauss silicon has a weakness in the ROM Boot Loader where the code does not wait sufficient time for the NAND to initialize after power on.  Therefore, when configuring the EVM for NAND Boot mode, the boot may fail.  The EVM workaround is to simply issue a button reset after it fails at power on.  This RBL issue will also be documented in the device errata document.

    You can work around this issue in your custom hardware by programming the FPGA to apply reset to the NAND device before the reset is applied to the C6657 or you need to implement a CPU reset following a POR reset so that you can Natively boot from NAND without use of an IBL on I2C EEPROM.

    I am checking with the hardware experts to see what may be the cause of the erorr you are seeing while updating the FPGA firmware and will get back to you soon.

    Regards,

    Rahul

    PS: Can you specify what version of the EVM you are using.

  • Jay,

    The update utility does not appear to be reading the bit file properly.  Is the EVM still functional or have you triied to load an invalid image?  Please re-download the bit file, re-check the path and try again.  You can also try both the v02 and v03 bit files for validation.  You must not get any error messages during the upgrade for it to succeed.

    Tom