Method for testing multiple data packet signal transceivers with a shared tester to maximize tester use and minimize test time
US-9319154-B2 · Apr 19, 2016 · US
US10296433B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-10296433-B2 |
| Application number | US-201213486471-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 1, 2012 |
| Priority date | Jun 1, 2012 |
| Publication date | May 21, 2019 |
| Grant date | May 21, 2019 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
A method for testing a device under test (DUT) during a test sequence. In accordance with one embodiment, during a regular, pre-defined test sequence, data packets are transferred from a tester to a device under test (DUT) containing data related to at least one of an identification parameter of the DUT, an operational characteristic of the DUT and a request for data. Examples of such transferred data include address data for identifying the DUT (e.g., a unique media access control (MAC) address) and calibration data for controlling an operational characteristic of the DUT (e.g., signal power levels, signal frequencies or signal modulation characteristics). In accordance with another embodiment, the DUT retrieves and transmits data to the tester, either in response to the request for data or as a preprogrammed response to its synchronization with the tester.
Opening claim text (preview).
What is claimed is: 1. A method for programming a device under test (DUT) during a test sequence, comprising: synchronizing a tester and a DUT, wherein said DUT has not yet been identified by a unique identification parameter; and following said synchronizing, receiving from said tester with said DUT data including a new unique identification parameter for said DUT; programming a non-volatile memory of said DUT with at least said new unique identification parameter of said DUT, followed by and independent of a signal from said tester, activating, with said DUT, said new unique identification parameter of said DUT, and transmitting, with said DUT, a data packet signal that includes said new unique identification parameter of said DUT. 2. The method of claim 1 , wherein said synchronizing a tester and a DUT comprises: transmitting, with said tester, a synchronization initiation signal; and transmitting, with said DUT, a synchronization confirmation signal. 3. The method of claim 1 , further comprising: following said synchronizing, transmitting, with said tester, a data signal including one or more data packets containing said new unique identification parameter of said DUT; transmitting, with said DUT, a response signal acknowledging receipt of said data signal by said DUT; and transmitting, with said DUT, another response signal in response to said request for data. 4. The method of claim 3 , wherein said transmitting, with said tester, a data signal including one or more data packets containing said new unique identification parameter of said DUT comprises transmitting, with said tester, address data for identifying said DUT. 5. The method of claim 3 , wherein said data packet transmitted by said DUT includes said new unique identification parameter of said DUT, and further comprising: decoding, with said tester, said data packet transmitted by said DUT; and comparing, with said tester, said decoded data packet and said new unique identification parameter of said DUT transmitted by said tester as part of said data signal. 6. The method of claim 1 , further comprising receiving, with said tester, said data packet transmitted by said DUT. 7. A method for programming a device under test (DUT) during a test sequence, comprising: receiving, with a DUT, a synchronization initiation signal from a tester, wherein said DUT has not yet been identified by a unique identification parameter; transmitting, with said DUT, a synchronization confirmation signal; and following said synchronization, receiving from said tester with said DUT data including a new unique identification parameter for said DUT; programming a non-volatile memory of said DUT with at least said new unique identification parameter of said DUT, followed by and independent of a signal from said tester, activating, with said DUT, said new unique identification parameter of said DUT, and transmitting, with said DUT, a data packet signal that includes said programmed data representing a unique identification parameter of said DUT. 8. The method of claim 7 , wherein said following said synchronization, receiving and programming data from said tester including said new unique identification parameter of said DUT comprises receiving, with said DUT from said tester, a data signal including one or more data packets containing said new unique identification parameter of said DUT or a request for data, and further comprising: transmitting, with said DUT, a response signal acknowledging receipt of said data signal by said DUT; or transmitting, with said DUT, another response signal in response to said request for data. 9. The method of claim 8 , wherein said receiving, from said tester with said DUT a data signal including one or more data packets containing said new unique identification parameter of said DUT or a request for data comprises receiving, with said DUT from said tester, address data for identifying said DUT.
Test interface between tester and unit under test · CPC title
Generation of test inputs, e.g. test vectors, patterns or sequences {; with adaptation of the tested hardware for testability with external testers} · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.