How to add ISP1362 component to SOPC in DE2?

ISP1362:avalon_slave_1_irq:"associated addressable interface"(assocaitedAddressablePoint) out of range..

this is th error i got when i tried to upgrade the .ptf file of DE2_SD_Card_Audio to .sopc file,

anybody knows the solution to this please?

@San : I have got the same problem (with isp1362 in quartus v9.0), and have been stuck for a long time. If you or anyone have a solution, please share!

thank alot!

If you add the ISP1362 as a "New Component.." in SOPC builder, it will bring up the Component Editor window.

Switch to the Signals tab, and for OTG_ADDR, click the Interface entry and select "New Conduit". This should create a new conduit called "conduit_end". Use this as the interface for all of the OTG_ signals. Change the Signal Type for all of the OTG_ signals to "export".

Create new interrupt sender interfaces for irq_n and irq_n_avalon_slave_1. set them both to signal type irq_n.

On the Interfaces tab, set the interface address source (?) under interrupt_sender to be avalon_slave_0. Use avalon_slave_1 for interrupt_sender_1.

Set the slave addressing (under deprecated for avalon_slave_0 and 1) to NATIVE. Set the timing to use ns, and the setup, r/w wait, and hold delays to be 100ns each.

This should get you past the SOPC errors...

A relatively simple method ：there is ISP1362_IF_hw.tcl in folder \ip\TERASIC_ISP1632 with DE2_70_NIOS_HOST_MOUSE_VGA project from de2-70 broad demonstrations!

You can copy out ISP1362_IF_hw.tcl into your builded project directory !

then,open SOPC builder ! So SOPC builder's System Contents display ISP1362 component !

Hello !

Sorry to unburry this thread, but it needs a little clarification and/or update. 2 methods were given to integrate the isp1362 component from the demonstration project called "DE2_HOST_MOUSE(...)" (v7.1) in your SOPC builder (v>10).

The first is to put the ISP1362 directory in your project directory so that SOPC builder loads it and upgrade it by itself. In my Quartus v11 this leads to really unclear errors.

So a kind member gave us the method to upgrade it by ourselves. This is very nice but also very disturbing because a little bit more details would be enough to get beyond this !

Here

--- Quote Start ---

"Switch to the Signals tab, and for OTG_ADDR, click the Interface entry and select "New Conduit". This should create a new conduit called "conduit_end". Use this as the interface for all of the OTG_ signals. Change the Signal Type for all of the OTG_ signals to "export"."

--- Quote End ---

OK that was easy : (cf : well.. first post can't post image...)

--- Quote Start ---

Create new interrupt sender interfaces for irq_n and irq_n_avalon_slave_1. set them both to signal type irq_n.

--- Quote End ---

?? Where is irq_n ?

--- Quote Start ---

On the Interfaces tab, set the interface address source (?) under interrupt_sender to be avalon_slave_0. Use avalon_slave_1 for interrupt_sender_1.

--- Quote End ---

Mmmh... nope can't see either

--- Quote Start ---

Set the slave addressing (under deprecated for avalon_slave_0 and 1) to NATIVE. Set the timing to use ns, and the setup, r/w wait, and hold delays to be 100ns each.

--- Quote End ---

Ah ! This one's easy !

I'm pretty sure it isn't that hard even more if you have read a tuto on how to build a SOPC component but a lot of people would be glad to have a little help on this ;-) !

On the Signals tab, you should have two signals named "irq_n" and "irq_n_avalon_slave_1".

For both of these, click on the interfaces field and select "new interrupt sender...". This should give you "interrupt_sender" and "interrupt_sender_1". For each of these updated lines, set the signal type to "irq_n".

Only once you've created these new interrupt senders will they show up in the right place on the Interfaces tab. Now go down to the "interrupt_sender" and "interrupt_sender_1" sections and pick the right avalon_slave from the "Associated addressable interface" pulldown in the Parameters section.

Still on the Interfaces tab, go to the "avalon_slave_0" and "avalon_slave_1" sections. Update the timing section to use nanoseconds, and set the setup, read wait, write wait, and hold delays to be 100ns for both. Go down a bit to the "Depreacated" section of each interface, click the triangle and set the slave addressing to use NATIVE instead of DYNAMIC.

This works for me using Quartus 11.0 and SOPC builder.

Thanks for the answer ! I had given up trying to have the two interupts. Instead I configured the ISP1362 to send both on one bit !

Good luck to any person doing USB !

I'm using Terasic's provided DE2_NIOS_DEVICE_LED project to try and get ISP1362 working. I opened the Quartus project file, then opened SOPC Builder and was prompted to update the components. I clicked upgrade ISP1362 and followed wtfe's instructions. The first step was OK, but there are [bold]no irq_n and irq_avalon_slave_1 signals listed in the Signals tab[/bold]. The "Add Signal" button is also greyed out.

However, if I skip the first step, I can add one signal (irq_n) and then do the OTG_ steps but I can't add another signal.

I also don't have "avalon_slave_1" listed in the Interfaces tab (only "clk", "avalon_slave_0_export", "avalon_slave_0", "avalon_slave_0_irq", "avalon_slave_1_irq", "interrupt_sender", and "conduit_end")