Hello,
Can you confirm if your email address is correct in our system, ie can I send you the ETHAPI source code to this email? You can check the email address in your account settings.
I send you the code, "AS-IS", this means no support is provided around the ETHAPI source code, do you also understand that? The reason about that is because what you are asking for is so outside the scope of technical support.
The driver is simply sending MAC packet over an NDIS interface, ETHAPI is building the packets as per SD040(sip_mac_engine).pdf and sending those packets to the NDIS layer via the NDIS device driver; you are correct, the driver itself should be able to work with several cards.
There might be problems about concurrent access to this driver and/or the API. We have a system to test FMC104 + FMC204 in order to test FMC204. In this case we have two PCI ethernet adapter hardware in the machine, two ML605s and we can communicate with both ML605 without problem, but this makes sense.
As a side note, I am not sure what will happen the moment both FMC cards are outputing samples in the same time, the NDIS driver has only one queue, you will need a way to differentiate between packets, ie packet top-1 is from card 1 and packet top-2 is from card 2, etc.. Implicitly extra software work which might causes missing frames, etc.. My point here is that it will not be as easy as dealing with "two IDs".
Also keep in mind the protocol is not reliable, the purpose of this link is to take/put snapshots to the board at a low speed in a point to point configuration. Anything else is not supposed to work as it wasnt tested that way. Typically there is no packet recovery algo, if you miss one MAC packet, you are screwed, it will not recover. We are not using TCP/IP which would make the protocol able to work over a switch, etc..
Best Regards,
Arnaud