In the "Strings" window we could find this "C++ library exception" which really looks like the code is written in C++
Find out the toolchain the firmware was made
Find out the toolchain the firmware was made
For decades, nobody is writing firmware in pure Assembler, they all use some higher-language for programming. C (or C++) is one of the most used for writing firmware. And every higher language has it's own bunch of libraries. As the firmware is stored as a monolithic image, the library functions used are also compiled into the resulting image. That means that if we could find out what the developers have used to write the IPC code, we can try to get our hands on the toolchain and maybe identify parts of the functions/subroutines as library functions. They are not so interesting for us to examine, but it would be good to distinguish between what is firmware-code and what libs.
In the "Strings" window we could find this "C++ library exception" which really looks like the code is written in C++
In the "Strings" window we could find this "C++ library exception" which really looks like the code is written in C++