Part Number: TSW14J57EVM
Hello, I am trying to program TSW14J57 through quartus ,And I have a problem on the pin planner interface.
I want to know some pin information of LED and keys. How can I get these information of this board.
Thank you.
This thread has been locked.
If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.
Part Number: TSW14J57EVM
Hello, I am trying to program TSW14J57 through quartus ,And I have a problem on the pin planner interface.
I want to know some pin information of LED and keys. How can I get these information of this board.
Thank you.
Jim,
I constrain the pins of TX SYNS LED according to the pin information on the schematic design, and then the Quartus prompts "Editing location assignment is not successful. The pin is already assigned."



But I'm pretty sure I don't assign PIN_ AG25. Because I deleted all pin configuration information in the project.
By the way,this project file is provided by TI and its name is TSW14J57RevE_ 16L_ XCVR_ ADCBRAMDACDDR.
Jim,
I noticed that "Note: Tx SYNC signal of the device routed to FMC is not connected to FPGA in the Arria10 EVM. Hence the SYNCB0CMOS of the device is bluewired to Arria10 EVM through J7 SMA connector" was written on the third page of the A10 AFE74xx XCVR 2x44210 JESD Reference Design User Guide, but I did not find the J7 SMA connector on the AFE744EVM. Can you answer my confusion?
Thank you,
Deng.
Deng,
Are you using a TSW14J57EVM or an Arria 10 GX FPGA Development kit? The document you are referencing uses the Arria 10 board.
J7 is the SMA on the Arria 10 GX FPGA development kit, not the AFE744EVM. After looking at the AFE744EVM schematic, I noticed all SYNC options (LVDS and CMOS) are routed to FMC pins that are not used by the Arria 10 board. The AFE also has no way of getting to one of these SYNC pins unless you cut traces and connect a blue wire to a connector (J11) or connect it to pad 1 of Q21 after it is removed (this part is not required). From my knowledge, we have never interfaced these two platforms before.
Regards,
Jim