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.

CCS/TMS320C6678: Spi boot problem

Part Number: TMS320C6678


Tool/software: Code Composer Studio

Hi All,

I have some problems in SPI booting with C6678 board.

On one hand,If I just connect emulator in hardware,not launch .ccxml or not connect target, there always one device cannot running in SPI boot mode.And emulator cannot connect core 0 at this time when I want to know the status of the device,however,all the other cores are connected successfully.

On the other hand, if I completely take off the emulator ,no matter in hardware or software,all devices run successfully when I turn off and on the power.

As I know, JTAG mode can take effect only when I connect the target successful,right?And I also can be sure the power is enough to support all devices to run ,because I have successfully ran all in JTAG mode.

So, what may be the reasons?

Waiting for your reply!

Thanks,

HaiShan

  • Hi,

    I've notified the RTOS team.

    Please share which Processor SDK RTOS are you using?

    Best Regards,
    Yordan
  • Hi,
    I am still using bios_mcsdk_02_01_02_06 version!

    Thanks,
    HaiShan
  • I do not understand the issue clearly. Is it a boot issue or emulator related issue?

    Are you working on custom board or EVM? Do you see this problem in one or more boards? What is the boot mode set?

    Thank you.
  • Hi,

    Sorry ,I didn't work in office latest.

    This also is what I don't understand.I tell the issue in detail.

    I am still working on custom board with four DSPs designed by ourself.I set the default boot mode in SPI boot.

    If I disconnected the emulator ,and have burned the code in flash,the board would work normally .

    If there was no code in flash, I also could connect  and debug the board  normally.

    The prolem is only met when I burned the code in flash,launch the .ccxml configuration but didn't connect.There is one DSP always not working.Then I connected the unnormal DSP with core0,but failed.However I successfully connected with the other cores in the same device.

    So I think there are two problems,one is the booting issue and the other is the connected issue.And they only appear in particular circumstance.

    Thanks,

    HaiShan

  • HaiShan,

    I think there is a problem with the code running on core 0 which does not allow you to connect to the core because you are able to connect to the core when there is no code on SPI flash/no boot mode.

    If you have EVM, please try to re-produce the issue with the image used on your board.

    Thank you.
  • Please note that MCSDK 2.x is a legacy baseline and we are only supporting Processor SDK RTOS based development for these devices on the E2E forums. The documentation for Processor SDK RTOS clearly highlights this need to use older compiler as you can see from here: