Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 366 subscribers
  • Views 368 views
  • Users 0 members are here
Related

Speedway Lab 10 Difficulties

Former Member

Is anyone doing Lab 10 of the Speedway SW series and encountering the undefined value XPAR_FABRIC_PWM_W_INT_0_INTERRUPT_OUT_INTR in the examples? I have a complier error on this value that doesn't seem to be defined anywhere in the entire workspace.

Parents
  • 0

    I ran into the same problem using Vivado 2016.2, and here's what I did to fix it:

    The HW Block Diagram shows the PWM_w_Int_0 module's "Interrupt_out" net connected to the Zynq module's "IRQ_F2P[0:0]" port. From the Xilinx documentation I note that IRQ_F2P[0] is Interrupt ID 61, which is #define'd in xparameters_ps.h as "XPS_FPGA0_INT_ID". So I added a #include "xparameters_ps.h" to the top of my LED_Dimmer_Int.c file, and changed the #define INTC_PWM_INTERRUPT_ID to set it to XPS_FPGA0_INT_ID.

    Of course you could alternately short-circuit the extra #include by simply directly setting XPS_FPGA_INT_ID to 61.

    If there's a more "official" way to pass interrupt assignments via the hardware definition I'd love to know!

    - Richard

Reply
  • 0

    I ran into the same problem using Vivado 2016.2, and here's what I did to fix it:

    The HW Block Diagram shows the PWM_w_Int_0 module's "Interrupt_out" net connected to the Zynq module's "IRQ_F2P[0:0]" port. From the Xilinx documentation I note that IRQ_F2P[0] is Interrupt ID 61, which is #define'd in xparameters_ps.h as "XPS_FPGA0_INT_ID". So I added a #include "xparameters_ps.h" to the top of my LED_Dimmer_Int.c file, and changed the #define INTC_PWM_INTERRUPT_ID to set it to XPS_FPGA0_INT_ID.

    Of course you could alternately short-circuit the extra #include by simply directly setting XPS_FPGA_INT_ID to 61.

    If there's a more "official" way to pass interrupt assignments via the hardware definition I'd love to know!

    - Richard

Children
No Data