Simple issue of Production Serialization

Thanks again. Having an external device that's programmed separately makes sense and I see your point about programming during testing is a minor issue. However, is it true that you need to make a physical connection? To FvM's point (thanks as well) I was thinking maybe the configuration memory would be programmed and serialized off board where a specific location of the config mem contained the unique serial number and would be read upon boot-up by the FPGA. I'm at a disadvantage because I don't know what data format is stored in the config memory and how the FPGA reads it out, so I don't know how easy it is to manipulate it or if it's even possible or if "the industry" frowns upon this approach.

FvM, I don't really care specifically where the information is stored. As you point out, the preferred location would probably be in the configuration memory since that already exists and then I wouldn't need another device.

I'm not necessarily looking for a specific solution to my specific problem. I'm mainly trying to get an ideal for what people commonly do in this situation since I'm very green on this subject. It sounds like Jake may have a point where the board is most likely going to be ICT and/or functionally tested and so just program/serialize it at that time via a connection. I can also look into getting the configuration memory programmed and serialized off board, but that's actually where I started and I just seem to get blank stares when I talk about this. I guess that's not actually common to do.

Thanks for the feedback.

Alex