build/vendor/github.com/tarm/serial
Jeff Johnson 2026ec7cdb cmd/buildlet: output logs to serial port on windows GCE buildlets
Use tarm/serial to direct logs to COM1 on GCE.
Tested with Windows Server 2016.

tarm/serial vendored at 37be519d49878d0098e34fb614136b81e6c87861

Change-Id: I66908a7d4dd0b0c40008a2e7945fc530af4cb1ee
Reviewed-on: https://go-review.googlesource.com/42141
Reviewed-by: Brad Fitzpatrick <bradfitz@golang.org>
2017-04-28 22:14:43 +00:00
..
.travis.yml cmd/buildlet: output logs to serial port on windows GCE buildlets 2017-04-28 22:14:43 +00:00
LICENSE cmd/buildlet: output logs to serial port on windows GCE buildlets 2017-04-28 22:14:43 +00:00
README.md cmd/buildlet: output logs to serial port on windows GCE buildlets 2017-04-28 22:14:43 +00:00
basic_test.go cmd/buildlet: output logs to serial port on windows GCE buildlets 2017-04-28 22:14:43 +00:00
serial.go cmd/buildlet: output logs to serial port on windows GCE buildlets 2017-04-28 22:14:43 +00:00
serial_linux.go cmd/buildlet: output logs to serial port on windows GCE buildlets 2017-04-28 22:14:43 +00:00
serial_posix.go cmd/buildlet: output logs to serial port on windows GCE buildlets 2017-04-28 22:14:43 +00:00
serial_windows.go cmd/buildlet: output logs to serial port on windows GCE buildlets 2017-04-28 22:14:43 +00:00

README.md

GoDoc Build Status

Serial

A Go package to allow you to read and write from the serial port as a stream of bytes.

Details

It aims to have the same API on all platforms, including windows. As an added bonus, the windows package does not use cgo, so you can cross compile for windows from another platform.

You can cross compile with GOOS=windows GOARCH=386 go install github.com/tarm/serial

Currently there is very little in the way of configurability. You can set the baud rate. Then you can Read(), Write(), or Close() the connection. By default Read() will block until at least one byte is returned. Write is the same.

Currently all ports are opened with 8 data bits, 1 stop bit, no parity, no hardware flow control, and no software flow control. This works fine for many real devices and many faux serial devices including usb-to-serial converters and bluetooth serial ports.

You may Read() and Write() simulantiously on the same connection (from different goroutines).

Usage

package main

import (
        "log"

        "github.com/tarm/serial"
)

func main() {
        c := &serial.Config{Name: "COM45", Baud: 115200}
        s, err := serial.OpenPort(c)
        if err != nil {
                log.Fatal(err)
        }
        
        n, err := s.Write([]byte("test"))
        if err != nil {
                log.Fatal(err)
        }
        
        buf := make([]byte, 128)
        n, err = s.Read(buf)
        if err != nil {
                log.Fatal(err)
        }
        log.Printf("%q", buf[:n])
}

NonBlocking Mode

By default the returned Port reads in blocking mode. Which means Read() will block until at least one byte is returned. If that's not what you want, specify a positive ReadTimeout and the Read() will timeout returning 0 bytes if no bytes are read. Please note that this is the total timeout the read operation will wait and not the interval timeout between two bytes.

	c := &serial.Config{Name: "COM45", Baud: 115200, ReadTimeout: time.Second * 5}
	
	// In this mode, you will want to suppress error for read
	// as 0 bytes return EOF error on Linux / POSIX
	n, _ = s.Read(buf)

Possible Future Work

  • better tests (loopback etc)