How to build a system image?
-
I would like to build a custom system image for VOXL2, as the on-system approach using apt-get is good for testing/dev but can't be used for deployment or even reproducible dev tests.
While the Kernel Build Guide works great to build the kernel, I was not able to build the system image.
I tried modifying the qrb5165-build .sh script to do a full "bitbake qti-ubuntu-robotics-image" (not only the kernel task).
But this resulted in a lot of errors. So I wonder if this is the right approach? -
I just saw in https://forum.modalai.com/topic/1695/could-we-enable-voxl-2-to-support-hires-camera-ov64b-by-install-driver-without-system-image-re-generated that a system image can only be created by the ModalAI team.
Can you elaborate a bit on why this is? And what kind of options there are to get around the problem?
-
ModalAI team: any update on this?
If not, could you clarify it the VOXL2 platform is more intended as a prototype only thing and you expect users to move to custom RB5 solutions with custom hardware and tool-chains later? Obviously if no custom build is possible this severely restricts the platform capabilities for potential products.
-
@elfowl You would need to have a license from Qualcomm to get access to all of their proprietary code in order to build your own system image.
-
@Eric-Katzfey we got that now. Do you provide information on how to setup the build?
-
@elfowl We don't expect our customers to build the system image for VOXL 2 and don't have a way to support it generally. What feature is missing that you need?
-
I understand that this might work for a development system. But it basically makes VOXL unusable for commercial / production use where you need to have a reliable way to build an update a system.
Just adding a software package/version not available on the current system is a nightmare (especially regarding dependencies) if you can't use a proper build systems (e.g. yocto/bitbake). -
@elfowl We treat package management and the base system image separately as the application level packages are updated much more frequently. Our enterprise customers follow this paradigm by modifying the SDK's offline installer to incorporate their packages
-