samples/subsys/usb/testusb/README.html · samples/subsys/usb/testusb/README.rst 공식 원문 ↗

Zephyr 3.7.0 · Samples · testusb

USB Testing Application

Gadget Zero 호환 interface를 등록하고 control·bulk test 전체를 실행합니다.

Official pathsamples/subsys/usb/testusb/README.html
Source filesamples/subsys/usb/testusb/README.rst
Source versionZephyr 3.7.0
TranslationFull · reviewed

본문 기준: Zephyr 3.7.0 LTS3 · 이후 유지보수 패치는 별도입니다.

Part 1

요약·해설

VID/PID module load, new_id 등록과 test 0~29 실행을 설명합니다.

Kernel

usbtest module

Userspace

testusb

Reference

Gadget Zero

Part 2

접을 수 있는 영어 원문 전체

영어 원문 전체 펼치기
원문 SHA-256 77829E4673105931E7035B0778D4746FB97837CD45ED394D8FF3A543457768D7
.. zephyr:code-sample:: testusb-app
   :name: USB testing application
   :relevant-api: _usb_device_core_api

   Test USB device drivers using a loopback function.

This sample implements a loopback function that can be used
to test USB device drivers and the device stack connected to a Linux host
and has a similar interface to "Gadget Zero" of the Linux kernel.
The userspace tool ``testusb`` is needed to start the tests.

Building and flashing
*********************

Follow the general procedure for building and flashing Zephyr device.

Testing
*******

To run USB tests:

#. Load the ``usbtest`` Linux kernel module on the Linux Host.

   .. code-block:: console

      $ sudo modprobe usbtest vendor=0x2fe3 product=0x0009

   The ``usbtest`` module should claim the device:

   .. code-block:: console

      [21746.128743] usb 9-1: new full-speed USB device number 16 using uhci_hcd
      [21746.303051] usb 9-1: New USB device found, idVendor=2fe3, idProduct=0009, bcdDevice= 2.03
      [21746.303055] usb 9-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
      [21746.303058] usb 9-1: Product: Zephyr testusb sample
      [21746.303060] usb 9-1: Manufacturer: ZEPHYR
      [21746.303063] usb 9-1: SerialNumber: 86FE679A598AC47A
      [21746.306149] usbtest 9-1:1.0: matched module params, vend=0x2fe3 prod=0x0009
      [21746.306153] usbtest 9-1:1.0: Generic USB device
      [21746.306156] usbtest 9-1:1.0: full-speed {control} tests

#. Use the ``testusb`` tool in ``linux/tools/usb`` inside Linux kernel source directory
   to start the tests.

   .. code-block:: console

      $ sudo ./testusb -D /dev/bus/usb/009/016
      /dev/bus/usb/009/016 test 0,    0.000007 secs
      /dev/bus/usb/009/016 test 9,    4.994475 secs
      /dev/bus/usb/009/016 test 10,   11.990054 secs

#. To run all the tests the Zephyr's VID / PID should be inserted to USB
   driver id table. The method for loading the ``usbtest`` driver for our
   device is described here: https://lwn.net/Articles/160944/.

   Since we use the "Gadget Zero" interface we specify reference device
   ``0525:a4a0``.

   .. code-block:: console

      $ sudo sh -c "echo 0x2fe3 0x0009 0 0x0525 0xa4a0 > /sys/bus/usb/drivers/usbtest/new_id"

#. Use the ``testusb`` tool in ``linux/tools/usb`` inside Linux kernel source directory
   to start the tests.

   .. code-block:: console

      $ sudo ./testusb -v 512 -D /dev/bus/usb/009/016
      /dev/bus/usb/009/017 test 0,    0.000008 secs
      /dev/bus/usb/009/017 test 1,    2.000001 secs
      /dev/bus/usb/009/017 test 2,    2.003058 secs
      /dev/bus/usb/009/017 test 3,    1.054082 secs
      /dev/bus/usb/009/017 test 4,    1.001010 secs
      /dev/bus/usb/009/017 test 5,   57.962142 secs
      /dev/bus/usb/009/017 test 6,   35.000096 secs
      /dev/bus/usb/009/017 test 7,   30.000063 secs
      /dev/bus/usb/009/017 test 8,   18.000159 secs
      /dev/bus/usb/009/017 test 9,    4.984975 secs
      /dev/bus/usb/009/017 test 10,   11.991022 secs
      /dev/bus/usb/009/017 test 11,   17.030996 secs
      /dev/bus/usb/009/017 test 12,   17.103034 secs
      /dev/bus/usb/009/017 test 13,   18.022084 secs
      /dev/bus/usb/009/017 test 14,    2.458976 secs
      /dev/bus/usb/009/017 test 17,    2.001089 secs
      /dev/bus/usb/009/017 test 18,    1.998975 secs
      /dev/bus/usb/009/017 test 19,    2.010055 secs
      /dev/bus/usb/009/017 test 20,    1.999911 secs
      /dev/bus/usb/009/017 test 21,    2.440972 secs
      /dev/bus/usb/009/017 test 24,   55.112078 secs
      /dev/bus/usb/009/017 test 27,   56.911052 secs
      /dev/bus/usb/009/017 test 28,   34.163089 secs
      /dev/bus/usb/009/017 test 29,    3.983999 secs

