The xparameters and device ID defines are basically the unique addresses on the AXI bus that the FPGA uses to identify all the modules on the AXI interface. It's how it knows where to route the data over the AXI interface. Great video. Looking forward to trying vitis out, I haven't used it recently.
Great video anyone looking to get familiar with using Vivado and Vitis on a FPGA board, using Microblaze and testing a C program (in this case - the UART test). Looking forward to more such videos
You get the warnings because you write to the two variables TxStatus & UartLiteStatus, but never read them. Maybe add some conditional statements to check they returned XST_SUCCESS or not
Hello, I'm interested in obtaining data through UART, processing it using my custom IP, and then sending the response from my custom IP back through UART. I would appreciate guidance on how to establish the connection between my custom IP, MicroBlaze, and the UARTLite IP. Thank you for your assistance.
When I attempt to export the hardware from vivado I get this error "Cannot write hardware definition file as there are no generated IPI blocks". Any ideas what I'm doing wrong? I'm on the Arty A7 not the S7 so that might be an issue. Thanks!
Great video. Too bad you did not include any text receiving from the UART. Regarding the compiler warning about TxStatus, it is declared (int declaration) and set (= assignment) but not used anywhere. Basically the set line (line 92) is used to call the SendData function but that's it. You're not taking advantage of the return value of the function for anything.
I didn't know that the Arty S7 had a USB UART until I watched this video. It must be on that empty schematic page. Thanks! Hopefully you have figured out why the warning on the unused TxStatus. It is assigned but not used. Just delete it.
Thanks for a great video. I am using Vivado and Vitis 19.2. At 20.29 on the video, when I right click on the uart_example_app to build the project, it gives this error message (mb-gcc.exe application was unable to start correctly (0xc0000142) - Any suggestions?
The issue was with the toolchain on my laptop and when I installed my tools on a new computer, it worked right out of the box. Thanks for a great video
I dont see any alphabet on my tera term, but only "Uart lite tx test successfull". Can you help me plz? Otherweise your video is very helpful to me. Thanks a lots !
Can it be because the local variable TxBytesSent is uninitialized? Local variables must be initialized. Otherwise they will have an undefined value. It should be initialized to 0. Or is this different somehow with C in this context?
![[SFM] Risky Recital](http://i.ytimg.com/vi/RzNkY1_Nk3o/mqdefault.jpg)
The xparameters and device ID defines are basically the unique addresses on the AXI bus that the FPGA uses to identify all the modules on the AXI interface. It's how it knows where to route the data over the AXI interface.
Great video. Looking forward to trying vitis out, I haven't used it recently.
Love seeing the people I'm watching commenting on the people I'm watching. Thanks for the explanation of the memory spaces.
Great video anyone looking to get familiar with using Vivado and Vitis on a FPGA board, using Microblaze and testing a C program (in this case - the UART test). Looking forward to more such videos
I love you. Everything that I needed in one video.
Great video! Thanks Dom!!
You get the warnings because you write to the two variables TxStatus & UartLiteStatus, but never read them. Maybe add some conditional statements to check they returned XST_SUCCESS or not
I think the set but not used error is because you're not reading it anywhere. Do you have an if statement to check the TxStatus?
you right thanks!
YOU ARE MY HERO
Would love to see a video where UART Rx from terminal controls FPGA output
Wow, man. 101°F at 5pm ? You live in a very hot place. Great vid though. :-)
Haha yep west coast gets hot in summer :(
nice tutorial , help me a lot
would it (example design) work the same with zynqmp ultrascale?
Hello, I'm interested in obtaining data through UART, processing it using my custom IP, and then sending the response from my custom IP back through UART. I would appreciate guidance on how to establish the connection between my custom IP, MicroBlaze, and the UARTLite IP. Thank you for your assistance.
When I attempt to export the hardware from vivado I get this error "Cannot write hardware definition file as there are no generated IPI blocks". Any ideas what I'm doing wrong? I'm on the Arty A7 not the S7 so that might be an issue. Thanks!
Never mind, I got it working !
Glad to hear you got it working! What ended up fixing the issue?
@@Dom-bo8wd I had to select “generate bitstream” option before exporting hardware
Great video. Too bad you did not include any text receiving from the UART. Regarding the compiler warning about TxStatus, it is declared (int declaration) and set (= assignment) but not used anywhere. Basically the set line (line 92) is used to call the SendData function but that's it. You're not taking advantage of the return value of the function for anything.
Is it possible to have 14 UARTs using Microblaze in SPARTAN-6 running at a baud rate of 460800?
How can we change baudrate
I didn't know that the Arty S7 had a USB UART until I watched this video. It must be on that empty schematic page. Thanks! Hopefully you have figured out why the warning on the unused TxStatus. It is assigned but not used. Just delete it.
Thanks!
Thanks for a great video. I am using Vivado and Vitis 19.2. At 20.29 on the video, when I right click on the uart_example_app to build the project, it gives this error message (mb-gcc.exe application was unable to start correctly (0xc0000142) - Any suggestions?
The issue was with the toolchain on my laptop and when I installed my tools on a new computer, it worked right out of the box. Thanks for a great video
I dont see any alphabet on my tera term, but only "Uart lite tx test successfull". Can you help me plz? Otherweise your video is very helpful to me. Thanks a lots !
Ya sometimes the code launches and this happens, while the board is connected to the terminal, hit the reset and you should see the alphabet pop up
Can it be because the local variable TxBytesSent is uninitialized? Local variables must be initialized. Otherwise they will have an undefined value. It should be initialized to 0. Or is this different somehow with C in this context?