On Mon, Jan 26, 2015 at 04:37:25PM +0100, Michael Zimmermann wrote: > Hi, > > I want to use the usb_debug serial driver as a UART shell on my > (embedded) device, because I just want to use it as a console(without > a complex protocol so I can easily use putchar and getchar functions). > > This seems to work pretty good except for two things. > Once upon establishing a connection I receive these data(send in > 4-word chunks, that's why the address is always the same): > 0x893d2600: 00000041 00000000 00000000 00000000 |A...............| > 0x893d2600: 00000054 00000000 00000000 00000000 |T...............| > 0x893d2600: 0000000d 00000000 00000000 00000000 |................| > 0x893d2600: 00000041 00000000 00000000 00000000 |A...............| > 0x893d2600: 00000054 00000000 00000000 00000000 |T...............| > 0x893d2600: 0000000d 00000000 00000000 00000000 |................| > 0x893d2600: 00000041 00000000 00000000 00000000 |A...............| > 0x893d2600: 00000054 00000000 00000000 00000000 |T...............| > 0x893d2600: 0000000d 00000000 00000000 00000000 |................| > 0x893d2600: f078007e 0000007e 00000000 00000000 |~.x.~...........| > 0x893d2600: f078007e 0000007e 00000000 00000000 |~.x.~...........| > > Is that some kind of initialization protocol I have to handle? If yes, > where do I find information about it?
The protocol should be part of the USB specification. > Another problem is that once the device got closed(by the screen command > i.e.). > I can't communicate with the device anymore. I've found that screen can leave usb serial ports in an "odd" state, it's not unique to this specific device, I blame the screen command :) greg k-h -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
