Jump to content

0xbadcaffe

Members
  • Posts

    15
  • Joined

  • Last visited

Posts posted by 0xbadcaffe

  1. Thanks JColvin!

    I was able to port the GPIO example to Vivado 2022.2 and used the Arty-S7 PMOD (JA) connector to send data to a PC connected to the PMOD using an FTDI (TTL/USB).

    I would like to proceed with the vhdl based UART example (not Microblaze) and expand it into an end-to-end request response design.

    The Arty fpga should support both RX and TX, store the incoming data into a buffer, analyse it and send a response respectively.

    I that there ready to use IPs from Xilinx. Not sure how flexible are they.

    Should I just expand your example and build my design around it?

    What is your suggestion to proceed with this issue?

     

    Thanks again!

     

  2. Thank you James for the answer.

    First, perhaps I was not that clear.

    I do not need both RS232 and RS485 working on the same RX and TX pins, they can be on separate PMOD connectors and thus different logic signals.

    I want to start with RS232.

    Is there a VHDL UART code example (not Microblaze based IP) for working with PMODs? specifically the  Digilent RS232?

     

    Also, I see in the The Digilent Pmod RS232  description page a note which states:

     

    Quote

    Note: There are two UART signal pin assignment conventions in use on Digilent products. This product uses the old signal assignment convention. Connecting a product using the old convention with one using the new convention requires the use of a UART Crossover Cable (not included). Click here for a more detailed explanation.

     

    Can use the Pmod RS232 with the Arty-S7? do I need to use the Crossover Cable?

     

    Thanks!

     

     

  3. Hi all and thanks for the replys.

    I understand that the XDC file has to be added manually and I also followed the instructions for adding it successfully.

    I was asking why they're not being added automatically while choosing the board type in Vivado project creation.

    I assume the reason was described by JColvin regarding some Xilinx restrictions.

  4. Hi

    Just out of curiosity, why are the Digilent Xilinx Design Constraint (XDC) files are not part of the vivado-boards git repository, and can be selected when adding a constraint with the appropriate board type?

    Why do I have to download the XDC file from a separate digilent-xdc repository?

    When I create a new project in vivado and choose the board type, the board's configuration files are added to the project (XMLs), why is the XDC file not one of them?

    Thanks!

×
×
  • Create New...