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.

C6678 Hyperlink Boot Issue

Hi Team,

my customer has a following issue:

-          Customer has two EVMs connected with the Hyperlink cable

-          On the first board there runs the TI demo for Hyperlink master

-          The second board should just run from the ROM

-          The DIP switches on the second board have the right configuration for Hyperlink Boot Mode (i've checked that)

-          After powering on the master stays in this function hyplnkExamplePeriphSetup, in the while loop -> while ((!status.link) || (status.serialHalt) || (status.pllUnlock)); -> status.link is 0 (picture below)

-          Hyperlink registers from Slave are all zeros (picture below)

-          Magic addres is strange too,  but not zero (picture below)

-          In DEVSTAT is the Bootmode I2C. We assume that it is the workaround for the Advisory 8 Multiple PLLs May Not Lock After Power-on Reset Issue, which goes over the I2C.

-          Could someone please verify if the workaround in the EEPROM is right implemented? It looks like the EEPROM code jump back to the wrong address in ROM.

 

Thanks and regards,

Oleg

 

  • Oleg,

    It is my understanding that the I2C fix for Advisory 8 will write the desired bootmode to DEVSTAT before branching back to the start of the ROM code. So seeing I2C in DEVSTAT makes it seem that something is wrong in the boot process.

    Can you get other boot modes to work correctly? Can you try one of the other slave bootmodes to see if the Slave DSP gets to the correct code loop?

    Regards,
    RandyP

  • Oleg,

    The EVM's FPGA always goto I2C boot mode to do work around for advisory 8. The image then reconfigures the DEVSTAT to reflect the bootstrap pins you are setting. Few reason whuy we are not moving to the next boot mode can be

    1. The EEPROM immage are corrupted. To check this, run POST ans see if that works. If it is not then we can be assure that the EEPROM image are corrupted. To solve this, goto MCSDK\tools\program_evm and run the program_evm. This will bring the board to the default state. You can test now with POST and see if this works.

    2. Second problem might be the endianess. The EEPROM image loaded is for little endian and if you are working in the big endian mode, you need to perform the program_evm and update the image for the big endian.

    Hope this helps.

    Arun.

  • Hi Oleg,

    Are you still facing this issue.

    Thanks,

    Arun.

  • Hi Arun,

    the topic is on hold right now, i am waiting for the PG2.0 EVM to test the hyperlink boot (without any workarounds)

    Thanks for your help.

    Regards,

    Oleg