No XMC4500 flash programming possible on Linux JLink 4.82 (works again after downgrade to 4.80e)

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

  • No XMC4500 flash programming possible on Linux JLink 4.82 (works again after downgrade to 4.80e)

    On JLink 4.82 64bit Linux version, I am unable to flash program my xmc4500-1024 (jlink-lite on Infineon XMC Relax board).

    Version 4.82 (fail):

    Source Code

    1. J-Link>loadbin test.bin, 0x8000000
    2. Downloading file... [test.bin]
    3. J-Link>


    Version 4.80e (success):

    Source Code

    1. J-Link>loadbin test.bin 0x8000000
    2. Loading binary file... [test.bin]
    3. Writing bin data into target memory @ 0x08000000.
    4. Info: J-Link: Flash download: Flash programming performed for 1 range (16384 bytes)
    5. Info: J-Link: Flash download: Total time needed: 1.142s (Prepare: 0.614s, Compare: 0.037s, Erase: 0.418s, Program: 0.013s, Verify: 0.004s, Restore: 0.054s)
    6. J-Link>


    Something odd on both versions has to do with scripting (I just was curious, so I tried):

    Source Code

    1. $ JLinkExe /opt/SEGGER/JLink/Samples/JLink/Scripts/XMC4500.JLinkScript
    2. SEGGER J-Link Commander V4.80e ('?' for help)
    3. Compiled Jan 31 2014 18:14:07
    5. Script file read successfully.
    6. DLL version V4.80e, compiled Jan 31 2014 18:14:04
    7. Firmware: J-Link Lite-XMC4000 Rev.1 compiled Dec 7 2012 19:23:07
    8. Hardware: V1.00
    9. S/N: 55100XXXX
    10. VTarget = 3.300V
    11. Info: Could not measure total IR len. TDO is constant high.
    12. Info: TotalIRLen = ?, IRPrint = 0x..000000000000000000000000
    13. No devices found on JTAG chain. Trying to find device on SWD.
    14. Info: Found SWD-DP with ID 0x2BA01477
    15. Info: Found Cortex-M4 r0p1, Little endian.
    16. Info: FPUnit: 6 code (BP) slots and 2 literal slots
    17. Info: TPIU fitted.
    18. Info: ETM fitted.
    19. Cortex-M4 identified.
    20. Target interface speed: 100 kHz
    21. Processing script file...
    23. Unknown command. '?' for help.
    25. Unknown command. '?' for help.
    27. Unknown command. '?' for help.
    28. ...
    Display All

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

  • Hi,

    Something odd on both versions has to do with scripting (I just was curious, so I tried):

    There is nothing odd with scripting you are just using an incompatible file as J-Link Commander "command file".
    Basically there are two types of script files which are completely different and not compatible to each other:

    1) J-Link script files (see UM08001 for more info) which are C-like-syntax scripts for customizing connect sequences, resets etc. for devices which need this.
    2) J-Link command files for J-Link Commander which are basically like batch files under windows: They contain 1 command per line that is executed by J-Link Commander.
    Syntax etc. is exactly the same as you were manually typing them in J-Link Commander.
    What you are trying to do is to execute a C-like J-Link script file as J-Link command file which is not possible

    On JLink 4.82 64bit Linux version, I am unable to flash program my xmc4500-1024 (jlink-lite on Infineon XMC Relax board).

    We will check.
    Could you please confirm that you are doing the following?:
    Start J-Link Commander like this:
    ./JLinkExe -device XMC4500-1024 -if SWD -speed 4000

    Then typing:
    loadbin test.bin, 0x08000000


    - Alex
    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.

  • Thank you very much for your kind reply.
    I tested it with the commandline you supplied on both versions:

    JLinkExe 4.82:

    Source Code

    1. $ JLinkExe -device XMC4500-1024 -if SWD -speed 4000
    2. SEGGER J-Link Commander V4.82 ('?' for help)
    3. Compiled Mar 10 2014 19:08:40
    4. Info: Device "XMC4500-1024" selected (1024 KB flash, 64 KB RAM).
    5. DLL version V4.82, compiled Mar 10 2014 19:08:37
    6. Firmware: J-Link Lite-XMC4000 Rev.1 compiled Dec 7 2012 19:23:07
    7. Hardware: V1.00
    8. S/N: 55100xxxx
    9. VTarget = 3.300V
    10. Info: Performing XMC4500 connection sequence.
    11. Info: Found Cortex-M4 r0p1, Little endian.
    12. Info: FPUnit: 6 code (BP) slots and 2 literal slots
    13. Info: TPIU fitted.
    14. Info: ETM fitted.
    15. Found 1 JTAG device, Total IRLen = 4:
    16. Cortex-M4 identified.
    17. Target interface speed: 1539 kHz
    18. J-Link>loadbin test.bin, 0x08000000
    19. Downloading file... [test.bin]
    20. J-Link>speed 100
    21. Target interface speed: 400 kHz
    22. J-Link>loadbin test.bin, 0x08000000
    23. Downloading file... [test.bin]
    24. J-Link>speed auto
    25. Target interface speed: 1539 kHz
    26. J-Link>loadbin test.bin, 0x08000000
    27. Downloading file... [test.bin]
    28. J-Link>speed adaptive
    29. The connected J-Link does not support adaptive clocking.
    30. J-Link>speed 100
    31. Target interface speed: 100 kHz
    32. J-Link>loadbin test.bin, 0x08000000
    33. Downloading file... [test.bin]
    34. J-Link>
    Display All


    JLinkExe 4.80e (4.80.5) (success):

    Source Code

    1. $ JLinkExe -device XMC4500-1024 -if SWD -speed 4000
    2. SEGGER J-Link Commander V4.80e ('?' for help)
    3. Compiled Jan 31 2014 18:14:07
    4. Info: Device "XMC4500-1024" selected (1024 KB flash, 64 KB RAM).
    5. DLL version V4.80e, compiled Jan 31 2014 18:14:04
    6. Firmware: J-Link Lite-XMC4000 Rev.1 compiled Dec 7 2012 19:23:07
    7. Hardware: V1.00
    8. S/N: 55100xxxx
    9. VTarget = 3.300V
    10. Info: Performing XMC4500 connection sequence.
    11. Info: Found Cortex-M4 r0p1, Little endian.
    12. Info: FPUnit: 6 code (BP) slots and 2 literal slots
    13. Info: TPIU fitted.
    14. Info: ETM fitted.
    15. Found 1 JTAG device, Total IRLen = 4:
    16. Cortex-M4 identified.
    17. Target interface speed: 1539 kHz
    18. J-Link>loadbin test.bin, 0x08000000
    19. Loading binary file... [test.bin]
    20. Writing bin data into target memory @ 0x08000000.
    21. Info: J-Link: Flash download: Flash programming performed for 1 range (16384 bytes)
    22. Info: J-Link: Flash download: Total time needed: 0.875s (Prepare: 0.100s, Compare: 0.032s, Erase: 0.405s, Program: 0.328s, Verify: 0.001s, Restore: 0.005s)
    23. J-Link>
    Display All



    Thanks for pointing out the differences between C-like and batch-like scripts.

    BTW:
    Description of the command line options in UM08001 §3.11.1.1 is inconsistent (-CommandFile vs -CommanderScript)

  • Hi,

    Alright, we will try to reproduce here.

    Description of the command line options in UM08001 §3.11.1.1 is inconsistent (-CommandFile vs -CommanderScript)

    Thanks for pointing this out. There have been some naming changes in the past (old commands are still accepted), so maybe some parts of the documentation have not been updated properly.


    - Alex
    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.

  • Hi,

    Problem is reproducible and will be fixed in the next version, planned for later today.


    - Alex
    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.

  • Hi,

    Status update:
    New version has been delayed for this week due to some other things we are currently working on and that should make it into this version.
    Will update this thread as soon as the new version is available.


    - Alex
    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.

  • Release is still "under development". For now, please find a fixed beta version available for download, on our website:
    segger.com/jlink-software-beta-version.html


    - Alex
    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.