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.

LAUNCHXL-F28027F: Flashing the TMS320F target, then unable to run "Gui Composer" in standalone

Part Number: LAUNCHXL-F28027F

Hello,

I have tested and built-up an IHM menu in Gui Composer.

I have flashed the TMS320F target with the proper code ; therefore I deselected the button "Autoprogram" in GuiComposer for the HMI generation.

And I uplaoded a standalone application.

Bu nothing works ; the GuiComposerHMI does not make the device working.

Can anybody indicate the right procedure ?

Many thanks in advance for your help.

Best regards.

  • Hello,

    Can you explain in more detail what is the exact issue? You mention "does not make the device working". Please clarify what this means and what is "no working".

    If auto-program is left enabled, does things work as expected?

    Thank

    ki

  • Hello Ki, 

    Thanks for your time, and sorry for my "poor" explanation.

    I will try to explain better:

    1- I have developped a HMI interface using "Gui Composer" ; this HMI is driving parameters in my CCS code. 

    2- After having launched "Gui Composer", ticked "Autoprogram" and uploaded the file "*.out" from my RAM folder project, every thing works well, as long as I remain in the "Gui Composer" environment. 

    3- From this step, I want to generate a standalone application, through the menu "File\Export\as Standalone App".

    I have installed "Gui Composer Runtime" and "TI Cloud Agent".

    4- Outside "Gui Composer", when I execute the runtime "launcher.exe", I can see the tool which launches the app, connects to the TMS320F target, and executes the "TI cloud Agent" ==> the apllication runs well afterwards.

    5- Now, I would like to flash the code in the TMS320F target, without programming the RAM anymore.

    Therefore, I have flashed the target in the CCS environment with my app code.

    And I wanted to generate a standalone HMI application, following the previous described method but without ticking "Auto Program" as the target is already flashed.

    And this does not work ==> the standalone HMI does not communicate with the target anymore.

    I don't know why.

    Hoping that is clearer now.

    Best regards.

    Bruno

  • Thanks.

    One last question. You mention that the code is flashed, but also mentioned RAM. Is the code loaded to flash or RAM?

  • Hello Ki,

    At the step 4 of my last description, the standalone launcher downloads the files "*.out" coming from the RAM folder of my CCS project.

    Therefore, I suppose that the code is downloaded in the RAM of the microcontroller (sorry, I am not an expert in using this tools).

    This operation works but I find that it is not a good method to program the micro each time the standalone application is launched. That's why I decided to flash the micro in the CCS environment, assuming that the micro being flashed, there is no need to reprogram it on each launch : this is the step 5 of my last description, which does not work.

    Bruno

  • Therefore, I suppose that the code is downloaded in the RAM of the microcontroller (sorry, I am not an expert in using this tools).

    Thanks for the clarification. 

    That's why I decided to flash the micro in the CCS environment, assuming that the micro being flashed, there is no need to reprogram it on each launch

    Since it appears the code is being loaded to RAM and not flash, as long as the target is not power cycled after the program is loaded, the code should remain in RAM (unless something is done to RAM like reinitialization, etc). 

    However, the default behavior for GC when connecting to the target via XDS is to briefly halt the target before resuming execution. If "auto-program" is disabled, then that would result in a brief interruption of the running program. Depending on the application, this can have a crucial impact on the application real-time behavior. There is no way to change this. Could it be that this short pause is disrupting your application behavior?

    ki