• State Not Answered
  • Replies 6 replies
  • Subscribers 90 subscribers
  • Views 2541 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 220779
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

OTA Final Production Testing

jumpingfool

We are preparing a product (based on nRF52840) for manufacturing and currently defining the production test process.

The product is hermetically sealed with no external ports and so it is not possible to access the UART for DTM during final test. We are therefore exploring options to test the product OTA.

We have reviewed the whitepaper describing an OTA testing approach using the LiteOn Bluetooth Advanced tester at:

http://infocenter.nordicsemi.com/pdf/nwp_028.pdf

The BLE_SMART_TX_RX_PER test looks to be an excellent fit for our requirements.

However, we also need to write configuration information over BLE to the product (serial number, etc), with a Windows based PC acting as a central. So to optimise the test flow we would like to understand if we can reasonably use the PC in place of the LiteOn equipment for functional testing.

If so what operations between the PC and product would be recommended to ensure maximum verification confidence? We propose to check advertising RSSI then connect and time a data transfer burst, comparing performance a against a golden sample. Anything else we would consider? Any risks with this approach?

Parents
  • 0

    Hi ,

    What instrument have you used for your test ?

    I need a final production test too but I am not sure how to realize and which instrument.

  • 0 in reply to lucaross

    Hi,

     

    The equipment we use is not relevant as we test in sockets (i.e. not soldered on PCBs) and perform much more comprehensive testing than you will be doing (and way more expensive than necessary).

    For a lot of the tests you can probably use the nRF52 or the other devices on the board. You can write a program that uses GPIOs, serial interfaces or similar, depending on what you are using, to distinguish an faulty unit from a good one by doing test reads or something. You can also pull lines high/low and measure the voltage, rise time etc. by probing test points using a voltage meter or oscilloscope. First step is anyway figuring out what is on your board and what you need to actually test.

     

    Best regards,

    Andreas

Reply
  • 0 in reply to lucaross

    Hi,

     

    The equipment we use is not relevant as we test in sockets (i.e. not soldered on PCBs) and perform much more comprehensive testing than you will be doing (and way more expensive than necessary).

    For a lot of the tests you can probably use the nRF52 or the other devices on the board. You can write a program that uses GPIOs, serial interfaces or similar, depending on what you are using, to distinguish an faulty unit from a good one by doing test reads or something. You can also pull lines high/low and measure the voltage, rise time etc. by probing test points using a voltage meter or oscilloscope. First step is anyway figuring out what is on your board and what you need to actually test.

     

    Best regards,

    Andreas

Children
No Data
Related