• State Resolved
  • Locked Locked
  • Replies 6 replies
  • Answers 1 answer
  • Subscribers 53 subscribers
  • Views 2106 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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/TMDSLCDK138: TMDSLCDK138

Itzhak Kroin
Intellectual 670 points

Part Number: TMDSLCDK138
Other Parts Discussed in Thread: OMAPL138

Tool/software: Code Composer Studio

TMDSLCDK138+XDS110 ARM bypass and DSP674x active

Hello project working.

Loaded typical SYS/BIOS project. compilation is OK and the following error occurred during load:

 

Thanks,

Itzhak

  • 0
    TI__Guru**** 171519 points

    Itzhak,

    The error you are seeing is failing to properly load the code to external memory. You should have a GEL file tied to the DSP to properly configure this (check this reference).

    This may or may not work, however. As I explained to you in the other thread, the use of XDS110 + OMAPL138 is not supported and may present some data communication issues during initialization or code loading.

    Do you have another Debug Probe available that you could test this configuration?

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 670 points

    Hi Rafael,

    What you means the  use of XDS110 + OMAPL138 is not supported? There was a solid recommended of TI to use XDS110 for emulation of TMDSLCDKL138 board. It was purchased recently. At the moment I don't have another emulator. So, lets consider the gel problem will be solved, what can be done? return back the XDS110 to TI and purchase another one instead (and which one)? By the way 18 sets of boards are involved here for academic purpose!

    Regards,

    Itzhak

  • 0 in reply to Itzhak Kroin
    Intellectual 670 points
    Hi Rafael,

    Is there a document/reference which describe what can be done and can't be done with the use of XDS110?

    Regards,

    Itzhak
  • 0 in reply to desouza
    Intellectual 670 points

    Rafael,

    The memory map problem solved after re-config the processor for slave or bypass.

    Regards,

    Itzhak

     

  • 0 in reply to Itzhak Kroin
    TI__Guru**** 171519 points

    Itzhak,

    Please apologize for the delay and thank you for reporting back your findings. I was also doing some additional investigation to see if the C674x core could be connected without having the ARM9 active.

    What I found is that the DSP is a slave core and depends on the ARM9 core to be properly powered up and released from reset.

    Power up the DSP can be done as long as the GEL file of the ARM9 core does not try to modify the PLL frequencies, which cause also the JTAG TCLK signal to change and make the XDS110 lose control over this core. Since the GEL file for the OMAPL138LCDK changes the PLL, a workaround is required to prevent the debugger from disconnecting. 

    What I did is shown in the short clip below.

    - added the GEL file to the C674x core instead of the ARM9

    - connected to the ARM9, opened the expressions view and added the following expressions: *(0x1C10A3C) *(0x1E27120)

    - Changed the radix to Hex and inserted 0x103 for the first entry and 0x1 for the second

    - Then I was able to connect to the DSP

    Depending on the boot mode of the device, the DSP is already released from reset and therefore can be connected without any blocking issues.

    Despite all this, the experience with the XDS110 + OMAPL138 is not straightforward and therefore the reason why it is not recommended. 

    Regards,

    Rafael

  • 0 in reply to desouza
    Intellectual 670 points
    Hi,

    I started with ARM set as bypass, DSP with init gel and other processors set as slave. The memory location as mentioned where already sets for the correct values and surprisingly it's start working. It seems the system is fragile and tends to stack. At that point or hard resetting the board or setting again configuration or close CCS and restart it helps. Need to be very carefully for any modification done or adding features.

    Thanks,
    Itzhak