PROM files: build .bin for daisy chain on the fly

snipped-for-privacy@gmail.com schrieb:

yes anyone has done this.

What impact does is 'merging' the slave .BIT inside the master bit by inserting the slave .BIT as single stream that written to LOUT register. Well at least that is how it work for serial configuration.

I have tried to configure multiply devices in chain without the LOUT trick but with little luck, usually both master and slave release done, but only one of them actually starts, eg GHIGH of the slave doesnt assert.

using impact to insert the second bit inside the master bit makes the second (slave) device also to start properly.

I bet you are (will be) facing the same problem.

inserting the slave streams into LOUT record isnt complicated but you need to parse the .BIT files in order to write out the resulting single binary image that you need.

Antti

Well, I understand I'll have to parse the file structure to be able to rebuild it. This is what I've been doing for a couple of last days. The problem is that Xilinx app. notes describes all the PACKETS used in file while I still have a problem undestanding the file STRUCTURE, i.e. why are those packets are being organized in the way they are.

snipped-for-privacy@gmail.com schrieb:

I have a xilinx bitstream 'dump' utility that can be used to look what impact has done.

the bitstream composition isnt complicated

Antti