• State Not Answered
  • Replies 6 replies
  • Subscribers 69 subscribers
  • Views 143 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 337235
Options

AutoPTS setup on nrf5340

Ran531

Hello,

We are trying to test our product for qualification purposes. I found documentation for configuring a Windows environment on the nrf52 series and trying to apply it to nrf5340.

The project sits in zephyr/tests/bluetooth/tester, and seems like it has an overlay and .conf files appropriate for the nrf5340, but the README lacks information on how to actually flash it.

there are some references to hci_ipc (ipc_radio in the newer SDK?) but the network core image does not get built like it does in the various sample projects that use Bluetooth. I am hoping you can give me some pointers on how to set everything up so we can run some of the tests via AutoPTS.

I have seen some relevant discussion in case 334059.

Thanks!

Parents Reply
  • 0 in reply to Asbjørn

    Hi,

    Yes I am using that repository to run PTS client on my mac connected to the nrf5340 dev kit (initialized with -b nrf53 and -t /dev/tty.usbmodem....), and the PTS server on a Windows machine with a dual PTS dongle. As I understand, the PTS client connects to the Windows server and forwards the HCI tests to the nrf5340 over the serial port, and the Windows server also tests the actual radio. 

    As i mentioned earlier, the nrf5340 is flashed with zephyr/tests/bluetooth/tester.

    I am following this guide referenced in the repository you mentioned: docs.zephyrproject.org/.../autopts-linux.html

Children
  • 0 in reply to Ran531
    Hi Ran,
    We haven't tested this suite ourselves, so it's a bit limited what we know. I see that there are a few optional steps in the installation and selection points. 
    • Am I correct in understanding that all the steps in "AutoPTS on Linux"  are done and they all install as intended? 
    • Are you using a virtual Windows setup and are you able to connect the boards to that environment?
      • usb.autoConnect.device0 = "0x0a12:0x0001"
      • just replace 0x0a12 with Vendor number and 0x0001 with ProdID number you found earlier.
    • You managed to compile the FW in zephyr/tests/bluetooth/tester for nRF5340? Does the FW start correctly? Are you seeing printed output or see the program counter change?
    • Did you build the example for nrf5340dk/nrf5340/cpuapp or nrf5340dk/nrf5340/cpuapp/ns
     Best regards
    Asbjørn
  • 0 in reply to Asbjørn

    This tester project in zephyr has some references to the nrf53 and 54 series via .overlay and .conf.

    I am using an actual Windows machine and not a VM. The PTS dongle is connected to that machine and the PTS software recognizes it.

    I managed to compile and build to nrf5340dk/nr5340/cpuapp (not ns). I know it runs since when I spam the uart (it reads commands through it) it prints "[00:01:55.353,576] <err> bttester: BT tester: invalid packet length" on the RTT. 

    Perhaps we can schedule a meeting on how to make this (or any other way of running qualification tests) work. I would very much appreciate it if we can go through the configuration and double check it.

    Thanks,

Related