06-06-2019 11:12 PM
I am trying to connect FPGA ML506 board to PC for serial communication using RS232; Basically, we are using UART for serial communication. While doing pin assignment in UCF we didn't find any pin for RS232 in the datasheet. Can anyone help in this as soon as possible or is there any other way rather than this would also appreciate.
06-07-2019 12:15 AM
Look in the example code for the board provided on line .
here is a start,
RS232 is a +- 12 v standard, and Virtex can not handle that level ,so there is a Rs232 serial driver / receiver chip on the board.
My guess , and thats all it is, is that the RS232 is to the "processor" in the fpga code.
06-07-2019 02:43 AM
Ok, where have you looked ?
06-07-2019 03:25 AM
We searched in ML506 datasheet, but we did not find any pin number.
here it is: https://www.xilinx.com/support/documentation/boards_and_kits/ug347.pdf
So our requirement is to send 128-bit data from PC to FPGA(ML506). For that, we wrote the code for UART. And we are sending this data through RS232 cable to "serial comp port 1" of FPGA.
We have attached UCF file screenshot with it and our ML506 kit board pic, a quick response will be appreciated.
06-07-2019 03:49 AM
If you do a search for "ML506 schematic" you'll find that - which tells you just what you need. FPGA_SERIAL1_TX is on AG20, and FPGA_SERIAL1_RX is on AG15.
As noted in the user guide, you will need a null modem cable for this - although that's not hard to build.
06-07-2019 03:55 AM
There are example designs to use, like the hello world, just look in there,
but this is my way of doing this.
start with the schematics :
sheet 1, tells yo uthat the UART , which is a way of saying "RS232" / "serial", is on sheet 12.
If you go to sheet 12, you find connector P3, which I htink is the connector your pointing at.
then following th esignals to the left, you see thay are named fpga_serial1 .
If you then search the scheamtics for those signals , you see thay are on sheet2, fpga bank 4, pins AG15 and AG20.
Hope that helps, its a good skill to have ,
06-07-2019 04:30 AM
06-07-2019 08:15 AM