cancel
Showing results for 
Search instead for 
Did you mean: 

How are non-existent pins / ports wired up

Danish1
Lead II

Does anyone have any experience of trying to control non-exisistant pins?

I have a design that takes stm32f767 in the lqfp100 package. But none seem to be available.

Looking around, I managed to procure a small run of stm32f779* in the wlcsp180 package, and I plan to make an adapter board so that they may be placed on my main board.

As far as I know, those processors are very similar so I intend to have the same firmware for both. The might even have the same die (i.e. chip), just that the unused pins are not bonded out.

Because the wlcsp180 omits certain pins present on the lqfp100 (PC2 - PC5), I plan to make a few minor changes to the pin-out. I want my code to auto-detect which processor is in use, and drive the appropriate pins.

My idea was that I could tie a pin on the wlcsp180 adapter board that isn't present on lqfp100. And then if I pull that pin either high or low and it follows both pulls the tie cannot be present and it must be the lqfp100 package.

But when I tried this with pin PF4 on my stm32f767VIT6 (taking care to enable the clock to GPIOF), the pin always read back as 0 - even if I was pulling or driving it high. So it might be that port F, which does not seem to be used at all on lqfp100, is not functional rather than just not bonded.

Is there a better pin to use? How might I detect which processor/package is present at run-time?

Regards,

Danish

*I only bought enough to cover one year's expected sales, a small fraction of what the distributor had at the time. And I see they are now all sold out.

2 REPLIES 2
TDK
Guru

My experience is that they always return 0 as well. I don't believe it is something that is specified.

If you have 1-2 free pins, you can tie those to ground on one one board while leaving them floating on the other and use pullups to determine which is which. Or if pins exist on one device and not on the other, you get this for free unless you tie them to ground.

The DEV_ID is the same between these packages so no help there.

If you feel a post has answered your question, please click "Accept as Solution".

That might explain why some absent pins are explicitly labelled as "NC" where most of the others are identified as "-".

The data sheet, in the notes for Table 11 pin and ball definitions says:

  1. NC (not-connected) pins are not bonded. They must be configured by software to output push-pull and forced to 0 in the output data register to avoid an extra current consumption in low-power modes. list of pins: PI8, PI12, PI13, PI14, PF6, PF7, PF8, PF9, PC2, PC3, PC4, PC5, PI15, PJ0, PJ1, PJ2, PJ3, PJ4, PJ5, PH6, PH7, PJ12, PJ13, PJ14, PJ15, PG14, PK3, PK4, PK5, PK6 and PK7.

So by implication, pins labelled "-" are tied to Vss to prevent class-A current when a pin is programmed to be a floating digital input