Actions
Forum Thread Details
  • State Not Answered
  • Replies 3 replies
  • Subscribers 366 subscribers
  • Views 367 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

    Hello Richard,

    We are actually in process of updating those labs to 2016.2. I recently ran into the same issue as you did with the interrupt_out. The issue stems back all the way to zynq hardware lab 7 when you are packaging your custom IP. In the IP packager under Ports and Interfaces, you will see your interrupt_out port. If you look at the properites on it you will notice that it is labeled as undefined. Right click on it and go Auto Infer Single Bit Interface --> Interrupt. That should fix the problem witht he parameter not passing properly into SDK.

    --Josh

Reply
  • 0

    Hello Richard,

    We are actually in process of updating those labs to 2016.2. I recently ran into the same issue as you did with the interrupt_out. The issue stems back all the way to zynq hardware lab 7 when you are packaging your custom IP. In the IP packager under Ports and Interfaces, you will see your interrupt_out port. If you look at the properites on it you will notice that it is labeled as undefined. Right click on it and go Auto Infer Single Bit Interface --> Interrupt. That should fix the problem witht he parameter not passing properly into SDK.

    --Josh

Children
No Data