[SOLVED] -nogui documentation request

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

  • [SOLVED] -nogui documentation request

    Can documentation for -nogui be added in the the user manual for jlink.exe?

    The UM08001_JLink.pdf from the v7.56b package only mentions -nogui for the GDB Server and worse it makes no mention of the required argument (-nogui 1 is needed for jlink.exe). Perhaps GDB Server doesn't need the "1" argument? This led to a bit a head scratching about why jlink.exe would complain about "Missing command line parameter after command -NoGui". (why does -nogui need an argument anyway?)


    Also, the release notes for commander and some forum posts indicate that -nogui is documented on the wiki (wiki.segger.com/J-Link_Commander#-NoGui), but that isn't the case. The J-Link Commander Wiki page doesn't mention -nogui at all (maybe it was removed for some reason?).

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

  • Hi,
    Thank you for your inquiry.

    The -NoGui command was lost when the wiki page was reworked.
    We corrected the J-Link Commander documentation accordingly:
    wiki.segger.com/J-Link_Commander#Batch_processing

    Thank you for making this known to us.

    The J-Link Commander requires parameters for all command line options for historical reasons.
    In theory, there are multiple command line options that would not require a specific value to work (-AutoConnect, -ExitOnError, -NoGui).
    However it was decided against changing the behavior in retrospect,
    a) to stay backwards compatible and
    b) to stay consistent with the current command line scheme used for the J-Link Commander.

    Does this answer your questions?

    Best regards,
    Fabian
    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,
    Good to hear that you were able to figure it out even while the documentation was lacking.

    We will consider this thread as closed now.

    Best regards,
    Fabian
    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.