• Content Count

  • Joined

  • Last visited

About Notarobot

  • Rank
    Prolific Poster

Recent Profile Visitors

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

  1. Paul, If you Ok with the Zynq I would suggest to look at variety of boards on I used some of them with success and would give my recommendations. High speed connectors are mechanically robust and easy to route if you want to make custom daughter boards. Documentation is also excellent.
  2. Hi, @Ram Based the diagram you've allocated only 2 BRAM addresses for storing 32-bit data words. However based on your description you intended to have 4 memory cells. That is confusing to me as well. Dual BRAM means that it can be read and written by two different actors using the same address area. For example, PL is writing data and PS is reading same data, asynchronously. To my knowledge, if you use Vivado block diagram tools for 32-bit data you should have a variety of choices to configure the address width. Restrictions come when you choose nonstandard BRAM configurations.
  3. 1. Since it is such a simple code, most likely the issue is not with Vivado version but with your project. The best way would be recreating the project in the new version from scratch. 2. When you get positive outcome from someone's post, please, indicate that this is a solution. It would allow others to learn, plus would encourage more help. Thanks!
  4. Notarobot

    CAN Bus

    Hello @tahoe250 Hope you will find useful the discussion about CAN here CAN on Zybo works well but requires correct configuration. If you want real help we need more info. I don't have time for if-then-else speculations about what could be incorrect. Best of luck!
  5. @tahoe250 Answers to your question can be found in Vivado folder ...SDK\...\data\embeddedsw\XilinxProcessorIPLib\drivers\canps_ The folloing code makes the trick: /* The Baud Rate Prescaler Register (BRPR) and Bit Timing Register (BTR) required * to be set for the desired baud rate. * For more information see the CAN 2.0A, CAN 2.0B, ISO 11898-1 specifications. * The CAN clock is 24MHz. */ #define TEST_BTR_SYNCJUMPWIDTH 3 // 100, 250 -> 3 #define TEST_BTR_SECOND_TIMESEGMENT 2 // 100, 250 -> 5 500 -> 2 #define TEST_BTR_FIRST_TIMESEGME
  6. Hi @tanvi127 1. In the example app TesSD.c the block containing f_mkfs function was commented because it never worked on Zybo board. It appears that you've changed that code. 2. Looking at your screenshot I've noticed red dot in "Problems" Tab indicating that you have code errors. This can't be f_mkfs failure. I would recommend cleaning this error. Please note that for best results SD cards should be formatted with the application distributed for free by SD Association. Good luck!
  7. Good morning, My similar problem was solved replacing USB-RS232 dongle with the one supporting high speed, specifically, Silicon Labs part number CP2102N-EK. It should be mentioned that Zynq PS side was utilized for RS-232 at 921600 bit/s without flow control and parity. It worked flawlessly since for tw-way communication and sending large files. Hope it'll help!
  8. Hi @Bilal29 You can find two examples of default XADC usage in Xilinx library Xilinx\SDK\201....\data\embeddedsw\XilinxProcessorIPLib\drivers\xadcps_v2_2\examples It is well documented and it pretty much effortless. Everything is done in SDK, no hardware configuration is required. It worked for me. I don't know what is your goal but these examples could be a good starting point. Good luck!
  9. Notarobot

    Stuck in SDK

    Kris, Printing via xil_print is using STDIO by default and could reconfigured in Vivado and SDK. With little info you provided a lot left for guessing. My last recommendation is to pay attention to a configuration of your build in SDK. The interrupt interrupt service routine (ISR) might not work if GCC compiler has optimization ON. To make it work the variable in the ISR should be declared volatile. Debug build usually has flag -O0 that optimization none. Good luck!
  10. Notarobot

    Stuck in SDK

    Hi, Kris, I noticed uart_rtl line on your diagram and assumed that it was for xil_printf. It is easier to use standard UART connected to MIO which doesn't need PL blocks. I recommend to search or for Introduction to Zynq Lab 6 called "Adding Interrupts from the Custom PL Peripheral". Also try to set Integrated Logic Analyzer (ILA). It is extremely useful to debigging.
  11. Notarobot

    Stuck in SDK

    Hi Kris, Based on info you provided it could be many different things. For example, why are you using uart_rtl instead of UART1 or UART0? This could be a configurattion issue. Using interrupts for buttons is another tricky part which requires proper configuration not described in your post. I would start with known path and upgrade gradually. In the past I tested the original Zybo with a trivial button-LED project and attached three files related to it. Try it if you want. The project requires Zybo board file and AXI configuration. SDK UART console is used for xil_printf. Goo lu
  12. Notarobot

    Reading Pmod AD1 value

    Hello wing, In my experience Digilent project here is the most comprehesive use case of PmodAD1 on Zynq boards. It allows for running either continuos and single acquisition on both channels. Also do a search of Digilent forum, you should find block diagrams related to you questions.
  13. Hi EELE First of all I would recommend PmodAD1 for your experimentation. It contains two ADC chips with 12-bit resolution. I've used it successfully with Zybo 7000 for data acquisition at 1MHz sample rate and it worked at 2 MHz as well. Then search the forum on Google using request: PmodAD1 You will get a lot of very useful information for making your decisions. I believe this is the shortest path to a knowledge you are looking for.
  14. @Jonathon Kay My recommendation is to start with this board and follow tutorials from here. Download and install recommended Vivado versions not the latest. This board is very affordable and has everything to start. Tutorials will give you a picture of the design process with Vivado. It will help to see integration of the FPGA part in the system. Udemy Zynq tutorials are applicable to this board with minor corrections. I wish to have this when I started. It might be hard but it is a lot of fun as well and without fun who would do it.
  15. @Jonathon Kay You definitely can. Just give it some time. It took me three month in the beginning to program my first working VHDL code. Personally, I recommend VHDL because in my view its structure is a closer reflection of hardware. I agree with zygot that you can learn programming without any board just in Xilinx Vivado. Keep in mind that you will need to learn Vivado and I recommend video tutorials. is not bad for fast learning. However, programming a physical board brings more satisfaction than simulations. Zedboard seems to be an overkill for your goals. I had g