• State Not Answered
  • Replies 3 replies
  • Subscribers 88 subscribers
  • Views 56 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 360109
Options

using Power Profiler with PPK2 and nRF52840

roy0

I'm using the PPK2 to develop a product with this device: https://wiki.seeedstudio.com/xiao_nrf52840&_wio_SX1262_kit_for_meshtastic/

Specifically, I am using the Digital Channels (Logic Analyzer) to view some pins on initial power up.  I have already STARTED the trace, and I'm ready to power up the device over USB.

However, when I plug in the nRF52840 to USB, the Power Profiler RESETS, and I am unable to capture the Digital Channels I am interested in.

It seems like the Power Profiler is reseting because it detects the nRF52840, whereas I was already connected to the PPK2 and ready to make the measurements before the reset.  I am not interested in the Power Profiler connecting to the nRF52840.  (The USB connection with my laptop is required for serial debug.)

I hope this is a sufficient description of the problem.

Thanks in advance for any help.

Parents
  • 0

    specific steps to reproduce this: (note it only happens sometimes .... MOST of the time)


    setup:

    - using this product: XIAO nRF52840 & Wio-SX1262 Kit with PPK2 (https://wiki.seeedstudio.com/xiao_nrf52840&_wio_SX1262_kit_for_meshtastic/)

    - PPK2 plugged into MacOS (Tahoe) laptop, running Power Profiler 4.3.1

    - only Logic Port hooked up to DUT.  No use of current measurement

    steps:

    1. PPK2 plugged into laptop and running; DUT unpowered 
    2. START trace on PPK2 --> trace starts running live
    3. plug DUT into the same laptop via USB
    4. --> trace STOPS dead, and Power Profiler ask to Select Device again

    Two Log traces below ...

    Log trace #1:

    18:16:50.950
    Initialising the bundled nrfutil device
    18:16:51.237
    Using the bundled core version for nrfutil device: 8.0.0
    18:16:51.264
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:16:51.265
    Device connected with the serial number CA68583CD84B
    18:16:51.342
    Using nrfutil-device version: 2.10.2
    18:16:51.342
    Using nrf-device-lib version: 0.17.71
    18:16:51.342
    Using nrf-probe version: 0.38.0
    18:16:51.342
    Using JLink version: JLink_V9.24a
    18:16:51.342
    Your version of SEGGER J-Link (9.24a) is newer than the one this app was tested with (8.18). The tested version is not required, and your J-Link version will most likely work fine. If you get issues related to J-Link with your devices, use the tested version.
    18:17:39.147
    Selecting device with the serial number CA68583CD84B
    18:17:39.282
    Selected device with the serial number CA68583CD84B
    18:17:39.283
    Connected to the device with the serial number CA68583CD84B and family: Unknown
    18:17:39.459
    PPK started
    18:17:39.460
    PPK opened
    18:17:51.805
    Device connected with the serial number CA68583CD84B
    18:17:51.805
    PPK closed
    18:17:52.229
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:17:52.230
    Device connected with the serial number CA68583CD84B
    18:17:52.461
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:17:52.466
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:17:52.757
    Getting serial port options from the persistent store for 6FAD1EF504394AC7.pc-nrfconnect-ppk
    18:17:52.758
    Device connected with the serial number 6FAD1EF504394AC7
    18:18:25.584
    Device connected with the serial number 6FAD1EF504394AC7
    18:18:27.382
    Selecting device with the serial number CA68583CD84B
    18:18:27.516
    Selected device with the serial number CA68583CD84B
    18:18:27.517
    Connected to the device with the serial number CA68583CD84B and family: Unknown
    18:18:27.692
    PPK started
    18:18:27.692
    PPK opened
    ===================================================
    Log trace #2:

    18:32:55.315
    Selecting device with the serial number CA68583CD84B
    18:32:55.452
    Selected device with the serial number CA68583CD84B
    18:32:55.452
    Connected to the device with the serial number CA68583CD84B and family: Unknown
    18:32:55.612
    PPK started
    18:32:55.612
    PPK opened
    18:33:01.872
    Device connected with the serial number 6FAD1EF504394AC7
    18:33:08.685
    Device connected with the serial number CA68583CD84B
    18:33:08.686
    PPK closed
    18:33:08.723
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:33:08.724
    Device connected with the serial number CA68583CD84B
    18:33:08.960
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:33:08.969
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:33:09.513
    Getting serial port options from the persistent store for 6FAD1EF504394AC7.pc-nrfconnect-ppk
    18:33:09.513
    Device connected with the serial number 6FAD1EF504394AC7
    18:33:13.350
    Selecting device with the serial number CA68583CD84B
    18:33:13.489
    Selected device with the serial number CA68583CD84B
    18:33:13.489
    Connected to the device with the serial number CA68583CD84B and family: Unknown
    18:33:13.648
    PPK started
    18:33:13.648
    PPK opened
    18:33:19.795
    Device connected with the serial number 6FAD1EF504394AC7
    18:33:23.890
    Device connected with the serial number CA68583CD84B
    18:33:23.890
    PPK closed
    18:33:24.317
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:33:24.317
    Device connected with the serial number CA68583CD84B
    18:33:24.555
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:33:24.568
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:33:24.857
    Getting serial port options from the persistent store for 6FAD1EF504394AC7.pc-nrfconnect-ppk
    18:33:24.857
    Device connected with the serial number 6FAD1EF504394AC7
    18:34:48.981
    Selecting device with the serial number CA68583CD84B
    18:34:49.124
    Selected device with the serial number CA68583CD84B
    18:34:49.124
    Connected to the device with the serial number CA68583CD84B and family: Unknown
    18:34:49.296
    PPK started
    18:34:49.296
    PPK opened
    18:34:57.587
    Device connected with the serial number 6FAD1EF504394AC7
    18:35:02.213
    Device connected with the serial number CA68583CD84B
    18:35:02.214
    PPK closed
    18:35:02.638
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:35:02.638
    Device connected with the serial number CA68583CD84B
    18:35:02.873
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:35:02.879
    Getting serial port options from the persistent store for CA68583CD84B.pc-nrfconnect-ppk
    18:35:03.149
    Getting serial port options from the persistent store for 6FAD1EF504394AC7.pc-nrfconnect-ppk
    18:35:03.149
    Device connected with the serial number 6FAD1EF504394AC7
  • 0 in reply to roy0

    Hi,

    This is indeed a quite strange. My guess is that your computer is struggling to keep the USB power at the needed voltage when you connect your device.

    Did you try using another source to power your board as Turbo J suggested?

    Can you maybe share a picture or a schematic of your setup to see if I can see anything abnormal?

    Also, does your hardware have some device connected to it that would draw some current when the USB gets plugged in (screen, motors, LEDs, ...)?

    And last, does the PPK2 also disconnects when you plug your device USB if the PPK2 is not connected to your board (only connected to your computer)?

    Best regards,

    Simon D-M

Reply
  • 0 in reply to roy0

    Hi,

    This is indeed a quite strange. My guess is that your computer is struggling to keep the USB power at the needed voltage when you connect your device.

    Did you try using another source to power your board as Turbo J suggested?

    Can you maybe share a picture or a schematic of your setup to see if I can see anything abnormal?

    Also, does your hardware have some device connected to it that would draw some current when the USB gets plugged in (screen, motors, LEDs, ...)?

    And last, does the PPK2 also disconnects when you plug your device USB if the PPK2 is not connected to your board (only connected to your computer)?

    Best regards,

    Simon D-M

Children
No Data
Related
Terms of service