Memory organisation of SFP, QSFP, XFP and OSFP modules for programming

Question

A reference post on the memory layout used when programming transceivers: SFP blocks A0h (serial ID/vendor, often write-protected) and A2h (diagnostics, page-select byte 7Fh, page 00h/01h user-writable); QSFP block A0h with page-select 7Fh, page 00h identity write-protected and page 03h user EEPROM; XFP tables via 7Fh; OSFP/CMIS lower 128 bytes fixed plus paged upper memory. It stresses that read-only bytes cannot be changed and that passwords may protect specific write areas.

Transceivers: SFP, QSFP, XFP, OSFP
Form factor: SFP, QSFP, XFP, OSFP

Symptoms / messages:

reference: which bytes are writable, where checksums and passwords live

qsfpwolf · Accepted Answer

Select the page/table/bank in the GUI rather than editing the raw buffer; respeect read-only bytes (writes to them cause verification errors) and enter any host/manufacturer password before writing protected areas.

Comments 1