Part 3

한국어 전문 번역

이 sample은 Linux host에 연결된 USB device driver와 device stack을 시험하는 loopback 기능을 구현합니다. Interface는 Linux kernel의 ‘Gadget Zero’와 비슷하며 test를 시작하려면 userspace testusb tool이 필요합니다.

빌드 및 flash

Zephyr device의 일반적인 build 및 flash 절차를 따릅니다.

테스트

다음 순서로 USB test를 실행합니다.

  1. Linux host에서 vendor ID 0x2fe3, product ID 0x0009를 지정해 usbtest kernel module을 load합니다.

    $ sudo modprobe usbtest vendor=0x2fe3 product=0x0009

    usbtest module이 device를 claim하면 enumeration 정보, matched module parameter와 full-speed control test 지원이 kernel log에 나타납니다.

    [21746.128743] usb 9-1: new full-speed USB device number 16 using uhci_hcd
    [21746.303051] usb 9-1: New USB device found, idVendor=2fe3, idProduct=0009, bcdDevice= 2.03
    [21746.303055] usb 9-1: New USB device strings: Mfr=1, Product=2, SerialNumber=3
    [21746.303058] usb 9-1: Product: Zephyr testusb sample
    [21746.303060] usb 9-1: Manufacturer: ZEPHYR
    [21746.303063] usb 9-1: SerialNumber: 86FE679A598AC47A
    [21746.306149] usbtest 9-1:1.0: matched module params, vend=0x2fe3 prod=0x0009
    [21746.306153] usbtest 9-1:1.0: Generic USB device
    [21746.306156] usbtest 9-1:1.0: full-speed {control} tests
  2. Linux kernel source directory의 linux/tools/usb에 있는 testusb tool을 사용해 device node의 test를 시작합니다. 이 기본 실행에서는 test 0, 9, 10의 시간을 확인합니다.

    $ sudo ./testusb -D /dev/bus/usb/009/016
    /dev/bus/usb/009/016 test 0,    0.000007 secs
    /dev/bus/usb/009/016 test 9,    4.994475 secs
    /dev/bus/usb/009/016 test 10,   11.990054 secs
  3. 모든 test를 실행하려면 Zephyr VID/PID를 USB driver ID table에 삽입해야 합니다. 이 sample은 Gadget Zero interface를 사용하므로 reference device로 0525:a4a0을 지정합니다. Driver load 방식은 LWN 설명을 참고합니다.

    $ sudo sh -c "echo 0x2fe3 0x0009 0 0x0525 0xa4a0 > /sys/bus/usb/drivers/usbtest/new_id"
  4. 같은 testusb tool을 verbose transfer size 512로 다시 실행합니다. Output에는 test 0부터 29 가운데 지원되는 control·bulk·loopback test의 실행 시간이 차례로 나타납니다.

    $ sudo ./testusb -v 512 -D /dev/bus/usb/009/016
    /dev/bus/usb/009/017 test 0,    0.000008 secs
    /dev/bus/usb/009/017 test 1,    2.000001 secs
    /dev/bus/usb/009/017 test 2,    2.003058 secs
    /dev/bus/usb/009/017 test 3,    1.054082 secs
    /dev/bus/usb/009/017 test 4,    1.001010 secs
    /dev/bus/usb/009/017 test 5,   57.962142 secs
    /dev/bus/usb/009/017 test 6,   35.000096 secs
    /dev/bus/usb/009/017 test 7,   30.000063 secs
    /dev/bus/usb/009/017 test 8,   18.000159 secs
    /dev/bus/usb/009/017 test 9,    4.984975 secs
    /dev/bus/usb/009/017 test 10,   11.991022 secs
    /dev/bus/usb/009/017 test 11,   17.030996 secs
    /dev/bus/usb/009/017 test 12,   17.103034 secs
    /dev/bus/usb/009/017 test 13,   18.022084 secs
    /dev/bus/usb/009/017 test 14,    2.458976 secs
    /dev/bus/usb/009/017 test 17,    2.001089 secs
    /dev/bus/usb/009/017 test 18,    1.998975 secs
    /dev/bus/usb/009/017 test 19,    2.010055 secs
    /dev/bus/usb/009/017 test 20,    1.999911 secs
    /dev/bus/usb/009/017 test 21,    2.440972 secs
    /dev/bus/usb/009/017 test 24,   55.112078 secs
    /dev/bus/usb/009/017 test 27,   56.911052 secs
    /dev/bus/usb/009/017 test 28,   34.163089 secs
    /dev/bus/usb/009/017 test 29,    3.983999 secs

Source

출처

영어 원문에는 문단, 문서 지시문, 표, 코드, 코드 심벌, 경로를 그대로 보존했습니다.