Used for communication between the Maple board and a computer.
Contents
In addition to three serial ports, the Maple’s STM32 microprocessor includes a dedicated USB peripheral. This peripheral is used to emulate a regular serial port for use as a terminal. The emulated terminal is relatively slow; it is best for transferring data at regular serial speeds (kilobaud).
Library access to the emulated serial port is provided through the SerialUSB object. You can mostly use SerialUSB as a drop-in replacement for Serial1, Serial2, and Serial3.
Warning
The SerialUSB functionality includes a 50 millisecond timeout for writes, and does not try to detect if the USB host is “really” connected, or just enumerated and initialized.
This means that if you have a number of calls to one of the SerialUSB write() or print() functions in your code, and you are not monitoring SerialUSB on a computer, your program will run much slower than if it is being monitored or totally disconnected (run off of a battery).
You can avoid this behavior by deciphering the port status using the DTR and RTS line status (the behavior of these control lines is platform dependent and we no longer interpret them by default).
The SerialUSB object is an instance of the USBSerial class, which is documented in this section. This means that you can use any of these functions by writing SerialUSB.functionName(arguments...). For example, to print the message “hello, world!”, you can write USBSerial.println("hello, world!").
Emulated serial-over-USB class. SerialUSB is the predefined (singleton) instance.
Set up the USB peripheral for emulated serial communication. The peripheral is configured this way by default; calling this function should only be necessary if you have disabled the peripheral using SerialUSB.end().
Disables the USB peripheral. Note that using this function will terminate all USB communications between the Maple and the USB host; in particular, it implies that you won’t be able to upload any new programs without resetting the board or using perpetual bootloader mode.
Returns the number of bytes available for reading.
Returns the next available, unread character. If there are no available characters (you can check this with available), the call will block until one becomes available.
Print the given byte over the USB connection.
Print the given character over the USB connection. 7-bit clean characters are typically interpreted as ASCII text.
Print the given null-terminated string over the USB connection.
Print the argument’s digits over the USB connection, in decimal format. Negative values will be prefixed with a '-' character.
Print the argument’s digits over the USB connection, in decimal format.
Print the argument’s digits over the USB connection, in decimal format. Negative values will be prefixed with a '-' character.
Print the argument’s digits over the USB connection, in decimal format.
Print the digits of n over the USB connection, in base base (which may be between 2 and 16). The base value 2 corresponds to binary, 8 to octal, 10 to decimal, and 16 to hexadecimal. Negative values will be prefixed with a '-' character.
Like print(c), followed by "\r\n".
Like print(b), followed by "\r\n".
Like print(n), followed by "\r\n".
Like print(n), followed by "\r\n".
Prints "\r\n" over the USB connection.
Sends one character over the USB connection. This function is currently blocking, although nonblocking writes are a planned future extension.
This is a low-level function. One of the print() or println() functions is likely to be more useful when printing multiple characters, when formatting numbers for printing, etc.
Send the given null-terminated character string over the USB connection.
This is a low-level function. One of the print() or println() functions is likely to be more useful when printing multiple characters, when formatting numbers for printing, etc.
Writes the first size bytes of buf over the USB connection. Each byte is transmitted as an individual character.
This is a low-level function. One of the print() or println() functions is likely to be more useful when printing multiple characters, when formatting numbers for printing, etc.
Safe print: This function should run smoothly and not block; the LED should blink at roughly the same speed whether being monitored, running from battery, or connected but not monitored. You may need to experiment with the DTR/RTS logic for your platform and device configuration.
#define LED_PIN BOARD_LED_PIN
void setup() {
/* Set up the LED to blink */
pinMode(LED_PIN, OUTPUT);
}
void loop() {
// LED will stay off if we are disconnected, and will blink
// quickly if USB is unplugged (battery power, etc.).
if(SerialUSB.isConnected()) {
digitalWrite(LED_PIN, 1);
}
delay(100);
// If this logic fails to detect if bytes are going to be read
// by the USB host, then the println() take a long time,
// causing a very slow LED blink. If the characters are
// printed and read, the blink will only slow a small amount
// when "really" connected, and will be fast fast when the
// virtual port is only configured.
if(SerialUSB.isConnected() && (SerialUSB.getDTR() || SerialUSB.getRTS())) {
for(int i = 0; i < 10; i++) {
SerialUSB.println(123456, BIN);
}
}
digitalWrite(LED_PIN, 0);
delay(100);
}