Is nrf at all production friendly?

[dhla]

Hi

I am using the nrfjprog.dll to program my UUT (nrf51822) during our production PCBA test. Apparently this is a bad idea to use this dll since you sometimes change the definitions and then production stops if we update nrf tools. The reason that I have to update is that we start to use the nrf51802 instead of nrf51822 and then I had to update nrfjprog.dll. And then everything stops working because you Guys have added the text "NRFJPROG" in all function names. Should I use the command line Tool (nrfjprog.exe) instead or do you also change in that every now and then without making it backwards compatible?

[Nguyen Hoan Hoang]

An alternative solution is to use the IDAP-Link to parallel program multiple board at once. Supports both nRF51 & nRF52 series. No mergehex require to flash all 3 hex files.

[dhla]

Hi

Thank you for your reply. Ok, that looks really nice. Especially the parallel programming. That is very good for production. Unfortunately we cannot do that with nrfjprog.dll so I can imagine that the IDAPnRFProg.exe does not use the nrfjprog.dll?

However when I look at the IDAPnRFProg.exe usage description I miss some functions to read and write bytes and erase sectors (just like --memrd, --memwr and --earsepage in nrfjprog.exe)