• Content Count

  • Joined

  • Last visited

About TeslaCrytpo

  • Rank

Recent Profile Visitors

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

  1. I would rather have the mux operation inside the XADC versus the cross talk with external MUX. That is part of the appeal of the Cora board where so many analog pairs are brought to the header. For CMODA7 doing this while consuming some pins that would normally be dedicated to digital is fine; but just need more pins on the CMOD S7 for analog inputs.
  2. The CMOD S7 with at least 4 more analog inputs. If possible, add 6 more analog inputs to bring the total to 8. The XADC has the channels, the pins are are just not exposed. In a similar fashion, the CMOD A7 board has 2 analog inputs, but many pins that could be accessed as analog inputs (deferentially, of course) making it reasonable to have several analog inputs to the XADC on the CMOD A7 (both variants, 15 and 35.) Thanks. James
  3. Thanks for the feedback Ana-Maria, and I was able to successfully program the CMODS7 this way as you described. Additionally, I also approached it by attached the .ELF file in Vivado and programming the configuration flash directly from the hardware manager. Both ways work. The main difference is that once you have a working design in SDK you have to go back to Vivado to use hardware manager as shown below versus programming the flash directly in SDK. I think the key factor or point to mention is that the Microblaze program is running out of block RAM on the CMOD S7, versus running o
  4. I am starting with working design for the CMOD S7 where I program the device through SDK and all functionality works as intended. Now where I am falling short is getting the program to run out of the SPI Flash. I have been following the "How To Store Your SDK Project in SPI Flash" guide from Digilent in order to put a Microblaze design into SPI Flash on the CMOD S7 located at the link here: https://reference.digilentinc.com/learn/programmable-logic/tutorials/htsspisf/start There is a recommended offset of 0x00300000 for the CMOD A7 - My question is what is the recommended o
  5. TeslaCrytpo

    CMOD S7 STP FIle

    There is a 3D stp file available for CMOD A7 board, but I do not see one for the CMOD S7 board. Is one available? Thanks. James
  6. I have performed an experiment, where I've disabled the interrupt controller C code functions as shown below and re-run the system. I tested by very basic two command parser and it responds correctly! From this test, it appears that configuring the interrupts has no value, as I've disabled them and the system works. Apparently, creating an interrupt controller in the fpga fabric is unnecessary. Thanks. James /******************************************************************************/ /** * * @file Take from - xuartlite_intr_example.c from Xilinx * * Mod
  7. Additionally, I have drawn some insight from these posts: 1) The question is raised as to whether an interrupt controller is necessary in the fabric at all as detailed in this link: https://forums.xilinx.com/t5/Embedded-Processor-System-Design/running-the-AXI-UART-Lite-irq-examples-on-Zynq-AXI-intc-vs-PS/td-p/867810 2) The same question that I raised was also raised previously but without a definitive answer. https://forums.xilinx.com/t5/Embedded-Processor-System-Design/UARTLite-Interrupts-Not-Working-on-Zynq/td-p/651594 I was just wondering if anyone at Digilent has s
  8. Hello All, I have an issue getting the interrupts to work on a Uart placed in the FPGA fabric and connected to the Zynq processor on a Cora Z7-10 board. Also, thanks to the help from jpeyron to suggest the Zedboard example. What I have discovered in implementing a uart in the FPGA fabric and connecting it to Zync is that the interrupts do not seem to work !!! My code shown below functionally works, i.e. the basic command parser that I've implemented with a continuous loop (quasi-polling) does functionally work.However, the interrupts do not work whatsoever. I've seen other posts
  9. One additional comment is that I am attempting to use the uart completely in the PS portion of the Zynq/Cora versus having to use the uart in the fpga logic. Thanks, James
  10. Thank you for the feedback jpeyron, I appreciate it. I have looked through the SDK files for the Zedboard uart interrupt project that you sent. This is for uartlite, and I am wondering what I have to do in the Cora to use the uartlite versus the regular uart driver? If you have any thoughts there, would appreciate it. Kind Regards, James
  11. Hello All, I have a Coraz7-10 board where I have the uart working in send mode, but not in receive mode. The uart is configured to operate on an interrupt, and I'm using the xilinx example code. I have modified just slightly with some debug messages and the recv handler. Basically, I just want to "set" a signal when then handler occurs, and "reset" it in the main() loop. In the handler itself, I am just checking to see if the received data makes it there, confirming in debugger view of SDK with watch variables. However, rx data is never present. I'm new to Zync, so if ther
  12. I was really looking to combine the step file with the chipKit daughter card and have the view in Altium ... Great to show customers and overall pass the design review. I have measured everything with calipers, including the 50 mil offset in the in line headers and the 1.75" separation on the horizontal. I was really looking for the step file, if you don't have it, no worries. The CMOD's have step files and I have used them for such purposes in the past. Thanks, James
  13. I am looking for the mechanical .step files of the Cora board, just wondering if they are available. Thanks. James