XO 4 Touch Testing: Difference between revisions
No edit summary |
|||
Line 12: | Line 12: | ||
''After testing is complete, the MSP430 should probably be placed into reset to allow for cable disconnect. It should be rebooted for each test.'' |
''After testing is complete, the MSP430 should probably be placed into reset to allow for cable disconnect. It should be rebooted for each test.'' |
||
select /touchscreen |
|||
0 to faults test-os |
|||
faults if green-screen else red-screen then |
|||
touch-rst-gpio# gpio-clr |
|||
key drop |
|||
==IR PCB ASSY== |
==IR PCB ASSY== |
||
Line 25: | Line 31: | ||
''After testing is complete, the MSP430 should probably be placed into reset to allow for cable disconnect. It should be rebooted for each test.'' |
''After testing is complete, the MSP430 should probably be placed into reset to allow for cable disconnect. It should be rebooted for each test.'' |
||
* can be done now with revision A IR PCBA if the finger or stylus is omitted: |
|||
select /touchscreen |
|||
0 to faults test-fss |
|||
faults if green-screen else red-screen then |
|||
touch-rst-gpio# gpio-clr |
|||
key drop |
|||
* waiting on revision B IR PCBA for implementation: |
|||
select /touchscreen |
|||
0 to faults test-edges |
|||
faults if green-screen else red-screen then |
|||
touch-rst-gpio# gpio-clr |
|||
key drop |
|||
==MB SMT== |
==MB SMT== |
||
Line 31: | Line 51: | ||
==Lightguide Tooling== |
==Lightguide Tooling== |
||
==Field== |
|||
test /touchscreen |
|||
[[Category:Hardware]] |
[[Category:Hardware]] |
Revision as of 04:17, 28 August 2012
This page describes the production test support provided with the touchscreen in XO-4.
Test routines are provided in Open Firmware for testing the various components of the touchscreen system, at various stages of manufacture.
IR PCB SMT
This test is done to bare IR PCB boards, without a light guide. The code runs on XO-4 A2 or later motherboards.
The idea is to check for opens and shorts of the IR diodes and detectors, as well as proper mounting of the ASIC and connector on the IR PCB.
There should be no operator interaction with the IR PCB. They should simply be able to drop a board into the test fixture, press a button on the keyboard, and the screen says pass or fail with an appropriate background (red/green).
After testing is complete, the MSP430 should probably be placed into reset to allow for cable disconnect. It should be rebooted for each test.
select /touchscreen 0 to faults test-os faults if green-screen else red-screen then touch-rst-gpio# gpio-clr key drop
IR PCB ASSY
This test is done to IR PCB assemblies, including a light guide and bezel. The code runs on XO-4 A2 or later motherboards in a production line situation, using a test fixture to connect to the bezel assembly.
The idea is to check for proper assembly of the lightguide and IR PCB, as well as proper lightguide and IR PCB operation.
They should simply be able to drop a bezel assembly into the test fixture, and press a button on the keyboard. They then need to pass a finger or stylus along two adjacent inside edges of the bezel to complete the test. Upon completion, the screen says pass or fail with an appropriate background (red/green). There should be an automatic abort of the test (w. fail) if the appropriate motion isn't detected within thirty seconds.
After testing is complete, the MSP430 should probably be placed into reset to allow for cable disconnect. It should be rebooted for each test.
- can be done now with revision A IR PCBA if the finger or stylus is omitted:
select /touchscreen 0 to faults test-fss faults if green-screen else red-screen then touch-rst-gpio# gpio-clr key drop
- waiting on revision B IR PCBA for implementation:
select /touchscreen 0 to faults test-edges faults if green-screen else red-screen then touch-rst-gpio# gpio-clr key drop
MB SMT
MB ASSY
Lightguide Tooling
Field
test /touchscreen