Wow, how do you even test bit flips from the procurer side (Airbus in this case)? I work in industrial manufacturing (although not as mission-critical as a pla

Wow, how do you even test bit flips from the procurer side (Airbus in this case)? I work in industrial manufacturing (although not as mission-critical as a plane) and suppliers have surprisingly amount of problems in their parts and we can't (and shouldn't) need to stress-test every single part we buy from 3rd parties. Just last month we found out one of the bluetooth chips we use is giving kernel panics seemingly randomly once a week. It can only be fixed with a power-cycle. Supplier just shrugged and asked us to run some diagnostics software, we gave up on using bluetooth for this product instead (we had a physical display as an extra addon, but now it is mandatory). Note this is a million-dollar product and we were lucky to have caught this problem before release. We actually accounted for a similar problem for our network communication messages by adding CRC to our messages. https://en.wikipedia.org/wiki/Cyclic_redundancy_check https://en.wikipedia.org/wiki/Cyclic_redundancy_check But bit flips inside a microcontroller or memory is beyond our capabilities to detect or simulate. Note I am not one of the embedded engineers they might have some safeguards for this on top of trusting the hardware error-correction that I don't know about.