[ABANDONED] Segger J-Link refuses to flash the RM48L952 because of endianess

This site uses cookies. By continuing to browse this site, you are agreeing to our Cookie Policy.

  • [ABANDONED] Segger J-Link refuses to flash the RM48L952 because of endianess

    Hi,

    I'm trying to debug an Hercules RM48 software using CCSv7 and Segger J-Link.
    Unfortunately, the debug is aborted prior to flashing the device, with the following error:
    "CortexR4: GEL: File: C:\\workspace_v7\Test\Debug\Test.out Does not match the target endianness, not loaded. Check project build options and target configuration file (ccxml)."
    The target configuration file is already configured for little endian, but the error persists.
    What can I do to debug the RM48 software through J-Link USB in CCSv7?

    Facts:
    - Hercules RM48 ARM Cortex-R4 processor
    - Code Composer Studio version 7.0.0.00043
    - CCS Segger J-Link version 6.10.0.n

    Best regards,
    --
    Reggie Vivekananda
    Software Engineer
    ART - Alta Rail Technology
    Visit our website: alta-rt.com/
    -= Be conscious, print only what is really needed =-

  • Hi Reggie,

    In order to narrow down the list of possible causes of this issue:
    Could you please give J-Link Commander a try?
    J-Link commander is part of the J-Link software package, which is available free of charge here .

    • Start J-Link Commander (jlink.exe)
    • Type "connect" in order to start a debug session
    • Type in the target device name if asked (Or type "?" for a target selection Dialog)
    • Choose the correct target interface (JTAG/SWD/etc..)
    • Use a valid speed (Default: 4000kHz, try 100-500 if default does not work)
    • [JTAG only]JTAG conf can be default(most of the times)
    • You should now be successfully connected.
    • It is now possible to program a binary file via the >loadfile< command (works with .bin/.hex/.srec/.s19/etc. files. CCSv7 most likely has an option called "generate additional output file" which can be used to generate a file automatically after each build)
    • The commands >r<, >g<, >h<, >s< can be used for reset, go, halt and step.
    • Breakpoints can be set by using the >setbp< command.
    If anything fails, could you please post a screenshot of the complete session?

    Best regards,
    Niklas
    Please read the forum rules before posting.

    Keep in mind, this is *not* a support forum.
    Our engineers will try to answer your questions between their projects if possible but this can be delayed by longer periods of time.
    Should you be entitled to support you can contact us via our support system: segger.com/ticket/
    Or you can contact us via e-mail.