This forum seems to be new, we all have problems, everyone looks and nobody brings solutions.

[Fernando1]

This forum seems to be new, we all have problems, everyone looks and nobody brings solutions. The official support only gives code to verify the neural network, but I do not want to verify, I want to predict, I want to use the neural network in the microcontroller, I have already passed the verification stage. Some help please with the functions and initialization to be able to use the neural network. regards

[Tesla DeLorean]

The pay for doing support work is just awful here, hard to attract talent when support has no value.

[Jack Peacock_2]

It does reinforce my faith in my fellow man that programmers are every bit as altruistic as lawyers, willing to donate hundreds of hours of free labor so students don't have to actually learn something.

The forum isn't really all that new. Ten years ago it was primarily ARM7 and ARM9 controllers. Not many software question about the SPL, mostly requests for help on understanding how the hardware worked. I still use the SPL, a practice validated on a daily basis when I see the number of HAL related posts.

Ironically the lack of initiative benefits those of us quite near retirement age. Not easy to find programmers (and no, I won't use 'software engineer', an engineer is the guy who ***** the whistle at the RR crossings) to do anything more complex than the latest Javascript Framework for a storefront website. This last week I spent most of my time troubleshooting problems from outsourced hardware designs. I'd like to personally encourage everyone on the forum to continue answering homework questions, at least until I'm outta here....

Jack Peacock

[Fernando1]

I don't understand your answer, but I already managed to make my neural networks work, both with STM32Cube IA and with MATLAB coder and load it into an STM32F4, and Simulink Coder for TM4C123 and dsPIC. I complain because nobody brings anything, I'm not going to give my solutions either.

[Fernando1]

I use my own PCBs, I send them to be manufactured, and they come out much cheaper than buying development boards. I wanted to try to ask for help in this forum and the truth is that there is hostility.

[Tesla DeLorean]

>>...truth is that there is hostility.

Think of it as a cry for help. Do you understand how depressing it is to be surrounded by people who want/expect "help", but they never reciprocate in kind?

[HHarj.1]

I'm new here as well and trying to learn = making questions & while not having that much knowledge (yet) to contribute. I think this software attracts newbies as myself since it gives the impression of making the embedded programming easier. But certainly I will share if/when I find the solutions. That's what these forums are all about.

[Jack Peacock_2]

You're right about the HAL, it's there to compete with the likes of Microchip/Atmel. Ease of use, just generate the code. It's the proverbial royal road to embedded design, let the computer make all the decisions.

The reality is learning how to use a code generator is right at the bottom of the list of marketable skills in the embedded world (except for IC layout, but that's highly specialized). What's valuable is delivering a maintainable design (defined as 15-20 year life where programmers you will never meet have to figure out your little gems of elegant but comment-free code), understanding the cost/benefit trade off when choosing components, laying out a cost effective PCB (no, you can't build it all out of fine pitch BGAs, WLCSPs and 0201 passives), make the final product testable (error logs and statistics are marvelous debugging tools, especially for RMAs), the ability to write down what you've done, and being able to pitch your ideas to management in terms they understand (google 'return on investment'). Clever software frameworks don't enter into it. Especially since they will have disappeared toward the end of that 20 year lifecycle (still writing code in FORTH?).

If you really want to get some benefit out of the forum, learn to write in a clear and concise manner. Before asking, explain what you want to accomplish, what you've done, the steps you did for troubleshooting (please, please, please show the status registers with the error flags), and in what way the results don't match what you expect. Takes too much time? Sure, we all agree. That's why no one else answers the one line 'please post code' questions. Hostility in the forum is really nothing more than Garbage In, Garbage Out.

Embedded is not website programming. It's quite a bit more complicated, and it requires many skills not found in a Javascript shop. You need a background in electronics, communications (writing!!!), economics (can you explain present value as it relates to the inventory of those parts on your shiny new PCB) and mathematics (if you don't know what numerical analysis is don't ever use floating point in your code or work on a DSP), to go along with some idea of how to build and reuse commercial code that generates a profit for your company.

And finally, English not your first language? Just keep it simple, most everyone here tolerates the language mistakes. I cringe any time I have to use my extremely limited Spanish, rarely heard outside the neighborhood tortilliera at lunchtime. "Por favor, dos chimichangas al Pastor, para llevar."

Jack Peacock

[RMcCa]

Too many people ask extraordinarily vague questions. I am glad you figured what you are trying to do, but perhaps the lack of response to your question forced you to do it the way you should have in the first place - read & study and play with it until you understand. It's called learning.​

I have found this forum helpful, but i only ask very specific question​s.

[oeliks]

Well How many people did You help?

​

You are part of this forum.​

​

I hope You will find some help. But neural networks arent basic topics.

[GIkar]

When using STM32 uC you have to help your self. But sadly most documentation and ST expamble codes are written in SPL not HAL or LL.

[Jack Peacock_2]

Old code may use the SPL, but anything new is all HAL and virtually no easily understood examples. Just try figuring out the OTG or DMA2D by tracing through the generated spaghetti code. Worst of all are the ST sensors. Datasheets have virtually no information on setup or use, and app notes all refer to opaque "black box" HAL routines.

[gregstm]

Congratulations Fernando. You are solving your own problems and making your own hardware - that is the STM32 way. I have been visiting this forum on-and-off for almost 10 years, it has changed a lot. Originally it was people trying to guide ST to create better products, but now it seems like a deluge of questions. I can understand why everyone gets overwhelmed. Unfortunately solving problems often involves gritting your teeth, taking a deep breath and burrowing into the documentation. Thankfully the documentation is fairly thorough. As far as not wanting to share your solution, fair enough - if you are competing against fellow students/companies, why would you want to give your advantage away?

[JNord]

There are example of initializing networks and doing prediction in several of the example codes provided by ST. For example in the FP-SENSING-AI. I agree there could be more practical walkthroughs and API reference for particular parts of the AI library (and the HAL), but the information *is* available.