USB Gadget/Serial

= USB serial gadget =

This gadget allows your devices act as a serial port device. The gadget serial driver talks over USB to either a CDC ACM driver or a generic USB serial driver running on a host PC. This guide demonstrates a way to use the gadget driver as a poor man's serial port debugging tool. One downside of this approach is that the driver does not activate immediately when booting the kernel. The early boot messages (bootloader, kernel) will not be printed via this serial device, but the kernel messages can be accessed e.g. via 'dmesg' in case the system is able to boot to the command prompt.

Kernel support
Currently, the g_serial module is not compiled as part of default kernel configuration. Here we assume the user wants to compile the support in the kernel, not as a module

Device Drivers USB support <*>  Inventra Highspeed Dual Role Controller (TI, ADI, AW, ...) MUSB Mode Selection (Dual Role mode) *** Platform Glue Layer *** <*>    Allwinner (sunxi) <*>  USB Gadget Support [*]  Serial gadget console support <*>  USB Gadget precomposed configurations (Serial Gadget (with CDC ACM and CDC OBEX support))

Make sure you use the dual role mode for MUSB unless the device tree configuration has been updated accordingly. Otherwise the system might fail to set up the device, complaining about an invalid or missing 'dr_mode' property.

You can now continue following manual build howto to continue kernel compilation and installation.

Preparing the gadget device
The serial device shows up as /dev/ttyGS0 on the gadget device. You can redirect kernel messages to this device by changing the kernel command line: setenv bootargs "console=ttyS0,115200 console=ttyGS0,115200 init=/usr/lib/systemd/systemd"

In case the host machine runs Linux, the serial device might show up as /dev/ttyACM0 or something similar. You can use minicom to communicate with the gadget device: minicom -D /dev/ttyACM0