Skip to main content
Jan Breuer
Jan Breuer
Associate II
December 14, 2017
Question

[proposal] Public STM32CubeMX issue tracker

  • December 14, 2017
  • 3 replies
  • 1728 views
Posted on December 14, 2017 at 13:10

There are lot of bugs in STM32CubeMX and its components. Having public issue tracker will simplify the situation with reporting all issues and tracking their status.

Idally, having public source code of STM32CubeMX can also atract community to fix these issues and send Pull Requests to ST developers. Waiting more then year (or forever) for fixing a bug is not ideal situation.

What do you think, ST?

#bug #stm32cubemx
This topic has been closed for replies.

3 replies

Jeanne Joly
Jeanne Joly
Associate
February 23, 2018
Posted on February 23, 2018 at 09:55

Hello

Breuer.Jan

,

Thanks for taking time to share your point of view on the ST forum.

I agree thatit is not normal when it took more than a year to fix a correction however, as you may know, the delay of a fix could depend on the complexity, the project priorities, the marketing decisions and of course, the availability of the development team. And you can be sure that we do our best to have a reliable solution and a CubeMX tool that evolve according to customer requests .

Regarding your point on public source, a study to have the FW library on github is in progress. However, I can't give you anymore details for the moment.

It is a first step that do not fully answer your request but we keep your idea in mind and we are in the way to have some changes regarding the availability of the source code.

BR. Jeanne

Jan Breuer
Jan BreuerAuthor
Associate II
February 23, 2018
Posted on February 23, 2018 at 15:08

Hello

Joly.Jeanne

‌,

I understand the situation and the priorities and it was just a suggestion.

So I'm surprised and very happy to hear that you are really doing that study.

BR. Jan

henry.dick
henry.dick
Associate II
February 23, 2018
Posted on February 23, 2018 at 16:16

It helps to have a publically accessible bug submission mechanism. it can be hosted off ST's website for example.

giving the public the ability to view the bugs submitted would be a dead weapon your competitors can use against you (as a chip maker).

If I were NXP/TI/'you-name-it chip maker', my first market slide would be a link to that report of bugs,

Jan Breuer
Jan BreuerAuthor
Associate II
February 23, 2018
Posted on February 23, 2018 at 16:40

There are at least two points of vew.

From the marketing point of view, it is sad, that many decisions about used chips are done by managers and not with cooperation with developers. So many dumb managers will listen just to buzzwords and understand this as weapon againts ST. This is reality, it is sad and I understand your opinion.

From developer point of view, it will be always weapon against ST's competitors. Like 'Hey, they have bug tracker with 1000 bugs but 980 from them are already solved. Thats great and really impressive!'

henry.dick
henry.dick
Associate II
February 24, 2018
Posted on February 24, 2018 at 02:00

'There are at least two points of vew.'

i'm sure. but the fact that noone is doing it should be enough to make you think really hard as to why it is smart for you to buck the trend.

'From developer point of view, it will be always weapon against ST's competitors. Like 'Hey, they have bug tracker with 1000 bugs but 980 from them are already solved.'

let's say that you do run up two otherwise identical chip makers, one usually has an errata of 20 items in it, and another usually has 1000 bugs (99.9% fixed however, by now). you think you are going to go with the guy with 1000 bugs consistently on its chips?

if it becomes known that a vendor often has 1000s of bugs in its chips (early release), any sane person would say 'let's go with somebody else', or if you really want to go with this guy, 'let's wait for them to work out most of those bugs'.

a public bug submission is great; a public bug report is suicidal.

T J
T J
Senior III
February 24, 2018
Posted on February 24, 2018 at 12:21

We have been working around bugs, since forever.

ST, HAL and the CUBE, seems a good team,

Stable and robust after the misunderstandings subside.

The substructure of HAL-ARM interface seems ultra reliable

disfunction()

{

    I don't want to mention the wife.

    My advice is : Be careful what you wish for and be thoughtful how you ask.

    Flowers work.

:}

ST is better to wait for a good idea to come along.. ( does that sound like my wife or what ?)

I would suggest ST has a keen ear for you all.       ( she is listening from a mile away)

We need some flowers to get real progress

Terms & ConditionsAccessibility statement