cancel
Showing results for 
Search instead for 
Did you mean: 

STM32F746G Discovery Arduino D10 Pin confusion ... Bug?

Posted on June 09, 2018 at 11:23

Hi,

I have tried

to use the PWM output on Arduino UNO connector D10 on my STM32F746G Disco.

It is a bit confusing because different documentations show different pin sources for this pin.

  • actual ST Cube Tool shows: ARUDINO PWM / D10 - PI0, TIM5 CH4
  • actual User Manual UM1907 shows: PWM/D10 - PA8, ARD D10, TIM1 CH1
  • actual Schematic Pack STM32F746G-DISCO schematics  (MB1191) shows: PWM/D10 - PI0, TIM5 CH4

My Logic Analyzer on my Hardware MB1191 B-01 shows PA8, ARD D10, TIM1 CH1 is the right one...

So my conclusion, ST Cube and schematic pack show the wrong pins PI0, User Manual shows the right Pins in combination with my HW Version MB1191 B-01.

Is this a bug in the documentation and Cube or is there a hardware change on the board and the user manual is to old?

Thanks a lot!

#st-cube #documentation #stm32f746-discovery #bug?
4 REPLIES 4
Posted on June 09, 2018 at 17:40

https://community.st.com/0D50X00009XkgDCSAZ

https://community.st.com/0D50X00009XkZ5xSAF

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
Posted on June 09, 2018 at 17:51

Hi Clive One

thanks,

then I think the problem seems not to be solved since Jul 22, 2015 ...

Posted on June 09, 2018 at 19:54

I think the user manual got fixed, D10=PA8, D5=PI0, but the schematic and CubeMX continue to propagate the original error.

At this point the problem has spread so far and wide it probably isn't something that can ever totally be remedied. Still my original comments seem prescient, it is a pity the port to Jive gnarled up so many of the links, the original test port of the forum to Jive was a lot cleaner.

Tips, Buy me a coffee, or three.. PayPal Venmo
Up vote any posts that you find helpful, it shows what's working..
Posted on June 22, 2018 at 09:57

Hi

mikrocontrollerproje

,

I confirm it is a bug in CubeMX and it will be fixed in next release.

Thanksfor rising this problem.

regards,

Mohamed.