LinkServer installation on Ubuntu via command line

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

LinkServer installation on Ubuntu via command line

Jump to solution
1,104 Views
mimlo
Contributor IV

Hello,
I'd like to ask a question regarding installation of LinkServer (assuming one already has a .bin file downloaded) in an automated way - no human intervention needed.

I'm executing the following command:
./LinkServer_25.3.31.x86_64.deb.bin --accept
, but I'm still prompted with license agreement window.

From the --help it seems like it should be enough to make it accept the agreement. Below you will find output from ./LinkServer_25.3.31.x86_64.deb.bin  --help command:

Makeself version 2.4.0
 1) Getting help or info about ./LinkServer_25.3.31.x86_64.deb.bin :
  ./LinkServer_25.3.31.x86_64.deb.bin --help   Print this message
  ./LinkServer_25.3.31.x86_64.deb.bin --info   Print embedded info : title, default target directory, embedded script ...
  ./LinkServer_25.3.31.x86_64.deb.bin --lsm    Print embedded lsm entry (or no LSM)
  ./LinkServer_25.3.31.x86_64.deb.bin --list   Print the list of files in the archive
  ./LinkServer_25.3.31.x86_64.deb.bin --check  Checks integrity of the archive

 2) Running ./LinkServer_25.3.31.x86_64.deb.bin :
  ./LinkServer_25.3.31.x86_64.deb.bin [options] [--] [additional arguments to embedded script]
  with following options (in that order)
  --confirm             Ask before running embedded script
  --quiet               Do not print anything except error messages
  --accept              Accept the license
  --noexec              Do not run embedded script
  --keep                Do not erase target directory after running
                        the embedded script
  --noprogress          Do not show the progress during the decompression
  --nox11               Do not spawn an xterm
  --nochown             Do not give the extracted files to the current user
  --nodiskspace         Do not check for available disk space
  --target dir          Extract directly to a target directory (absolute or relative)
                        This directory may undergo recursive chown (see --nochown).
  --tar arg1 [arg2 ...] Access the contents of the archive through the tar command
  --                    Following arguments will be passed to the embedded script

I'm wondering if I'm doing something wrong or the LinkServer CLI is faulty.


While I'm at the topic of tools and automation, are you planning on adding a docker image for LinkServer tool or similar?


Best regards,
Michael

0 Kudos
Reply
1 Solution
1,030 Views
ErichStyger
Specialist I

Hi Michael,

can you try this:

sudo ./LinkServer_25.3.31.x86_64.deb.bin acceptLicense skipIdeSelect

?

 

Erich

View solution in original post

0 Kudos
Reply
8 Replies
1,031 Views
ErichStyger
Specialist I

Hi Michael,

can you try this:

sudo ./LinkServer_25.3.31.x86_64.deb.bin acceptLicense skipIdeSelect

?

 

Erich

0 Kudos
Reply
1,021 Views
mimlo
Contributor IV

Hi @ErichStyger,

It works like a charm thank you.

Looking at this command you provided and at the --help print, it looks like there is something missing (for example the skipIdeSelect option).
Unless of course I'm missing something and it's documented somewhere else.

Thank you once more.

Best regards,
Michael

0 Kudos
Reply
348 Views
ErichStyger
Specialist I

Hi @mimlo ,

FYI, I wrote an article about it here on my blog: https://mcuoneclipse.com/2025/08/11/streamlining-linkserver-installation-for-ci-cd/

I hope this helps,

Erich

343 Views
mimlo
Contributor IV
Impeccable timing
I'll read it tomorrow and comment there.

I see we're after a similar thing here, so combined effort might actually bring great benefits to the community.
Thanks for that!
0 Kudos
Reply
1,044 Views
mimlo
Contributor IV

Hi @ErichStyger,
I have recently seen your blog post about devcontainers and it's exactly what I wanted to set up in my team as well - although it's still on my TODO list
However, I was wondering about something more official that would be on dockerhub or some other registry with full documentation and official NXP branding. Since it's becoming more and more popular for some solutions I was just curious if that is something NXP considers.

I'm fairly confident that what you proposed works, however it does not answer the main question (even though it provides a viable solution in a form of an alternative installation method which I like very much).
The question was whether there is some misuse in my command line or there is something wrong with the binary itself.
As a matter of fact, I recently found some such inconsistency in the LinkServer flash dump command and I've been told it will be relayed up the chain to fix, so I believe it's possible and I would only want to make it clear in case anyone else stumbles upon the same issue.

I love your blogs, it's a great jobs you are doing out there, keep it up!

0 Kudos
Reply
1,039 Views
ErichStyger
Specialist I

Hi Michael,

thank you very much for your kind words!

On the --accept option, I believe this is on the debian side (not an expert on debian installation scripts), and possibly the LinkServer installation sub-part does not honor that somehow. I have pinged a contact I have so he might chime in.

About the LinkServer flash dump: if you don't mind, can you share it here or the link to that discussion?

 

Erich

0 Kudos
Reply
1,099 Views
ErichStyger
Specialist I

On the topic of automation (say: CI/CD), I recommend to have a look at a series of articles on my blog, starting with https://github.com/ErichStyger/MCUXpresso_LPC55S16_CI_CD/blob/main/README.md

Or simply use: https://mcuoneclipse.com/category/ci-cd/ 

 

I hope this helps,

Erich

0 Kudos
Reply
1,100 Views
ErichStyger
Specialist I

Hi Michael,

you can see how I'm doing this (in my case in a Ubunto docker image):

https://mcuoneclipse.com/2025/02/18/remote-debugging-with-devcontainer-and-vs-code/ 

The code and scripts are here:

https://github.com/ErichStyger/MCUXpresso_LPC55S16_CI_CD

The file is here: https://github.com/ErichStyger/MCUXpresso_LPC55S16_CI_CD/blob/main/.docker/Dockerfile 

I hope this helps,

Erich

0 Kudos
Reply