Trying to Delete All Flash and BBR Keys Gets NAK

[bobvan]

I actually doubt this is a problem with pyubx2; more likely my PEBKAC. Seems like knowing how to apply pyubx2 is half the battle.

For reproducible F9T config testing, I want to put it back to "factory" state. Would deleting all the key/value pairs in flash and BBR with a wildcard be a reasonable approach? I get a NAK when I try.

Is this expected? What's a better way to get back to factory state?

`from serial import Serial
from pyubx2 import UBXReader, UBXMessage, SET_LAYER_FLASH, SET_LAYER_BBR, TXN_NONE

with Serial("/dev/ttyACM0", 9600) as ser:
delete_msg = UBXMessage.config_del(SET_LAYER_FLASH|SET_LAYER_BBR, TXN_NONE, [0xffffffff])
print(delete_msg)
ser.write(delete_msg.serialize())
ubr = UBXReader(ser, protfilter=2)

while True:
    (raw_data, parsed_data) = ubr.read()
    print(parsed_data.identity, parsed_data)
    if parsed_data and parsed_data.identity == 'ACK-ACK':
        print("Flash and BBR key delete ACKed")
        break
    if parsed_data and parsed_data.identity == 'ACK-NAK':
        print("Flash and BBR key delete NAKed")
        break`

<UBX(CFG-VALDEL, version=0, bbr=1, flash=1, action=0, reserved0=0, keys_01=4294967295)> ACK-NAK <UBX(ACK-NAK, clsID=CFG, msgID=CFG-VALDEL)> Flash and BBR key delete NAKed

[semuadmin]

You can use the CFG-CFG command to perform a factory reset, e.g.

msg = UBXMessage(
    "CFG",
    "CFG-CFG",
    SET,
    clearMask=b"\x1f\x1f\x00\x00",
    loadMask=b"\x1f\x1f\x00\x00",
    devBBR=1,
    devFlash=1,
    devEEPROM=1,
)

Refer to the F9P Interface Specification for further details on the meaning of the clearMask and loadMask fields and memory layers.

FYI PyGPSClient has a specific preset for this, among many other common configuration commands.

[bobvan]

Thanks, will use that.

I guess my interest in doing the factory reset with UBXMessage.config_del() is mostly academic. I started down this path based on the F9T Interface Description admonishments for CFG-CFG. I guess it's not deprecated like some other messages, but they seem to be pushing in the direction of UBX-CFG-VALDEL at every opportunity.

[semuadmin]

The legacy CFG configuration messages are deprecated in F9 firmware, and removed altogether in X20 firmware, with the exception of:

• CFG-CFG (clear, save and load configurations)
• CFG-OTP (set one-time programmable memory)
• CFG-RST (reset receiver / clear backup data structures)
• CFG-VALGET
• CFG-VALSET
• CFG-VALDEL

See the relevant interface specification(s) for further details.

If this addresses your query, I'd be grateful if you could 'Mark as answer'. Thanks.

[bobvan]

Helpful insight, thanks!