Protected memory & passwords

Some transceivers protect their memory: certain pages cannot be written until the module is unlocked with a password. CodingBox handles this in the application settings.

How unlocking works

The module is unlocked by writing a password to a specific address before the protected pages are written. In the settings you configure:

• the table address that selects the protected area,
• the password address where the password is written,
• the password value itself.

With those set, the selected pages can be written to the module.

Where to find the values

Known password patterns for common modules are kept in the CodingBox database and applied by the app. When a module needs values you do not have, they must come from the module's documentation or vendor.

Writing to protected memory changes the module permanently. A backup is taken before writing — see the Code database.

Password refused, hardware write protect or a write that does not stick: EEPROM read & write errors.