I just installed the Android App "Serial USB Terminal" on a Samsung S7 and attached it via an FTDI adapter.https://play.google.com/s...usb_terminal&hl=enBe sure to use a USB OTG adapter
/ cable, if not already supplied with your phone.
from the description: To connect USB to serial converters, your android device must support USB OTG aka. USB host mode.
For a self written debug-monitor my PIC24FJ...GB I can use both a simple serial port (usually connected via FTDI to an USB host = PC), but I can also use my PIC's USB / CDC (based on MLA code).
FTDI attached to the S7 works out of the box, no driver (automatic detection of FTDI), no hassle.
Then I attached my PIC's USB (i.e. CDC) to the phone. The App provides a menu which contains "USB devices" and this point will list an unknown / custom CDC device with Vendor ID (04D8) and Product ID (0057), i.e. this is Microchip.
the app then also offers a choice for the "Driver for unknown device"
If I choose CDC here (and later connect ... ) this works perfectly with my PIC24.
So at least for my configuration I did not have to install any driver for this on my Android 7 phone. No idea what possibly the App does behind the scenes, and whether it brings along those drivers listed above.
The App looks good, it also allows to define HEX byte sequences as strings.
edit: one itsy bitsy detail
This Android app seems to send the message body and the Newline character(s) in different USB packets. (or with a time gap?)
The Microchip USB stack function
uint8_t getsUSBUSART(uint8_t *buffer, uint8_t len)
in my case will first retrieve the body, and on the next call it will get the selected Newline character(s).
post edited by rodims - 2018/02/09 12:53:15