Pin Assignment failed to be downloaded to the FPGA board

--- Quote Start ---

Hi, All,

I am using the Cyclone II DE board and had a strange problem.

Once I changed the pin assignment, e.g., I changed the reset signal from push button KEY0 to KEY1; then I re-compiled the project and downloaded it again on to the board. Surprisingly, when I monitored the signals using SignalTap, it seemed that the "reset" signal was still controlled by the previous setting, namely KEY0, how come??

I tried to download again and again but seems the pin assignment never got changed to tally with my new assignments. I am now really confused, really hope some one could help~ =)

Thanks a lot!

Regards

grit

--- Quote End ---

first have look into the <>.pin file. It is locaterd in the Quartus RunDir. Search for your signal and check whether the assignment changed or not.

If not, how do you change the assignment ? Using the Assignment Editor ? Which Version of Quartus do you use ?

Kind regards

GPK

--- Quote Start ---

first have look into the <>.pin file. It is locaterd in the Quartus RunDir. Search for your signal and check whether the assignment changed or not.

If not, how do you change the assignment ? Using the Assignment Editor ? Which Version of Quartus do you use ?

Kind regards

GPK

--- Quote End ---

Hello, GPK,

Thanks for replying!

Now the problem seems have gone. The solution is that I re-added nodes inside the SignalTap each time I changed the pin assignment in Pin Planner, and then re-compile.

I am using Quartus II 9.0 SP2.

Thanks once again.

--- Quote Start ---

Hello, GPK,

Thanks for replying!

Now the problem seems have gone. The solution is that I re-added nodes inside the SignalTap each time I changed the pin assignment in Pin Planner, and then re-compile.

I am using Quartus II 9.0 SP2.

Thanks once again.

--- Quote End ---

Hi,

I observed a similar problem with Quartus II 9.1. When you use post-fitting nodes in Signaltap the Partition Top ( that is a defalut partition in every project) preserve Level is set to "Placement & Routing" and a new pin assignment will be ignored. Look into your messages, I sure sure you will find an info about this issue.

Kind regards

GPK