Dear Ricky,
I guess blindly doing all the writes the same should get the chip up and running. If you want need to time information, then use windows API to time stamp all the writes in the file, then you get address, value as well as time sent (as seen by the program init).
In theory, if you know 500 writes bring the chip set alive, doing these 500 writes not from a mac_engine but from a state machine should do the same.
To go back to the list, a day I had to produce such a table for another FMC product. I modified the software to create a CSV file, each time the function would be called it would add a line in the CSV file. I would have ultraedit configured to automatically reload the file when changed. Then what I would so is:
1) Step over the call to sipif_writesipreg()
2) Go to ultraedit and add a comment on the last column (after the last comma), ie clocktree write, adc init, etc..
3) Would be saving the file in ultraedit and loop to 1).
It might look cumbersome but this is faster than figuring out all the register by yourself, the FMC30RF is without doubt the most complex chip set in 4DSP portfolio.. From that table you will modify values and create a new table.
I hope that helps,
Arnaud