This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

PPK and automated testing

Hi,

I'm thinking about implementing automated testing of current consumption using the PPK, and in the PPK blog it says: "We are planning on also making a Python API that developers can use to create their own automated tests by using this hardware. "

How are those plans going? :) My option is of course to reverse engineer the python code (which I dont really mind), but if there are a documented API on the way I would prefer using that.

Btw, PPK is an awesome tool! I use it for all sorts of projects (not just nRF stuff). A small feature request though, it would be nice to be able to choose the Emulator to use (i.e. calling self.nrfjprog.connect_to_emu_with_snr(serial_number=, jlink_speed_khz=JLINK_SPEED_KHZ) instead of self.nrfjprog.connect_to_emu_without_snr(jlink_speed_khz=JLINK_SPEED_KHZ) in rtt.py). Until i hacked the rtt.py file i constantly connected to the DUT instead of the DK.

BR Henrik

  • The API for the PPK has been lagging a bit behind unfortunately, due to other updates. Maybe this answer will help you getting started a bit faster. At this time, I cannot give you an exact answer to when we will release an API for it.

    With regards to connect_to_emu_without_snr(), JLink should pop up a dialog where you can choose your preferred debugger connection if you have several connected. You don't have this? To me, it seems a bit of a hassle to have to give the serial number manually every time, say in case you swap between several DK's to measure different stuff.

    Very nice to hear that you like the tool! There are still lots of improvements to come, so stay tuned :)

  • Thanks for your answer, I will have a look at that thread.

    I think the JLink popup is a Windows thing only unfortunately, in Linux (at least for me) it just connects / flashes to the first device it recognizes it seems. I agree that my current solution (the rtt.py hack) is not suitable for everyone, so it's nice that the code is open. :) I will most likely regret my hack when I change DK in a year or so and nothing works...

    Looking forward to the new features!

Related