Recommended Programming Architecture for nRF9151 Mass Production

Hi Nordic DevZone,

We are currently looking at how best to handle nRF9151 programming in mass production, and I would like to understand Nordic’s intended approach a bit better.

The nRF91 Series Production Programming documentation describes the production programming flow, including the modem firmware loader, modem update and verification. I also understand that Nordic currently recommends nrfutil 91 modem-firmware-upgrade for programming the modem firmware.

For automated production using dedicated gang programmers( not j-links ), is the intention that programmer vendors implement this production-programming algorithm themselves?

If so, do you know of any third-party production programmers that have already implemented the complete nRF9151 flow, including modem firmware programming?

It would also be helpful to know whether:

  • Nordic has known or validated programmer implementations available;
  • Nordic provides any reference implementation, library, or validation support for programmer vendors.

Ultimately, we are trying to understand what production programming architecture Nordic expects customers to use for automated, parallel mass production of nRF9151-based products.

Thanks!

Best Regards,
Kasper

Parents
  • Hi Kasper,

    The official tool to perform the actions explained in the nRF91 Series Production Programming guide (link) is JLink. However, the actions themselves are directly performed on the registers, so there is nothing preventing you adapting it to any other SWD-based programmers.

    I think I saw a few other programmers that were able to perform the modem firmware updates and such, but they are community projects and not official. I'll leave it to the community to give you suggestion on these alternatives.

    Best regards,

    Simon

  • Hi Simon,

    My concern is that J-Link is fundamentally an R&D/debug probe. While it works well for development and programming individual devices, it does not represent the dedicated multi-target programming architecture we would normally expect for mass production.

    Nordic’s Production Programming guide, however, seems specifically designed to allow programming-tool vendors to implement the nRF91 programming flow.

    So if J-Link is the only officially supported implementation today, what is Nordic’s intended solution for automated, parallel mass production of nRF9151 devices?

    Are there commercial production programmers that Nordic knows have implemented the complete flow, including modem firmware? And is there a process by which Nordic can validate or qualify such an implementation?

    We are essentially trying to understand how Nordic expects customers to move from the J-Link/R&D environment to a supported production-grade gang-programming solution.

    Best regards,
    Kasper

Reply
  • Hi Simon,

    My concern is that J-Link is fundamentally an R&D/debug probe. While it works well for development and programming individual devices, it does not represent the dedicated multi-target programming architecture we would normally expect for mass production.

    Nordic’s Production Programming guide, however, seems specifically designed to allow programming-tool vendors to implement the nRF91 programming flow.

    So if J-Link is the only officially supported implementation today, what is Nordic’s intended solution for automated, parallel mass production of nRF9151 devices?

    Are there commercial production programmers that Nordic knows have implemented the complete flow, including modem firmware? And is there a process by which Nordic can validate or qualify such an implementation?

    We are essentially trying to understand how Nordic expects customers to move from the J-Link/R&D environment to a supported production-grade gang-programming solution.

    Best regards,
    Kasper

Children
No Data
Related