• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 56 subscribers
  • Views 285 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.

CCS/TDA2HF: What kind of project should i made for M4 core's debug?

user6243290
Intellectual 510 points
Part Number: TDA2HF
Other Parts Discussed in Thread: TDA2

Tool/software: Code Composer Studio

Hi everyone,

I'm using TDA2x, CCSV6.2 under windows 10 Environment. I already  had a project file from others(1 A15 core,2 C66 cores ,one M4 core related) ,the file has no .cproject or .ccsproject...

so i built one common c project by CCSV6.2, import all my files, the building process was succeed. all elf was loaded ok.

I'm trying to debug the M4 core for  drivers conifg, the breakpoint just can't ran into the line. 

Is that right that i made the common c project,or should i make one M4 project at CCSV6? 

Thanks for ur help!

  • 0
    TI__Guru**** 159715 points

    Are you saying you have a single project that builds the program files for the A15, 2x C66 and M4?  That seems odd as there would be different compilers used for each of the cores or in the case of the A15 and M4 at least different build options.  CCS projects typically don't allow you to produce multiple elf files.  You would have one per core.

    John

  • 0 in reply to JohnS
    Intellectual 510 points

    Hi,John

    I made one c project,and load the files ,it can build successfully. the connection to TDA2X is ok too.i just can't debug for one core -m4.

    Do u mean that i need to make one M4 project for debug the m4 core? 

    If so, how to connecting  the target,  the A15 always need to connect 1st,in my opinion. 

    The loaded picture is the example for TDA2_BIOS, i cant' connect to the TDA2X chip.

    How to deal with my problem ,thx a lot!

  • 0 in reply to user6243290
    TI__Guru**** 159715 points

    Really there are 2 issues here.

    1) Projects

    If using CCS projects you will need to have a project for each of the programs that you are going to build.  The M4 would have its own project that produces its own output.  The C66 cores use a completely differnet compiler from the A15 and M4 cores and would have to have there own project as well.  Typically the processor SDK for these devices does not provide CCS projects but instead has makefiles.  Those makefiles could be setup to create multiple outputs from a single build. 

    2) M4 core being held in reset

    That error in red that you are seeing is stating that the Cortex M4 core is being held in reset.  A couple lines above that in the output I see something that indicates that it should have been released from reset but that appears to not be the case. (IcePick_D: GEL Output: Ipu RTOS is released from Wait-In-Reset.).  I will need to loop in someone from the automotive team to help with this as I do not have access to this device to debug this issue.

    Regards,

    John

  • 0 in reply to JohnS
    TI__Mastermind 42515 points

    Hi @,

    can you try to run the .gel configuration file as described inthis post (just note it is for IPU2, you should use IPU1):

    Also you may look at this Application Note and see if you can find some directions there:

    Regards,

    Yordan

  • 0 in reply to Yordan Kamenov
    Intellectual 510 points

    Hi,you two guys,

    Thanks for reply me.

    Do u mean i must select the A15 CORE's connectiong at anyother projects for TDA2X?

    If i made one M4 CORE project, i must choose A15 and M4 core, and connect the A15 1st, then connect the M4,no metter the A15 has elf or not?

    Is that right?

    PS，

    I did it in a IPC example ,as follows:

    " https://e2e.ti.com/support/tools/ccs/f/81/t/914833 ", it's my question too ,and my main task is to solve the IPC problem,it bothers me a lot.

    could u please help me to solve it , thanks a lot!