Forum Discussion
Altera_Forum
Honored Contributor
10 years agoHello Brad,
Here are some answers to your questions: --- Quote Start --- So if I understand you correctly, if you didn't make any changes to the .dts file then the entry for this component in the device tree blob was still set to 1, correct?If that's the case then what IRQ did the kernel end up using? There seems to be a direct conflict between the IRQ setting in Qsys (IRQ 4) and the .dts/.dtb file (IRQ 1). I have always had problems if the IRQ settings in the Qsys system and the .dts/.dtb files didn't match. --- Quote End --- There is some misunderstanding. I said we didn't make any MANUAL change. As .sopcinfo had updated, we had to re run sopc2dts utility. So with new dts, device tree blob was set to 4 (same as assigned in Qsys) --- Quote Start --- I assume you are using Linux as your OS (or are you using a HAL-based system?). --- Quote End --- Yes, we are using Linux. --- Quote Start --- If you are using Linux would it be possible for you to run the "cat /proc/interrupts" command to see how the interrupts mapped to the kernel. --- Quote End --- We will try it tomorrow. --- Quote Start --- Also, could you tell me what IRQ you have assigned to your USB Host Controller? Can you say which manufacturer of the USB Host Controller core you are using? --- Quote End --- IRQ 2 have been assigned to USB Host Controller and IP core is from System Level Solutions (I) Pvt. Ltd. Let me know if you have any other confusion. Thanks, Bhaumik