Skip to content

Commit 8d30887

Browse files
Copilot_Lite: Add the factory testing procedure
Signed-off-by: Adrien Ricciardi <aricciardi@baylibre.com>
1 parent 2ae4f17 commit 8d30887

2 files changed

Lines changed: 45 additions & 0 deletions

File tree

Copilot_Lite/Factory_Testing.md

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
# Factory testing
2+
3+
The board comes from the factory, fully assembled but without any jumper.
4+
5+
The test setup is made of :
6+
7+
* A Linux PC running Debian
8+
* An USB 3.x/2.0 hub.
9+
* Two USB-C cables, one of them being *USB 3.x* compliant. The second one can be only *USB 2.0* compliant.
10+
11+
## Serialization
12+
1. On the PC, run `sudo dmesg -wH` in a terminal.
13+
2. Connect the PC to the board `PC USB (J4)` connector through an USB-C cable (the cable can either be *USB 3.x* or *USB 2.0* compliant).
14+
1. The `PC USB (D2)` LED must light.
15+
2. The PC must detect a `FT230X Basic UART`.
16+
3. Disconnect the USB-C cable from the board only, flip it face-to-down and reconnect it to the board `PC USB` connector. The result must be identical to the previous step.
17+
4. Run the serialization tool with the command `sudo Copilot/Copilot_Lite/Software/Serialization/copilot-lite-serialize`.
18+
5. Disconnect and reconnect the USB-C cable from the board `PC USB` connector. The `dmesg` output must now display a `BayLibre Copilot Lite Vx.y` product.
19+
6. Make sure that the serialized version is matching the version written on the board PCB silkscreen.
20+
21+
You can close the terminal displaying the kernel console output once all boards have been successfully serialized.
22+
23+
## USB 3.0 passthrough
24+
25+
1. On the PC, run `sudo dmesg -wH | grep -i -e superspeed -e high-speed` in a terminal.
26+
2. Fit a jumper between pins 1 and 3 of the board `J1` pin header.
27+
3. Connect the board `PC USB (J4)` connector to the PC with an USB-C cable.
28+
1. The `PC USB (D2)` LED must light.
29+
2. The `USB (D3)` LED must light.
30+
4. Connect an *USB 3.x* USB hub to the `J9` USB-C connector.
31+
5. Connect a second USB-C cable from the PC to the board `J3` USB-C connector. Note that the cable **must** be *USB 3.x* compliant in order to the whether the board *USB 3.0* SuperSpeed pairs are working.
32+
6. There are only two board USB-C connectors orientation that allow the power and the data to go through. Flip the `J3` and the `J9` cable orientation one after the other, the USB hub must be detected in two of the four possible combinations.
33+
7. Each time that the USB hub is detected, make sure that the PC kernel console is detecting both *SuperSpeed* and *high-speed* internal USB hubs. This proves that either the *USB 3.0* and the *USB 2.0* board signals are working.
34+
35+
## Connecting jumpers
36+
37+
1. Remove any testing jumper from the board.
38+
2. `J1` pin header :
39+
1. Fit a jumper horizontally between pins 3 and 5.
40+
2. Fit a jumper horizontally between pins 4 and 6.
41+
3. `J11` pin header :
42+
1. Fit a jumper horizontally between pins 2 and 3.
43+
4. `J12` pin header :
44+
1. Fit a jumper vertically between pins 3 and 4.

README.rst

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -12,6 +12,7 @@ The generated HTML pages can be viewed `here <https://baylibre.github.io/Copilot
1212
The board hardware files are in the ``Copilot_Lite/Hardware`` folder.
1313

1414
The FTDI chip is configured and serialized by the ``Serialization`` software located in the ``Copilot_Lite/Software`` folder.
15+
The boards serialization and test procedure is described in the ``Copilot_Lite/Factory_Testing.md`` file.
1516

1617
Doc build instructions
1718
----------------------

0 commit comments

Comments
 (0)