Let me try to rephrase what you are saying to make sure I understand correctly. You are saying we should flash the cruise control onto the CORE2 using VSCode, like stated in the tutorial, because it is not possible to access the IMU data otherwise unless we change the serial bridge node so that the wheel encoder data can also be accessed by the Tinkerboard, since the bridge does not seem to do this at the moment.
That is correct.
If this is correct, then do we need to flash every node that uses the hFramework library onto the CORE2?
Yes, it need to be flashed onto CORE2, but there can be only one node running on CORE2 at the same time.
And is it then possible to launch these nodes together with our other nodes on the Tinkerboard with a single launch file?
Node on CORE2 is running since it is powered on and will be running until it is powered off. It can be restarted by reset button or flashing new firmware.
Node on CORE2 starts to publish/subscribe as soon as serial brigde is started.
Effectively, starting serial bridge equals to starting node on CORE2, thus you can include serial bridge in your launch file to start it with other nodes on TinkerBoard.
USB driver installation is required only on Windows. For Linux version, default USB driver is enough for flashing process.