Max 10 pin assignment issue

[MinzhiWang]

Hello Guys,

We are using Max 10 device, the part number is "10M25DAF484C7G". Our Quartus version is 23.1std.0991 standard edition.

There are several ADC input buses which are connected to Max 10. However, several of them have pin assginment issue, as following image show.

After compilation, Quartu dosen't use our assigned pin location. It changes to other pin location.  Why can this happen? And how to resolve it?

BTW, I checked the messages, and found the following warning messages:

Warning (15705): Ignored locations or region assignments to the following nodes
	Warning (15706): Node "M10_ADC_A1_OUT[0]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_A1_OUT[1]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_A1_OUT[2]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_A1_OUT[3]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_A1_OUT[4]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_A1_OUT[5]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_A1_OUT[6]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_A1_OUT[7]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_A1_OUT[8]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_A1_OUT[9]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_B1_OUT[0]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_B1_OUT[1]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_B1_OUT[2]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_B1_OUT[3]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_B1_OUT[4]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_B1_OUT[5]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_B1_OUT[6]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_B1_OUT[7]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_B1_OUT[8]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_B1_OUT[9]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_C1_OUT[0]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_C1_OUT[1]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_C1_OUT[2]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_C1_OUT[3]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_C1_OUT[4]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_C1_OUT[5]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_C1_OUT[6]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_C1_OUT[7]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_C1_OUT[8]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_C1_OUT[9]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D0_OUT[0]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D0_OUT[1]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D0_OUT[2]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D0_OUT[3]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D0_OUT[4]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D0_OUT[5]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D0_OUT[6]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D0_OUT[7]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D0_OUT[8]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D0_OUT[9]" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D1_OUT0" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D1_OUT1" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D1_OUT2" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D1_OUT3" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D1_OUT4" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D1_OUT5" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D1_OUT6" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D1_OUT7" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D1_OUT8" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_ADC_D1_OUT9" is assigned to location or region, but does not exist in design
	Warning (15706): Node "M10_TO_C10_LVDS_RESERVED_CLK" is assigned to location or region, but does not exist in design

 

[sstrell · Accepted solution]

You have signals named incorrectly (OUT vs. Out).  You should not enter signal names manually in the Pin Planner.  They will appear there after Analysis & Elaboration so you can select location and other I/O-related assignments.

[MinzhiWang]

Hi sstrell,

Yes, you are right. We apply constrain thru TCL script files. The pins assignment include two parts, however, the two groups assignment names have tiny difference. So Quartus takes them as two different objects.

Thanks for you remind.

[AqidAyman_Intel]

Hi MinzhiWang,

I'm glad the answer from @sstrell does helps you.

Do you need any more support on this issue?

Regards,

Aqid

[MinzhiWang]

Hi Aqid,

No, it's enough for us. We have resolve this issue now.

[AqidAyman_Intel]

I’m glad that your question has been addressed, I now transition this thread to community support. If you have a new question, Please login to ‘https://supporttickets.intel.com’, view details of the desire request, and post a feed/response within the next 15 days to allow me to continue to support you.