• State Verified Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 91 subscribers
  • Views 755 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 285850
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Current Measurement on nRF5340 DK

Frikkie Badenhorst

Hi there, 

We are currently doing current measurements on the nRF5340 DK with a Power Profiler Kit 2.

To do this, we simply use the PPK as a source meter and connect it to the "External Supply" pin. We also set SW10 to on (VEXT->nRF).

We leave the the USB connected to the interface MCU in order to communicate via UART.

However, we are measuring a current of 6mA for this which is quite high, as the only peripheral we are running is the RTC and the watchdog.

Could you please confirm whether this is the recommended way of measuring the current.

We have also tried measuring using the PPK as a ammeter, and connecting it to the measurement pin (p22) while using the USB as power source, however we are getting even higher readings using that method.

Please advise.

Regards,
Frikkie

Parents
  • 0

    Hi,

    Can you provide the PPK2 measurement files?

    What SW are you running on the 53DK ? is it one of our samples?


    Have you seen this guide:Optimizing Power on nRF5340 SoC Designs - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com)

    R    egards,
    Jonathan

  • 0 in reply to JONATHAN LL

    We are using our own custom, baremetal application (no Zephyr). In the application, we only have the RTC, Watchdog 0 and 1 UART enabled and running. 

    We have managed to place the device in System Off mode, in which case the system draws 2uA. I think this is expected, so I would believe our above method of measuring current is fine?

    JONATHAN LL said:
    Have you seen this guide:Optimizing Power on nRF5340 SoC Designs - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com)

    Thanks for referring me to this article, however we have created our own separate project (without a proj.conf file) as we are not going to use Zephyr. We want to have full control over the device and understand exactly in which state it is and when. I thus have a question regarding

    CONFIG_LOG=n 
    CONFIG_SERIAL=n

    and

    CONFIG_PM=y

    What exactly is serial logging and is it enabled by default? How would one disable it using firmware rather than editing a config file? If you could refer me to where this is written in the manuals, that should also be fine. Also, what is the firmware equivalent of CONFIG_PM=y?

    According to the Product Specification, the PMU is automatic, and you can only put the device in on of 3 states, 1) System On low power (which we are trying to achieve), System on constant latency and System off. How does CONFIG_PM=y fit in here?

    Regards,

    Frikkie

Reply
  • 0 in reply to JONATHAN LL

    We are using our own custom, baremetal application (no Zephyr). In the application, we only have the RTC, Watchdog 0 and 1 UART enabled and running. 

    We have managed to place the device in System Off mode, in which case the system draws 2uA. I think this is expected, so I would believe our above method of measuring current is fine?

    JONATHAN LL said:
    Have you seen this guide:Optimizing Power on nRF5340 SoC Designs - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com)

    Thanks for referring me to this article, however we have created our own separate project (without a proj.conf file) as we are not going to use Zephyr. We want to have full control over the device and understand exactly in which state it is and when. I thus have a question regarding

    CONFIG_LOG=n 
    CONFIG_SERIAL=n

    and

    CONFIG_PM=y

    What exactly is serial logging and is it enabled by default? How would one disable it using firmware rather than editing a config file? If you could refer me to where this is written in the manuals, that should also be fine. Also, what is the firmware equivalent of CONFIG_PM=y?

    According to the Product Specification, the PMU is automatic, and you can only put the device in on of 3 states, 1) System On low power (which we are trying to achieve), System on constant latency and System off. How does CONFIG_PM=y fit in here?

    Regards,

    Frikkie

Children
Related
Terms of service