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
