Difference between revisions of "Signature"
| Line 1: | Line 1: | ||
Documents signature bytes used on EPROM, AT89C51, 87C51, etc. | Documents signature bytes used on EPROM, AT89C51, 87C51, etc. | ||
| − | |||
Is AT89C51 signature the same as P87C51 signature? | Is AT89C51 signature the same as P87C51 signature? | ||
| Line 8: | Line 7: | ||
Are EPROM signatures compatible with mcs51 signatures in any way? | Are EPROM signatures compatible with mcs51 signatures in any way? | ||
| + | |||
| + | = JEDEC = | ||
| + | |||
| + | https://www.jedec.org/standards-documents/docs/jep-106ab | ||
| + | |||
| + | Think these are flash specific | ||
| + | |||
| + | "JEDEC SOLID STATE TECHNOLOGY ASSOCIATION" | ||
| + | |||
| + | "The intent of this identification code is that it may be used whenever a digital field is required, e.g., hardware, software, documentation, etc." | ||
= 89C51 family = | = 89C51 family = | ||
Revision as of 17:26, 12 August 2018
Documents signature bytes used on EPROM, AT89C51, 87C51, etc.
Is AT89C51 signature the same as P87C51 signature?
Do mcs51 mask ROM parts support signature?
Are EPROM signatures compatible with mcs51 signatures in any way?
JEDEC
https://www.jedec.org/standards-documents/docs/jep-106ab
Think these are flash specific
"JEDEC SOLID STATE TECHNOLOGY ASSOCIATION"
"The intent of this identification code is that it may be used whenever a digital field is required, e.g., hardware, software, documentation, etc."
89C51 family
IDs are found at special NV memory address 0x30-0x32
| ID (hex) | Vendor | Chip label | Die ID |
|---|---|---|---|
| row 1, cell 1 | row 1, cell 2 | row 1, cell 3 | row 1, cell 3 |
| row 2, cell 1 | row 2, cell 2 | row 2, cell 3 | row 2, cell 3 |
