Add TE0714-03-50-2l

[rroohhh]

The SPIFlashResource defined for this board is connected to the configuration interface, this means one cannot drive the clock directly, but one has to use the USRCCLKO primitive. Any guidance on how to reflect this in the platform file?

[whitequark]

The SPIFlashResource defined for this board is connected to the configuration interface, this means one cannot drive the clock directly, but one has to use the USRCCLKO primitive. Any guidance on how to reflect this in the platform file?

We can't do this yet, but I have plans to fix this in near future.

[whitequark]

Can you provide an URL for the board documentation?

Does the board have no way to program it?

Even if the answer to the above is "yes", having blinky with do_program=False would still be quite useful for smoke testing.

[rroohhh]

Can you provide an URL for the board documentation?

The schematic can be found here.
Looking it up again made me notice that the last letter is not a small L but a capital i instead :)

Does the board have no way to program it?

The board has the JTAG only on the expansion connector, so the programming method depends on how you break that out.

Even if the answer to the above is "yes", having blinky with do_program=False would still be quite useful for smoke testing.

Sure makes sense.

[whitequark]

Thank you for your contribution!