[SOLVED] J-Flash readrange behavior different with GUI and command line

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

  • [SOLVED] J-Flash readrange behavior different with GUI and command line

    When using JFlash to read memeory, input NumBytes parameter to Blankcheck is different. By command line, it always be 4 and by GUI, it will be the actual bytes from range.
    Is it normal? Thanks.

    By command line:
    "C:\Program Files\SEGGER\JLink\JFlash.exe" -openprjmytest3.jflash /min /wait -connect -readrange,0x10078000,0x1007FFFF
    Result log:
    Reading target memory (0x10078000 - 0x10078000) ...
    - Start of determining flash info (Bank 0 @ 0x10078000)
    - End of determining flash info
    - Flash bank info:
    - 8 * 4 KB @ 0x10078000
    - Start of preparing flash programming
    - End of preparing flash programming
    - [b]Blank checking 0x10078000 - 0x10078003[/b]
    - Start of restoring
    - End of restoring
    - Target memory read successfully. (4 bytes, 1 range) - Completed after 0.103 sec
    J-Flash V7.80: Target memory read successfully. (4 bytes, 1 range) - Completed after 0.103 sec


    By GUI:
    Target -> Manual Programing -> Read Back -> Range -> 0x10078000 - 0x1007FFFF
    Result log:
    [tt]Reading target memory (0x10078000 - 0x1007FFFF) ...
    - Start of determining flash info (Bank 0 @ 0x10078000)
    - End of determining flash info
    - Flash bank info:
    - 8 * 4 KB @ 0x10078000
    - Start of preparing flash programming
    - End of preparing flash programming
    - [b]Blank checking 0x10078000 - 0x1007FFFF[/b]
    - Start of restoring
    - End of restoring
    - Target memory read successfully. (32768 bytes, 1 range) - Completed after 0.281 sec
  • Remember that Segger's command line utility options have the unusual requirement that parameters to options must follow the option with no whitespace or punctuation.

    Try this command line:


    Source Code

    1. "C:\Program Files\SEGGER\JLink\JFlash.exe" -openprjmytest3.jflash /min /wait -connect -readrange0x10078000,0x1007FFFF
    I can't guess a reason why the utility interprets "-readrange,0x10078000,0x1007FFFF" as a 4 byte read starting from 0x10078000 other than it's confused by that first comma.
  • @sharon Good to hear that you are up and running

    @mwb1100 It is not really an unusual requirement of "SEGGER's command line utility" but more a J-Flash specific thing. We are in the process of changing that to make it more standard but at the same time keep backward compatibility. The J-Flash command line was designed ages ago and is indeed somewhat weird at some points.
    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.