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.

  • Resolved

CCS/RM41L232: CCS Release version loading problem

Part Number: RM41L232

Tool/software: Code Composer Studio

Hi all,

We are trying to load the release FW version in a RM41L232 microcontroller using CCS and we are having problems with it. We are using the XDS200 USB programmer, we have generated the hex or out files with the code composer and load them with the UNIFLASH program version 4.3.1 but unsuccessfully. When we load the release version it does not give any fault in the programming or in the verification but the equipment does not do anything (not a simple blink of a led). Could you give us any idea of where the fault is? If you need more information please request us anything.

Best regards

  • Guru 148060 points

    To have another reference point, does the same program (.out) run as expected when loaded using CCS?

    ____________________________________________________________________________

    Please click This Resolved My Issue if the reply answers your question.

    Search the wikis for common questions: Compiler, CCSv6, CCSv7
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

  • In reply to AartiG:

    The (.out) and the (.hex) do the same thing, when uploaded the system remains inoperative.

  • In reply to Marcos Martinez:

    You state that the "release" version does not work correctly when programmed. Do you also have a "Debug" version of this firmware? Does that version work correctly? What are the optimization levels that are different between the "Debug" and the "Release" versions?

    I have seen experienced that an increased optimization level is used for the "Release" version, which causes the compiler to optimize out some code.
  • Guru 148060 points

    In reply to Marcos Martinez:

    Marcos Martinez
    The (.out) and the (.hex) do the same thing, when uploaded the system remains inoperative.

    We need to isolate if the issue is with the tool (Uniflash) or the firmware code. To that end I was asking whether you are able to load and run the code successfully using CCS instead of Uniflash (to help isolate if the issue is specific to Uniflash).

    And as Sunil suggested, are you able to load and run the "Debug" version of the firmware code successfully? How about other programs? 

    ____________________________________________________________________________

    Please click This Resolved My Issue if the reply answers your question.

    Search the wikis for common questions: Compiler, CCSv6, CCSv7
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

  • In reply to AartiG:

    Hi AartiG,

    If we load the Debug version with CCS it works OK, but we have been not able to make a (.hex) and load it with Uniflash succesfully. We don't have any other program to load with Uniflash and try, do you have a simple test program to try loading it?
  • In reply to Sunil Oak:

    Hi Sunil,

    We actually have a Debug version and it works OK loading it with CCS but we want to load the final version. We have not implemented any optimization, we have just create (.hex) file and try to load it with Uniflash but it doesn't work.
  • Guru 148060 points

    In reply to Marcos Martinez:

    Marcos Martinez
    If we load the Debug version with CCS it works OK, but we have been not able to make a (.hex) and load it with Uniflash succesfully.

    How about if you load the .out file (instead of .hex file) using Uniflash? Does that work? If it works, then the issue could be in the hex conversion process.

    Marcos Martinez
    We don't have any other program to load with Uniflash and try, do you have a simple test program to try loading it?

    Sunil, do you have a known good example program for this target device that they could try with Uniflash?

    ____________________________________________________________________________

    Please click This Resolved My Issue if the reply answers your question.

    Search the wikis for common questions: Compiler, CCSv6, CCSv7
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

  • In reply to AartiG:

    Marcos,

    Can you please upload the CCS project that you are using to try to blink the LED? I can look at the configuration options and see if a compiler optimization is causing the pin toggle code to be optimized out.

    Aarti,

    The issue is not with loading / verifying the code with CCS or Uniflash. It is just that the code does not do what is expected after programming.

    The difference is between the "Debug" and the "Release" versions of the compiled output. Do you know what optimization levels are automatically enabled when going from "Debug" to "Release" configurations in a given CCS project?

    Regards, Sunil

  • Guru 148060 points

    In reply to Sunil Oak:

    Sunil Oak
    Do you know what optimization levels are automatically enabled when going from "Debug" to "Release" configurations in a given CCS project?

    That depends entirely on the project as the options are fully customizable. However, for a default Cortex R project created using the CCS New Project wizard, the "Debug" configuration has no optimization and "Release" has -o2 optimization.

    ____________________________________________________________________________

    Please click This Resolved My Issue if the reply answers your question.

    Search the wikis for common questions: Compiler, CCSv6, CCSv7
    Track a known bug with SDOWP. Enter the bug id in the "Find Record ID" box

  • In reply to AartiG:

    The (.out) file doesn't work with Uniflash either , both do the same thing, Uniflash doesn't show any error when uploading the image but after that the system doesn't respond.
    It would be fine as you commented if anyone could share a know working program and load it with Uniflash to test it.

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.