Sujet : Re: 32 bits time_t and Y2038 issue
De : pozzugno (at) *nospam* gmail.com (pozz)
Groupes : comp.arch.embeddedDate : 12. Mar 2025, 08:44:40
Autres entêtes
Organisation : A noiseless patient Spider
Message-ID : <vqre18$2g8c8$1@dont-email.me>
References : 1 2
User-Agent : Mozilla Thunderbird
Il 11/03/2025 17:32, David Brown ha scritto:
[...]
For anything other than a quick demo, my preferred setup is using makefiles for the build along with an ARM gcc toolchain. That way I can always build my software, from any system, and archive the toolchain.
[...]
Regading this point, it's what I want to do in new projects. What I don't know is...
Why many silicon vendors provide a *custom* arm gcc toolchain? Are those customizations important to build firmware for their MCUs? If not, why they invest money to make changes in a toolchain? It isn't a simple job.
Another point is visual debugging. I don't mean text editor with syntax hilighting, code completion, project management and so on. There are many tools around for this.
I used to have a button in the IDE to launch a debugging session. The generation of a good debugging session configuration is simplified in IDE if you use main debuggin probe (for example, J-Link).
How do you debug your projects without a full-features and ready-to-use IDE from the silicon vendor?