This forum's view

My own estimate - feel free to suggest other percentages:

90% of serial-port problems are probably generic.
70% of CAN questions
80% of uVision questions.
90% of "how do I ..." questions
50% of compiler problems
...

Beginners have a tendancy to start with very narrow and specific questions - but not because the question really is specific to a chip or compiler, but because they base the question on their knowledge instead of basing it on their lack of knowledge.

Instead of presenting a set of known facts and what they have done to get forward, they present a single fact with the assert: "this is wrong" and the question "why".

And most of the really processor-unique questions are so very unique that the number of people who can help may be very small. But remember: A lot of ARM developers have working knowledge of C51 chips, besides their "general" embedded knowledge.

In the end, my post about grading of people was no joke. You could give people scores and filter away noobs. That would make _your_ day nice. But only _if_ you have already spent the time gaining the required rank. You would have to "earn" your right to get a noise-free forum. But such a forum would be totally uninteresting for new Keil customers. They would get here with possibly very relevant questions but not be able to break through the "noob" filter until they have spent time helping real noobs. Obviously, a professional developer with a professional need can't afford the loss of calendar day for such a setup. And real noobs would never be able to break through the filter, so only Keil staff or very, very nice readers would spend the time helping the true noobs.

A separation on architecture on the other hand tends to put separating lines where no (or very weak) lines exists, since the synergy is so very high. The important factor is "embedded", not the marking on the processor.

My own estimate - feel free to suggest other percentages:

90% of serial-port problems are probably generic.
70% of CAN questions
80% of uVision questions.
90% of "how do I ..." questions
50% of compiler problems
...

Beginners have a tendancy to start with very narrow and specific questions - but not because the question really is specific to a chip or compiler, but because they base the question on their knowledge instead of basing it on their lack of knowledge.

Instead of presenting a set of known facts and what they have done to get forward, they present a single fact with the assert: "this is wrong" and the question "why".

And most of the really processor-unique questions are so very unique that the number of people who can help may be very small. But remember: A lot of ARM developers have working knowledge of C51 chips, besides their "general" embedded knowledge.

In the end, my post about grading of people was no joke. You could give people scores and filter away noobs. That would make _your_ day nice. But only _if_ you have already spent the time gaining the required rank. You would have to "earn" your right to get a noise-free forum. But such a forum would be totally uninteresting for new Keil customers. They would get here with possibly very relevant questions but not be able to break through the "noob" filter until they have spent time helping real noobs. Obviously, a professional developer with a professional need can't afford the loss of calendar day for such a setup. And real noobs would never be able to break through the filter, so only Keil staff or very, very nice readers would spend the time helping the true noobs.

A separation on architecture on the other hand tends to put separating lines where no (or very weak) lines exists, since the synergy is so very high. The important factor is "embedded", not the marking on the processor.

Sorry, but I'm not a beginner and if I search for one architecture topics I don't waste my time reading the other threads, too less time.

And I know that the register sets from a C166 is completely different than the LPS-set.
So what kind of information is inside a thread with the other architecture?

If you have the time to read all the threads to look where you can help, it's your turn.

I just asked to add filter buttons which I can use, not must use!

.

G.K

I guess it is an issue of motivation. Some people here actually enjoy lending a helping hand, others are strictly looking for answers. I think this forum should primarily serve the first group of people.

And they can't help if there are filter buttons given to that users who like to switch off a MCU-family?

Is it too complex for that guys which think, that they can help, to handle few buttons?
Are you unable to leave buttons unpressed?

Ok, I understand you, thanks.

G.K.