Forum Discussion

Muralidharan's avatar
Muralidharan
Icon for New Contributor rankNew Contributor
2 years ago

Intel Max 10 FPGA VCC and GND short after few days

Hi, Greetings! History: We are using Intel 10M25SAE144I7G FPGA in the design. Rev1 Board is working fine, in the Rev 2 Board we used the same FPGA design code and some of the pins assigned as input/ ...
Board Debug
Zawani_M_Intel's avatar
Zawani_M_Intel
Icon for Frequent Contributor rankFrequent Contributor
2 years ago

Hi Muralidharan,


It is best to tie a non-driven input to something (eg. GND or VCC) instead of leaving it floating to prevent inadvertent toggling.

A non-driven input could toggle from board noise and such and draw unwanted current.


If you have unused general purpose IO that do not have a signal assigned to it, it’s also a good idea to have it basically tied to some know value (eg. GND or VCC).

Quartus has the option to set unused IO as an output driving GND or an input with weak pull-up.

Yes, the idea is to prevent inadvertent toggle and thus unwanted current draw.


If the worst scenarios happened, it is possible enough signals and current going into a pin and can damage the pin.

From now you will observed sudden heat, pin shorted to GND and even the device death.

This is Electrical Overstress phenomenon.


Regards,

Wani



Muralidharan's avatar
Muralidharan
Icon for New Contributor rankNew Contributor
2 years ago

Hi Wani,

Thanks for your Feedback!

Non- Driven input pin, I'll connect to GND.

What about Non-Driven Output pin? Any suggestion here?

Attached the input and output pin details which is defined in the FPGA Pin Planner for Rev1 Board and unused in Rev2 Board and left floating.

We are using the same FPGA design files in both of our custom board Rev1 and Rev2.

Thanks,

Muralidharan G