STM32F030X8 alternate function unclear

[Valeriy Horash]

Posted on November 08, 2017 at 21:05

In the STM32F030X8 datasheet the PortB pin 15 alternate function AF0 is both SPI1_MOSI and SPI2_MOSI

(see table 13 on page 35 of en.DM00088500.pdf). The pin 15 is just an example - there are more of such.

How can this be resolved? Is there some other register that specifies the SPI module to connect to the pin?

#gpio-alternate-function-ambiguity

[Uwe Bonnes]

Posted on November 08, 2017 at 21:27

Look at the alternate function register. Look at table 12 to 16 in the datasheet

[Tesla DeLorean]

Posted on November 09, 2017 at 00:25

Seems like a bond-out specific either/or, should be notes indicating which part provides what. Similar thing goes on with the USART

[waclawek.jan · Accepted solution]

Posted on November 09, 2017 at 01:28

How can this be unclear?

Seems like a bond-out specific

No, these are simply completely different chips.

Btw. do you remember how did the 'F030 happen, that it was clearly said to be only a less-tested 'F051? The 'F030x8 is identical to 'F051.

JW

[Tesla DeLorean]

Posted on November 09, 2017 at 03:03

>>

No, these are simply completely different chips.

I was trying to be charitable, as there really shouldn't have been a need to do stupid stuff like this, there are enough empty AF slots for this to have been achieved in a coherent way across die and package combinations.

Perhaps after a long lunch, and high CO2 levels in the conference room?

I would have use some of the empty AF slots on other designs to switch USART RX/TX pairing

[Valeriy Horash]

Posted on November 09, 2017 at 07:01

Thank you Jan! I read through these remarks several times, but did not get it, untill you point it.

[waclawek.jan]

Posted on November 09, 2017 at 09:13

Perhaps after a long lunch, and high CO2 levels in the conference room?

 :D

[Uwe Bonnes]

Posted on November 09, 2017 at 10:40

Have also a look at the SYSCFG_CFGR1 for remapping functions.