3 ms·
>Tools for C are powerful, mature, and available on near every platform. If only this was true for embedded platforms! I have no tools at my disposal aside fro
by com2kid 13y ago
>Tools for C are powerful, mature, and available on near every platform.
If only this was true for embedded platforms! I have no tools at my disposal aside from a vendor supplied debugger. No pre-existing test infrastructure exists, what we have we have had to build up ourselves.
One of C's last remaining strongholds is in embedded, and the tooling in this world is atrocious! (Though some of the instruction and performance profiling tools are beyond amazing!)
Rigorous coding standards and a heavy reliance upon code reviews keep a code base clean and sane, sort of like on any other project written in any other language!
- silentbicycle 13y agoEmbedded test software is developing. Look at http://throwtheswitch.org/ http://throwtheswitch.org/ and my (more minimal) "greatest": http://github.com/silentbicycle/greatest http://github.com/silentbicycle/greatest
- Nursie 13y agoLast remaining strongholds? C is everywhere. I'm in a similar situation with embedded stuff at the moment. We're basically stuck with debug-by-printf over a serial port, far from ideal! I have worked on other embedded projects that were better, for instance you can make a gdb server that operates over serial or tcp/ip and allows you to use gdb (or even graphical debuggers like ddd) on a host machine to step through code as it runs on your device. This does rely on there being resources available to do this though I guess...