STM32Cube repository on Github

[viacheslav]

Posted on August 26, 2014 at 14:15

Why does ST not use Github for STM32Cube?

It would be better to get any official updates from the official Git repository as soon as possible rather than sitting and waiting for the new official zip-file complete release. Also I'm ready to contribute my bugfixes and improvements to the HAL sources via pull requests.

[Montassar BEN ROMDHANE_O]

Posted on August 28, 2014 at 10:45

Hi dobromyslov.viachesl,

We hear your frustration and take all feedback and suggestions into consideration. ST is working to improve the STM32Cube experience for everyone, and make firmware development more collaborative by targetting a similar solution in our future plans. 

Thanks for your participation!

With regards.

[AVI-crak]

Posted on July 02, 2017 at 17:02

GitHub, bitbucket and a whole bunch of free repositories.

The location of the program code STM32Cube is beneficial for the st. Users themselves will find errors, create their own branches, the administration will need to check the already ready solution - to the place and time of error detection.

This is much easier than discussing through a forum where most users sometimes can not formulate their problem.By the way, bitbucket + turtle

https://tortoisehg.bitbucket.io/

is much easier to learn by beginners than the same GitHub.

[vahid4134]

Posted on October 04, 2015 at 08:59

this is good suggest

[joe23]

Posted on December 14, 2015 at 22:08

This would be great. I have found numerous bugs in STM32Cube and the code it creates. I would love to see both STM32Cube and the HAL drivers on github as well where we could submit and discuss pull requests.

[thln47]

Posted on December 15, 2015 at 12:10

I agree with dobromyslov.viachesl suggestion,

I used HAL driver since a few weeks, and I already found many bugs on STM32F3xx_HAL_Driver and STM32_USB_Device_Library.

I hope ST will use a Git repository, as soon as possible.

[nikola1010]

Posted on December 15, 2015 at 13:53

Dear ST,

there exists large number of people who would gladly help you with testing. Put it on github so we can provide more hands on testing.

[schelven]

Posted on December 15, 2015 at 14:01

I vote for gitgub too !

[philip239955]

Posted on December 15, 2015 at 19:57

What bugs have you found in the USB device library? My company is trying to bring a USB device to market rapidly using STM32Cube, and I've found a bug where the order of the interrupt handlers seems to cause the HAL driver to get stuck in the USB busy state, leaving it unable to send any more IN transfers. I'll create a separate topic for the bug report with my proposed fix, but it would be ideal to move the whole development process to GitHub.

Philip Bliss

[Amel NASRI]

Posted on December 17, 2015 at 15:30

Hi All,

Please note that your request to manage STM32Cube on GitHub is shared internally. So it will be under review.

Waiting for a solution that meets your expectation, could you please report the problems and bugs you are facing or any other feedback on our STM32 related forums (if possible in separate discussions)?

-Mayla-

[Rob.Riggs]

Posted on July 02, 2017 at 04:01

Hi

st.mcu

,

This is justa friendly reminder that ST's users would still like to see this.

Is this still being considered internally?

It would be much easier to propose fixes for HAL code as git pull requests than postingthem here. Also, I always havebug fixes for the HALthat must be re-applied every time a new version comes out from ST. It would be much easier to pull down new HAL versions with git and merge ST's changes with mine until the fixes are accepted by ST.

Thanks,

Rob

[carmine]

Posted on December 17, 2015 at 16:38

Placing Cube framework on github would be a great improvement.

+1

[Tesla DeLorean]

Posted on December 17, 2015 at 16:50

I'd vote for more internal code review and testing. A lot of the issues don't need more eyes, just critical ones. There needs to be stronger leadership in the manner this is tested and released. The bug list and tracking needs to be more transparent.

This is embedded, you can't be patching flaws every week like Adobe/Microsoft, it's not a model that works well.