Actions
Forum Thread Details
  • State Not Answered
  • Replies 4 replies
  • Subscribers 360 subscribers
  • Views 565 views
  • Users 0 members are here
Related

vivado 2014.4 lab8 error :../src/main.c:61:38: error: 'XPAR_FABRIC_PWM_W_INT_0_INTERRUPT_OUT_INTR' undeclared

e14 Contributor

Hi

I was exactly doing the instructions in lab 8 then I faced error below:

../src/main.c: In function 'SetupInterruptSystem':
../src/main.c:61:38: error: 'XPAR_FABRIC_PWM_W_INT_0_INTERRUPT_OUT_INTR' undeclared (first use in this function)
#define INTC_PWM_INTERRUPT_ID        XPAR_FABRIC_PWM_W_INT_0_INTERRUPT_OUT_INTR
                                      ^
../src/main.c:128:50: note: in expansion of macro 'INTC_PWM_INTERRUPT_ID'
  XScuGic_SetPriorityTriggerType(IntcInstancePtr, INTC_PWM_INTERRUPT_ID
.
.
.



  • 0

    Hi nariman_nsi,

    That lab was originally developed in 2013.3 so the error that you report likely has somethign to do with a change in the tools to version 2014.4 of Vivado.  Specifically, the way that the interrupt number is named during the creation of the BSP may be different now.

    Take a look in the BSP project for the application where you are seeing the error.  Within the BSP you should find a folder which contains the includes which describe the hardware platform settings to your C application.

    Take a look in the hardware parameters file ps7_cortexa9_0/include/xparameters.h and see if you can find the interrupt definition (should be similarly named to XPAR_FABRIC_PWM_W_INT_0_INTERRUPT_OUT_INTR) and then adjust the definition line in your main.c to match the new definition:

    #define INTC_PWM_INTERRUPT_ID <name of interrupt that you find in xparameters.h>

    If you cannot find an interrupt definition within xparameters.h, go back and double check your hardware platform from Lab 7 to make sure that the interrupt was connected and enabled properly.

    Regards,

    -Kevin

  • 0

    Hello, 

    Same error on 2015.3.   Took your advice and, yes, you make the #define non-empty it compiles.  Is it the correct define though?

    I changed it to

    #define INTC_PWM_INTERRUPT_IDt       XPAR_PWM_W_INT_0_DEVICE_ID

    which is '0' - is this correct (there are no other interrupts in the system)?

    What was the original?

    Thanks, ~Tom

  • 0

    Hi,

    The correct solution is please update(replace) the IPs with new IP, i mean to say except PWM controller change replace all the IPs with new IPs(AXI BRAM CONTROLLER and ZYNQ processing system is mandatory to change ). Then u will find this signal (#define XPAR_FABRIC_PWM_W_INT_0_INTERRUPT_OUT_INTR 61) in xparameters.h

    Thank u