Getting Started With Minicom

From wiki.emacinc.com
Revision as of 18:02, 28 October 2015 by Jjung (talk | contribs)
Jump to: navigation, search
TODO: {{#todo: InProgress (10.28.2015-16:36->JJ+)|Jeffrey Jung|OE 5.0,InProgress,JJ,MD}}

Background

minicom is a serial communication program that connects to devices through a GNU/Linux PC's serial ports. If run my calling its name without any additional arguments, it uses whatever settings have been saved for its defaults in /etc/minicom/minirc.dfl. For those using a Windows, PuTTY is a great application to make such connections. More information about PuTTY can be found at http://wiki.emacinc.com/wiki/PuTTY.


General Information

The use of minicom is required when connecting to and EMAC board for testing purposes. This pages sets out to provide general information about using minicom as well as a guide to demonstrate using minicom to connect with EMAC devices.

Getting Started With Minicom

Hey!!! Create a nice intro type thing for the procedure.

  1. If minicom has yet to be installed on your development Linux machine, use apt-get to install the minicom package

    user@developerpc:~# sudo apt-get install minicom
  2. The minicom settings will need to be changed so that the application will be able to find your device. Pull up the settings using the -s option.

    user@developerpc:~# minicom -s
  3. The first thing that will need to be configured is the serial port setup. Arrow down to the title and press the Enter key.
    [Screenshot?]

  4. To modify the different configurations, press the key corresponding to the setting. For example, press the 'A' key to modify the Serial Device. Press the 'Enter' key to save the parameters for the setting. The EMAC devices will require the Bps/Par/Bits, and flow control settings. Set Bps/Par/Bits to 115200 baud, 8 data bits and no priority. Set both flow control settings to 'No'. Press the 'Esc' key to save the settings and to be be brought back to the configurations page.
    [definitely use a screenshot here]


Examples

Conclusion

Further Information

Where to Go Next
Pages with Related Content