• State Resolved
  • Locked Locked
  • Replies 5 replies
  • Subscribers 83 subscribers
  • Views 717 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/LAUNCHXL-F28379D: Flash CPUs indepently with Simulink and CCS

Stefan Schuhmacher
Prodigy 110 points
Part Number: LAUNCHXL-F28379D


Tool/software: Code Composer Studio

Hey Guys,

im building up an inductive Loading station with TI LaunchXL-F28379D and some Halfbridge MosFET Evaluation Boards. However i want to run on the first CPU the CCS program which measures the temperatures and show them on an LCD Screen. It works fine.

On the CPU2 i wanted to flash a Simulink project with a Sinusoidial ePWM. i tested both programs seperately and they are working fine.

My Problem is now that i wanted to bring them together. So first flash CPU1 with CCS and after that CPU2 with Simulink. But CPU2 doesn't start running. 

So may you have an idea how i can solve that problem and to explain why things are doing what things do:)


Greetings

Stefan  

  • 0
    Prodigy 110 points

    i wanted to know whats the problem is so i started it in external mode: 

    Here are the last lines of the Diagnostics Report:

    *** Connecting to target...
    C28xx_CPU2: GEL Output:
    Memory Map Initialization Complete
     
     
    C28xx_CPU2: If erase/program (E/P) operation is being done on one core, the other core should not execute from shared-RAM (SR) as they are used for the E/P code. Also, CPU1 will be halted to determine SR ownership for the CPU which will run the Flash Plugin code, after which CPU1 will be set to run its application. User code execution from SR could commence after both flash banks are programmed.
     
     
    *** Loading the program to the target...
     
    *** Program is running.
     
    *** Disconnecting from target...
     
    *** Terminating debug session...
    *** LOAD & RUN DONE.
    ### Successful completion of build procedure for model: TI_Programm
     
    ### Creating HTML report file TI_Programm_codegen_rpt.html
    Build process completed successfully
    action: EXT_CONNECT
    Component:Simulink | Category:Model
    Error occurred while executing External Mode MEX-file 'ext_comm': Failed to connect to the target. A time-out occurred while waiting for the connection response from the target. Possible reasons for the time-out: a) The target is not switched on. b) The target is not connected to your host machine. c) The application for the model is not running on the target. You might have clicked the Stop button. If the Run button is not dimmed, click it. Otherwise, click the Build button, which downloads and runs your application on the target.
    Component:Simulink | Category:Block diagram error
    Unable to connect to the 'TI Delfino F28379D LaunchPad' target for 'TI_Programm'.
  • 0 in reply to Stefan Schuhmacher
    TI__Mastermind 27200 points

    Stefan,

    Thanks for posting.  This is just to let you know we are looking into your question and will get back to you.

    Regards,

    Richard

  • 0 in reply to Richard Poley
    Mastermind 6460 points

    Hi,

    Try running CPU2 first from CCS and then CPU1.

    Here is a picture that shows the same. First run CPU2 as per image and then CPU1.

  • 0 in reply to Stefan Schuhmacher
    Mastermind 6460 points

    Hi,

    It is unlikely you can run external mode from CPU2 without MATLAB/Simulink code running from CPU1.

    But I can confirm this ASAP.

  • 0 in reply to venkatesh chilapur
    Mastermind 6460 points

    Hi,

    The Initialization routine of CPU1 and CPU2 are coupled such that ONLY MATLAB generated code running on CPU1 and CPU2 can get through the handshake sequence and the board can boot properly. But a non-MATLAB code on CPU1 will make CPU2 wait in-definately for a IPC response from CPU1 (which is specific to our internal design). That way, CPU2 code will never run. Hence from our point of view you should always use the MATLAB/Simulink to implement your application for both CPU1 and CPU2. It is unlikely that the current approach of non-MATLAB code on CPU1 will work.

    Please connect to Mathworks support for further help.

    https://mathworks.com/support.html