There isn’t really anything that needs to be “fixed” and it’s largely a non-existent issue in the professional software engineering world.
In the case of VESC-Tool, my understanding is that the author does not wish to publish the codebase under a different license, therefor users depending on his codebase are beholden to the limitations of the original license.
An author can choose to publish their code under whatever license they choose, so the fix is to simply publish your code using a different license that does not have conflicts with your target publishing platform. In fact, this is common practice as it then allows an author to license their software differently for different markets/applications/clients/demographics, often charging for different license usage.
The one under the silicon is an uart port (that can’t be easily used for anything else than the unity ble module…workaround here : Unity internal UART wiring). As far as i can tell the can port is kind of standard.
