Extend USB trace logic. When we are configured to decode and stringify trace data, de-stringification support is not included for class driver trace output

This commit is contained in:
Gregory Nutt
2013-09-06 17:24:02 -06:00
parent 15ecbb9ab4
commit fe285f6d16
+6
View File
@@ -1053,6 +1053,7 @@ Configurations
Device Drivers -> "USB Device Driver Support: Device Drivers -> "USB Device Driver Support:
CONFIG_USBDEV_TRACE=y : Enable USB trace feature CONFIG_USBDEV_TRACE=y : Enable USB trace feature
CONFIG_USBDEV_TRACE_NRECORDS=256 : Buffer 256 records in memory CONFIG_USBDEV_TRACE_NRECORDS=256 : Buffer 256 records in memory
CONFIG_USBDEV_TRACE_STRINGS=y : (optional)
Application Configuration -> NSH LIbrary: Application Configuration -> NSH LIbrary:
CONFIG_NSH_USBDEV_TRACE=n : No builtin tracing from NSH CONFIG_NSH_USBDEV_TRACE=n : No builtin tracing from NSH
@@ -1074,6 +1075,11 @@ Configurations
asynchronous with the trace output and, hence, difficult to asynchronous with the trace output and, hence, difficult to
interpret. interpret.
STATUS:
2013-9-6: I have not confirmed this, but it appears that the AT25 does not
retain its formatting across power cycles. I need to study this more.
2013-9-6: The mass storage class is not yet working.
hello: hello:
This configuration directory, performs the (almost) simplest of all This configuration directory, performs the (almost) simplest of all
possible examples: examples/hello. This just comes up, says hello possible examples: examples/hello. This just comes up, says hello