Controlling GPIO within nrfjprog

Hello,

I have a product with QSPI flash that I would like to use nrfjprog to program the flash part. However, the QSPI flash's VCC is controlled (via a FET) from a GPIO line. I am looking for a way to have nrfjprog enable the GPIO line before attempting to access the QSPI flash (so that the flash is powered up). Is there a way from qspiinit.ini to do this?

Thanks,

Jon

Parents
  • Thanks for the reply. A couple of questions:

    1. I assume this will be very similar for nRF52, correct?

    2. You mention that the program_file API might allow the part to reset during programming. Can you explain why? Would this potential reset happen on the nRf52 as well. Also, I currently found that I could program the gpio similarly with nrfjprog and the memwr command, followed by a second run of nrfjprog with the program command. However, now you have me concerned that with nrfjprog the part might reset losing the gpio seeing...

    Thanks,

    Jon

Reply
  • Thanks for the reply. A couple of questions:

    1. I assume this will be very similar for nRF52, correct?

    2. You mention that the program_file API might allow the part to reset during programming. Can you explain why? Would this potential reset happen on the nRf52 as well. Also, I currently found that I could program the gpio similarly with nrfjprog and the memwr command, followed by a second run of nrfjprog with the program command. However, now you have me concerned that with nrfjprog the part might reset losing the gpio seeing...

    Thanks,

    Jon

Children
  • 1. Yes, it should be mostly the same except for the gpio addresses and device name (obviously).

    2 I did not think of doing it like that. This might be the simplest solution if it works. Are there any indications that it might be powering off? I.e. do you get any programming errors if you include the --verify argument?

    Jon said:
    You mention that the program_file API might allow the part to reset during programming. Can you explain why?

    I am not familiar with the internals of this library, so I will have to check with the developers again and get back to you.

Related