PYNRFJPROG

RE: PYNRFJPROG

Vidar Berg — Wed, 25 Sep 2024 10:00:17 GMT

You can use recover(): https://github.com/NordicSemiconductor/pynrfjprog/blob/67e1a1eeaf77566214ea055aed4fd130401ae5a2/pynrfjprog/HighLevel.py#L453

RE: PYNRFJPROG

rodrigueza — Wed, 25 Sep 2024 09:54:03 GMT

Hi,

What are the steps required to successfully disable readback protection (APPROTECT) for both the application and network core when using the high-level API in the highlevel_program_hex.py example?

geometry dash breeze

RE: PYNRFJPROG

finkbr — Tue, 07 Nov 2023 20:40:19 GMT

Hi Vidor, That did it! i wasn't recovering each core separately. Didn't realize I had to do that. Its all working now and everything is much faster.

RE: PYNRFJPROG

Vidar Berg — Tue, 07 Nov 2023 10:33:48 GMT

Hi Brian,

I made a test using the 'highlevel_program_hex.py' example and discovered that one must specify the CPU core when disabling readback protection (APPROTECT). Please try to disable the readback protection using the high level API as I did here:

import sys
from pynrfjprog import HighLevel, Parameters


def program_hex(hex_file_path):

    # Initialize an API object.
    # Open the loaded DLL and connect to an emulator probe.
    with HighLevel.API() as api:

        probes = api.get_connected_probes()        
        snr = probes[0]
        # Initialize the probe connection. The device family is automatically detected, and the correct sub dll is loaded.
        with HighLevel.DebugProbe(api, snr) as probe:

            print("# Reading out device information.")
            # Read out device information to find out which hex file to program
            device_info = probe.get_device_info()
            print(device_info.device_family)

            # Erase all the flash of the device.
            print("# Programming %s to device with ERASE_ALL and SYSTEM_RESET." % hex_file_path)

            # Make a program option struct to modify programming sequence.
            # If ommitted, the default programoptions struct specifies ERASE_ALL, SYSTEM_RESET, and VERIFY_NONE.
            program_options = HighLevel.ProgramOptions(
                erase_action=HighLevel.EraseAction.ERASE_ALL,
                reset=HighLevel.ResetAction.RESET_SYSTEM,
                verify=HighLevel.VerifyAction.VERIFY_READ,
            )

            probe.set_coprocessor(Parameters.CoProcessor.CP_NETWORK)
            if probe.get_readback_protection() != Parameters.ReadbackProtection.NONE:
                print("Disabling APPROTECT on network core")
                probe.recover()
            probe.set_coprocessor(Parameters.CoProcessor.CP_APPLICATION)
            if probe.get_readback_protection() != Parameters.ReadbackProtection.NONE:
                probe.recover()
                print("Disabling APPROTECT on application core")
            
            probe.program(hex_file_path, program_options=program_options)

            print("# Application running. ")

    print("# Example done...")

def main():
    if len(sys.argv) != 2:
        print("No .hex file specified")
        sys.exit(1)
    
    hex_file = sys.argv[1]
    program_hex(hex_file) 


if __name__ == "__main__":
    main()

Please also ensure that your pynrfjprog package is up to date (v10.23.2 at the time of writing). This is required if the input hex file contains data for both the application and network core.

Vidar

RE: PYNRFJPROG

finkbr — Mon, 06 Nov 2023 15:09:43 GMT

Hi Vidar,

As you can see from the above code, I perform a low level recover:

print(f"The DLL version is: {api.dll_version()}")
print(f"Erase protect: {api.is_eraseprotect_enabled()}")
print("Recovering device")
api.recover()
print("Erasing Device")
api.erase_all()
api.close()

But I still cant program the device. I need to be able to permanently disable to protection. When I try from the command line, wit the command you provided, it works fine. we have several steps including serializing the device that the python program takes care of for us. Are you suggesting that i need to write the scripts in a different language because the python nrfjprog doesn't always work? Or is the lowlevel recover working and the chip is reset to its original state because I close the low level api and open the high level api? If that is the case, can you please tell me how to write a merged.hex using the low level api? The documentation is terrible for the python library.

I tried using a command shell from python it seems to work but I get these errors in the output:

[error] [ Client] - Encountered error -90: Command read_memory_descriptors executed for 15 milliseconds with result -90
[error] [ Worker] - Can't read memory descriptors, ap-protection is enabled.

However the code IS loaded onto the chip, so why the errors?

Brian

RE: PYNRFJPROG

Vidar Berg — Mon, 06 Nov 2023 13:29:01 GMT

Hello,

I would recommend using nrfjprog if you are looking for a way to program your nRF devices from the command line or a batch script, but do not necessarily need Python integration.

Flashing chip with nrfjprog when readback protection is enabled

$ nrfjprog --program merged_domains.hex --recover --verify  -r

Flashing chip with nrfjprog when readback protection is disabled

nrfjprog --program merged_domains.hex --chiperase --verify  -r

[quote user=""]An error was reported by NRFJPROG DLL: -90 NOT_AVAILABLE_BECAUSE_PROTECTION. [/quote]

The nRF5340 and nrf52832 with the latest build code (see IN142 Informational Notice v1.1) have readback protection enabled by default when they leave our factory, which must be disabled before you can perform the initial programming of the chip. When you do an "ERASEALL" in the programmer app, it will perform the same operation as nrfjprog --recover does to unlock the chip. The equivalent function in pynrfjprog is implemented here: https://github.com/NordicSemiconductor/pynrfjprog/blob/67e1a1eeaf77566214ea055aed4fd130401ae5a2/pynrfjprog/LowLevel.py#L680

Best regards,

Vidar