jaebond.blogg.se - Minicom usage

Minicom usage serial#
Minicom usage full#

config/minicom/, which would be a nice change since I don’t like polluting my top level dot files with a bunch of related configurations. Note: The minicom repository has a TODO item to move.

Minicom usage full#

Minicom will resolve the full path name to the configuration file on its own.

When loading a saved configuration into minicom, pass only the part of the configuration file.

i.e $HOME/.myminirc would become /home/dustfinger/.minirc._home_dustfinger_.myminirc.

If you provide a path to the configuration, all instances of the path separator will be replaced by an underscore and the resulting string will be used as the.

Custom configuration names will be saved as.

If, on the other hand, you navigate to the configuration menu after having started minicom without the -s flag, then minicom will save the configuration files to your home directory.

If you pass the optional flag -s which starts minicom directly in the configuration menu, then Minicom’s behaviour is to save the configuration to the compiled in directory only, regardless of whether or not you are running as root.

Minicom has some quirks when it comes to saving and loading configuration files. The configuration directory for the access file and the configurations We can look up the required group membership using the ls command. This is achieved by adding the correct group membership to our user account. Our user account requires rw permissions to initiate a connection with the device.

Minicom usage serial#

The rest of this blog post will simply use ttyUSB0 as the name of the serial port, but you must use the correctly named serial port assigned to your connected device if you are following along. The device name for a serial connection is properly referred to as a serial port. Also, the index number at the end of the name is determined by the devices minor number and may not be 0. There are more serial port names than I mention here. If your system architecture is ARM, you might see a name like this ttyAMA0 and if it is a Samsung, then the device might be named ttySAC0. In my case the TTY device name was ttyUSB0 however, if your cable is not a USB converter, then it might be named ttyS0 instead. usb 1-2: FTDI USB Serial Device converter now attached to ttyUSB0

ftdi_sio 1-2:1.0: FTDI USB Serial Device converter detected