newkid_old

Members
  • Content Count

    44
  • Joined

  • Last visited

About newkid_old

  • Rank
    Frequent Visitor

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I am using the Arty A100. I use the canned serial IP for that board.
  2. I have downloaded the Arm CortexM3 package and have followed the steps for Vivado 20 and Vitis to recognize the repository. I'm able to generate a bitstream from Vivado but when I get to Vitis and create the Platform Project I get this error: I have found a post on the Xilinx forums where this was a known problem in Vivado 19.2 so I installed the newest version 20 and still have the same issue. Any help is greatly appreciated.
  3. My apologies. I misinterpreted your question. When I was running the echo server in Vivado 18.3 I got the full message in serial terminal concerning the IP address and port. Now that I'm using Vivado 19.2 and the new SDK Vitis, I get the message that I displayed in my original post. It seems that the IP address and port are never getting set.
  4. No. It would tell me the echo server had been setup at the default IP address and port. You could then open a telnet Putty window at that address and port and have it echo what you typed in the console.
  5. Yes. I've installed the board files and followed the example. I had the example running on Vivado 18.3.
  6. I am trying to run the Echo Server demo on my Arty A7-100. I am using Vivado 19.2 and Vitis. I have the application loaded on the Arty and in my UART window it gives this message: It never gets to "TCP echo server started @ port 7". I've changed the TEMAC adapter speed to 100, 10 and Auto-Negotiate and all have the same problem. Any help is greatly appreciated. Cheers
  7. That fixed it. Thank you for your help. Cheers, Curt
  8. I have recently upgraded Xilinx Vivado to 19.1 and attempted to setup the Arty Echo Server example on my Arty A7-35 board. The bit stream gets generated without any errors as does the SDK portion of the project. After the bitstream and program is loaded onto the Arty however nothing happens. I receive nothing from the UART stating the server has started. I have successfully ran the echo server example when using Vivado 18.3. Has anyone else ran into this problem? Thanks in advance.
  9. Thanks for you reply. Do you think the Arty a7-100 could handle the task?
  10. I'm wondering if there's a way to modify the Arty Echo Server example project to utilize BRAM on the FPGA vice the DDR chip on the board? Thanks in advance.
  11. Jon, Thanks for the reply. I am using the Digilent board files for my project. I am using the example Ethernet Echo Server that does work without my extra input on the interrupt controller. This is hooked to the 3rd input on that IP. The other two are as per the example which is the timer and the ethernet IP blocks interrupt. I've tried changing the Interrupt type from Level to Edge but get the same results. Thanks, Curt
  12. I have an issue with one of my Arty interrupts. I'm using the AXI GPIO interrupt along with the ethernet and timer interrupt(using the echo server example). I've placed some debug code that sends over the UART that the interrupt is recognized but it locks the Microblaze controller from there. void InterruptHandler(void *CallbackRef) { //dataReady = 1; //Signals the main loop that the FIFO is full and ready to be read xil_printf("Interrupt found... \n\r"); XGpio_InterruptClear(&fifoFull, XPAR_AXI_GPIO_0_IP2INTC_IRPT_MASK); XIntc_Acknowledge(XPAR_INTC_0_BASEADDR,
  13. If there is errors, I didn't see any and I do have my module running on an Art A7 board. I do register my Pulse_Out with the clock event in an IF statement. Here is my code: I changed the Pulse_Count to 8 bits which is different from the block seen above that's 16 bit. Any pointers are appreciated. entity Pulse_Trigger is Port ( Reset : in STD_LOGIC; Clk : in std_logic; Trigger : in std_logic; Pulse_Length : in STD_LOGIC_VECTOR (7 downto 0); Pulse : out STD_LOGIC); end Pulse_Trigger; architecture Behavioral of Pulse_Trigger is signa