this container only has the NXP MCU-Link server to connect with NXP MCU -Link probes
142
26.6, latestThe image has been prepared to run NXP MCU-LINK Server only, with the goal to keep the container as small as possible. it is download from NXP official web site for its linux version.
By default to container will run the cotnianer with a root user, but this will change in the future. To run the container make sure to use the --device flag to map the USB ports to the container, and the -p flag to map the port 3333 to the host computer.
docker run -it --rm --device=/dev/bus/usb:/dev/bus/usb -p 3333:3333 modularmx/linkserver:latest
Once the container is running, you can connect to the LinkServer as you usualy do when is installed in a host computer the only thing to taken into account is a couple of extra flags. for instance with the following line LinkServer will wait a GDB connection on the port 3333 and any external IP address
LinkServer gdbserver --keep-alive --allow-remote MCXA156:FRDM-MCXA156
You can also check our nice tutorial How to run images with compose
networks:
static_net: # network name to be used by containers
driver: bridge # network driver
ipam:
config: # network configuration
- subnet: 172.25.0.0/16 # network subnet
gateway: 172.25.0.1 # network gateway
services:
link_server: # container name been used by the image to connect LinkServer
image: modularmx/linkserver:latest
ports: # port mapping
- 3333:3333
devices: # device mapping to usb ports
- /dev/bus/usb:/dev/bus/usb
networks:
static_net: # use network static_net
ipv4_address: 172.25.0.3 # assing ip address to container
command: LinkServer gdbserver --keep-alive --allow-remote MCXA156:FRDM-MCXA156
Content type
Image
Digest
sha256:f019923a7…
Size
171.9 MB
Last updated
2 months ago
docker pull modularmx/linkserver