4 ms·
I wrote firmware (~20kLocs) for a power (electrical) supply that's part of one such power train. This kind of development is very demanding, because you can't
by pbo 13y ago
I wrote firmware (~20kLocs) for a power (electrical) supply that's part of one such power train.
This kind of development is very demanding, because you can't afford to leave any bugs in your program but at the same time you're always shipping late because of tight schedules and often blurry specifications.
On top of that hardware and software development cycles are concurrent, so no target hardware available when you're writing your code.
In these conditions the only way I found to have something that works is to keep it very simple:
1. Simple algorithms
2. Simple data structures
3. Few abstractions
4. No dynamic memory allocations
Also, no compiler optimizations.
- T-zex 13y agoWow! Have you developed the software for the ECU?
- pbo 13y agoActually I distribute power from the battery to other subsystems, so it's rather far from the ECU.
- kayoone 13y agoas a huge F1 fan and software hacker id love to hear more, but i guess its all under NDA right ? :/
- zdrummond 13y agoCan you do an AMA? I would love to hear more!
- pbo 13y agoEven though the work environment is peculiar, the technical contents itself is far from exceptionnal, really. If you'd like to read more about this kind of systems, this document could be a starting point: http://www.ti.com/lit/ml/slup232/slup232.pdf http://www.ti.com/lit/ml/slup232/slup232.pdf It sums up pretty well the stakes and technical challenges with digital power supplies.
- pavanred 13y agoI love F1 and am really interested to know more. But, as kayoone mentioned there probably would be a NDA. If you have a blog, you should put your url out here.