Hi Dave, it was a real pleasure listening to your talk, getting insights and and hear about your experience on SW Portability/Abstratction/... . I really appreciate you taking the time to share all this and giving us those really valuable tools and thoughts for our engineering tool-box.
There's on more thing you made me curious about and it would be great to hear your opinion/experience: During the the Q&A you made a very interesting statement about communications protocols - that THE critical part of the design is how you move the Data.
Do you have some more tipps for designing/developing a performant communication protocols? What to watch for? What are the trapps and pittfalls to avoid? Abstraction best practices?
Since I am currently working on designing a specific middleware, so to say a highlevel protocol, you hit a sweet spot with that comment :-)
I am really looking forward to hear some more of your ideas!
Thanks, Andreas

Excellent!

Thank you for your talk, Dave. An excellent discussion. I'd appreciate the slides for reference as well.

Abstracting the RTOS was the most interesting section, that is one area I didn't consider for chip shortages! Thanks for sharing your knowledge in that area.

Thank you Dave, for your presentation. Will you be publishing your slides here?
I've pitched a similar framework before -- before 'Supply Chain Issues' was a thing -- so your talk is resonating well with me. Thank you for your consideration.

Hi Nathan, I really liked the talk! Thank you very much!
One initiative achieving a level of abstraction for ARM is CMSIS - what is your experience with /take on CMSIS?
Andreas

Thanks for the presentation, very interesting.
At my company we are seeing more and more customers asking us to port their firmware to new microcontrollers. The difficulty of those migration projects highly depend on the abstraction you describe in your video.
Also, could you publish the slides ?

Very interesting talk!
I think pretty much everybody today is minimally aware of the risks associated with non-portable code and some basic strategies like a set of primary software design principles, and the use of language usage constraints like MISRA. Today, however, with the increasing shortage problems, these risks have become more probable than ever,. and developing without minimum portability in mind is pretty much suicidal. In addition, the rise of embedded software complexity and off-the-shelf software and development ecosystems provided by silicon vendors with a certain degree of lock-in provides a lot more of coupling surface increasing the effort of making it portable, making careful planning and designing more necessary than ever.
What I enjoyed most about the talk though is the ability to structure and summarize the main challenging aspects and tactics to overcome them with success that the talk is able to distill.

Well-said Dave. Very good guidelines to follow that could save many projects from all the different kinds of crises that could cause a need to change MCUs to meet demand.