I have some nice embedded programming stories for ya:
Two old colleagues of mine spent about one week on a particular issue:
They were working on a SIP stack (for audio connections/sessions), when suddenly it stopped working completely. After one week it turned out that the PBX (kind of phone/SIP router) had blacklisted their device for too many failed calls)...
I have spent about 1,5 months on another issue with a driver for flash memory. TLDR: some bit in a settings register was not set/reset by our driver, so based on whether the device had used an older driver before it would work perfectly OR shift everything 1 byte.
The unfortunate part of embedded programming (at least back then) was that:
it took around 2 minutes to compile and flash ANY CHANGE that you had.
many errors show up when the linker gets involved, which is at 99% of the compilation process (so after 1 minute and 45 seconds, something like that)
especially in the beginning, none of us knew how to debug/profile embedded software.
Later on we added profilers and proper debugging setups (and a hardfault handler that printed stacktraces. GAMECHANGER!)
Good old arm-none-eabi-gcc days :P
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I have some nice embedded programming stories for ya:
Two old colleagues of mine spent about one week on a particular issue:
They were working on a SIP stack (for audio connections/sessions), when suddenly it stopped working completely. After one week it turned out that the PBX (kind of phone/SIP router) had blacklisted their device for too many failed calls)...
I have spent about 1,5 months on another issue with a driver for flash memory. TLDR: some bit in a settings register was not set/reset by our driver, so based on whether the device had used an older driver before it would work perfectly OR shift everything 1 byte.
The unfortunate part of embedded programming (at least back then) was that:
Later on we added profilers and proper debugging setups (and a hardfault handler that printed stacktraces. GAMECHANGER!)
Good old arm-none-eabi-gcc days :P