Shame on me. But I've been using the AT89LP4052 chip for years, and I know that it has a feature called "user row programming", but I have no idea what it does or how to use it.
Of course, I've already read the manuals, and googled and done lots of searches, but I'm still in the dark.

Anyone here cares enough to enlighten me?

@Papabravo

 

Always glad to help a kindred spirit.

There are a number of potential uses for such a thing. You can put a unique serial number in each one. Many devices on networks have an "identity" object that contains "attributes" (aka data) that uniquely identifies a device on a network of similar devices. Besides a unique serial number there could be a manufacturer ID, date, lot number and so forth. Such unique identifications can be used to assign network addresses in such a way that all addresses on a network are unique.

 

There are a number of potential uses for such a thing. You can put a unique serial number in each one. Many devices on networks have an "identity" object that contains "attributes" (aka data) that uniquely identifies a device on a network of similar devices. Besides a unique serial number there could be a manufacturer ID, date, lot number and so forth. Such unique identifications can be used to assign network addresses in such a way that all addresses on a network are unique.

Thanks. I was suspecting that much... but how is it any different from simply including said data within a program when one "burns" it into the chip? I mean, what's the particular advantage?
The only thing that comes to mind are the program lock fuses.... maybe user row programming could be read from the chip regardless of the state of those fuses?

 

Thanks. I was suspecting that much... but how is it any different from simply including said data within a program when one "burns" it into the chip? I mean, what's the particular advantage?
The only thing that comes to mind are the program lock fuses.... maybe user row programming could be read from the chip regardless of the state of those fuses?

I think that largely depends on the specific programming technology in terms of ISP (In System Programming) or programming blank chips before they are placed on a board. I'm here to testify to the enormous economic advantage of ISP in controlling wasted parts/boards. Especially when purchasing people ship blank parts to be placed on boards that become "chicklets" (scrap) when there is no method of ISP after the chip is placed on the board.

 

Especially when purchasing people ship blank parts to be placed on boards that become "chicklets" (scrap) when there is no method of ISP after the chip is placed on the board.

Oh yeah... that I get... particularly when SMT chips are being used... maybe "user row programming" can be read independently from the rest of the contents of the chip? So that version numbers and/or special notes and characteristics could be read regardless of the state of the lock fuses?