[SOLVED] How to configure J-Link flash loader for IAR EWARM?

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

  • [SOLVED] How to configure J-Link flash loader for IAR EWARM?

    The recipe for using the J-Link flash loader with EWARM IDE ends abruptly at the most intriguing moment...
    "Uncheck Use flash loader(s) in order to disable the IAR flash loader and enable the J-Link built-in flash loader."

    How can we enable the J-Link built-in flash loader?
    There is no such option in the J-Link submenu in EWARM or in the project options.
    I've installed J-Flash v. 7.82e.
  • It does not end abruptly. Disabling the IAR flash loader is all that needs to be done.
    The one from J-Link will automatically take over.
    There is NO extra menu in IAR to „enable“ the J-Link flash loader…
    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.
  • That's great, thank you Alex!

    Is the "universal" QSPI flash programming also supported in this mode for STM32 ?
    How to pass the "loader name" such as CLK@PF10_nCS@PB10_D0@PF8_D1@PF9_D2@PF7_D3@PF6 to the DLL?

    --dd
  • Yes, it is available.
    The only option for loader selection in EWARM is the J-Link control panel:
    wiki.segger.com/J-Link_Multipl…#J-Link_web_control_panel
    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.
  • Rejoiced too early ((
    This still does not work with ST Cube IDE.
    Copied v.7.82e DLLs to the Cube. Started debugger and opened the web UI.
    The QSPI flash pinout/loader name selection won't persist after change.
    Every time when I start debugger, I have to change the QSPI loader and relaunch.
    Even after this, the debugger goes hairwire and resets the target:
    .........
    Downloading 112 bytes @ address 0x2000AEFC - Verified OK
    Downloading 63 bytes @ address 0x91000000 - Verified OK <-------------- this is in QSPI
    ERROR: SEGGER_OPEN_GetFlashInfo(): Algo reported a flash size of 0 bytes. <---- ??? What The Flash ???
    Error while determining flash info (Bank @ 0x90000000)
    .......

    If I exclude QSPI data from the executable, debugger starts successfully (stops at main).
    Does the QSPI loader always reset the target after loading? Why?

    Where the settings file of the JLink*.dll is documented?
    The settings file can be specified on the Settings tab of the web UI. I wonder if it can help, because in the ST IDE settings of J-LINK do not seem to persist.
    (GDB server command line options can be specified in CubeIDE but these are not applicable to the J-LINK DLL?)

    The post was edited 1 time, last by ddbug ().

  • 1)
    The screenshot from the wiki article IS from the control panel. I NEVER wrote that the screenshot shows the settings for YOUR actual device.
    It is a generic article, so SOME device was used to create the screenshot.
    So your statement is just nonsense…

    2)
    As the article describes, a settings file is needed to make the settings persistent. The path needs to be passed by the IDE (it actually only needs to pass a path to the project directory, where J-Link has write permissions).

    If the IDE does not pass any -> Better get in touch with the IDE vendor, as the missing settings file path limits you in using the feature set of J-Link. We will contact ST in parallel, but experience tells that customer requests are taken prioritized for things like that.

    3)
    The settings file cannot be specified in the settings tab. All it does is showing what the active settings file is.

    4)
    You may start GDB Server manually…
    - Choose “show command line” in Cube IDE to see the GDB Server parameters.
    - Copy them.
    - Start your own GDB Server instance with that options and add the -settingsfile option with a path of your choice.
    wiki.segger.com/J-Link_GDB_Server#-settingsfile
    - Change your Cube IDE project from “Auto start local GDB Server” to “Connect to remote GDB Server”

    Done.
    Not beautiful, but something you can work with, until the vendor fixes the IDE.
    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.