• Content count

  • Joined

  • Last visited

Community Reputation

0 Neutral

About JPElectric

  • Rank

Profile Information

  • Gender
    Not Telling
  1. JPElectric

    ZAP 2.3.0-- using Xilinx #include files

    Thank you, Magnus and Jack, for helping sort this out. It was apparent that the project was missing key items and your information clarifies what is missing. John
  2. JPElectric

    ZAP 2.3.0-- using Xilinx #include files

    >> Therefore the correct processor type must have been selected. >> I'm not sure what you mean by that. I mean FPGA-- you referred to a Microblaze EDK project; could this even work for a Spartan 6?
  3. JPElectric

    ZAP 2.3.0-- using Xilinx #include files

    It is not known how the bitstream was created; however Papilio Loader transferred it to a Papilio Pro and it is running with the UARTs and all I/O functions working correctly. Therefore the correct processor type must have been selected. The initial assumptions were that ZAP could use the *.vhd, *.ucf, and *.c files as input and somehow spit out a usable bitstream. What other (more laborious) methods could be used to accomplish this, using the ISE WebPACK, Papilio utilities, and avr-gcc (et. al.)?
  4. JPElectric

    ZAP 2.3.0-- using Xilinx #include files

    The project is a machine control comprising several *.vhd and one *.c file. The *.c file needs refactoring, bug fixes, and additional features. The C code is tightly coupled to the hardware, i.e.; XUartLite_SetRecvHandler(&UartLite, RecvHandler, &UartLite); It is not an option to implement this part of the system entirely in VHDL. Presumably the *.vhd files create a bitstream in ISE; the *.c file is compiled and linked with avr-gcc; then these two are merged in Papilio Loader "Write to: Disk File", which is then transferred to the Papilio. Correct? This project came with no project files for any IDE, not even a minimal Makefile for avr-gcc. There is a complete bitstream that is running the hardware on a Papilio, but there is no documentation on the steps used to create it. First the correct #include files for the Papilio/ Spartan 6 target must be identified from among their multiple instances in the ISE subdirectories. This would permit setting avr-gcc's CFLAGS I(nclude) switch in a Makefile, as a minimal solution to create the object file so refactoring can proceed. If this were to be entirely supported in ZAP, perhaps you can outline the steps involved, so any work done will parallel that effort.
  5. An inherited project has the following #includes in main.c: #include <stdio.h> #include <string.h> #include <stdlib.h> #include "xparameters.h" #include "xgpio.h" #include "xio.h" #include "xstatus.h" #include "xuartlite.h" #include "xtmrctr.h" #include "xintc.h" #include "xil_exception.h" ZAP 2.3.0 barfs on the Xilinx #includes: main.c:37:25: error: xparameters.h: No such file or directory main.c:38:19: error: xgpio.h: No such file or directory main.c:39:17: error: xio.h: No such file or directory ... Hardwiring the paths complicated this, as the referenced #includes reference others: #include "/opt/Xilinx/14.7/ISE_DS/EDK/sw/XilinxProcessorIPLib/drivers/gpio_v3_01_a/src/xgpio.h" results in: In file included from main.c:27: /opt/Xilinx/14.7/ISE_DS/EDK/sw/XilinxProcessorIPLib/drivers/gpio_v3_01_a/src/xgpio.h:123:23: error: xil_types.h: No such file or directory /opt/Xilinx/14.7/ISE_DS/EDK/sw/XilinxProcessorIPLib/drivers/gpio_v3_01_a/src/xgpio.h:124:24: error: xil_assert.h: No such file or directory /opt/Xilinx/14.7/ISE_DS/EDK/sw/XilinxProcessorIPLib/drivers/gpio_v3_01_a/src/xgpio.h:125:21: error: xstatus.h: No such file or directory Even if this worked, it is not evident which of the multiple versions of the various *.h files to reference (ppc405, microblaze, ppc440, cortexa9, ...) How are the Xilinx headers to be referenced in a ZAP project? There does not appear to be a place to specify the many directories where these files are located. Which ones should be included for the Papilio Pro?