Build Errors for isp-imx-4.2.2.11.0

[Cbrobson]

Hello,

I am currently trying to port a custom MIPI image sensor for use with the IMX8MPEVK development board. Thanks primarily to this community thread, I am aware that there is currently a lack of specific low-level documentation on the subject, but I believe I generally understand what must be done.

I am attempting to build isp-imx-4.2.2.11.0.bin so that I can start working with the reference files for the OV2775 and adapting them for our sensor, but I'm running into errors that seem to be involved with my meta-toolchain. I have attached a log with the full output, and below you can see the point where it fails.

Scanning dependencies of target viv_fpga_driver_create_dir
[ 19%] Create dir for viv_fpga_driver
[ 19%] Built target viv_fpga_driver_create_dir
Scanning dependencies of target vvdisplay_shared
[ 19%] Building CXX object obj/display/CMakeFiles/vvdisplay_shared.dir/DrmDisplay.cpp.o
/home/developer/Documents/Camera-Porting-2/isp-imx-4.2.2.11.0/appshell/display/DrmDisplay.cpp:37:11: fatal error: g2dExt.h: No such file or directory
# include <g2dExt.h>
^~~~~~~~~~
compilation terminated.
make[2]: *** [obj/display/CMakeFiles/vvdisplay_shared.dir/build.make:63: obj/display/CMakeFiles/vvdisplay_shared.dir/DrmDisplay.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:2575: obj/display/CMakeFiles/vvdisplay_shared.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 19%] Linking CXX shared library ../../../../generated/debug/lib/libjsoncpp.so
[ 19%] Built target jsoncpp_lib
make: *** [Makefile:141: all] Error 2

After that point, the build does generate a long list of files, but based on the error above I assume that these generated files will be either incorrect or incomplete.

The header file at issue is related to basic GPU operation, which indicates to me an issue with the meta-toolchain. I followed the steps in Section 3.1.1 of the Yocto Project Application Developer's Guide and ran the ADT installer in an attempt to re-build my toolchain, but to no effect. I am currently looking into Section 3.3.2 of that same guide, thinking I might be pointing to the wrong sysroot.

The image for this dev board was built by a former colleague, and I have been trying to avoid going the route of a full re-build, but that might be my next step.

I would very much appreciate any direction in troubleshooting this issue. If anything is unclear above, or if I can provide any additional detail, please let me know!

Thank you,

Cody Robson

[khang_letruong · Accepted solution]

Hi @Cbrobson ,

Which image did you bitbake for Yocto SDK ? Mine is below :

$ bitbake imx-image-multimedia -c populate_sdk
or
$ bitbake imx-image-full -c populate_sdk

Then I install the Yocto SDK into my host system  :

$ ./tmp/deploy/sdk/fsl-imx-wayland-glibc-x86_64-imx-image-full-aarch64-imx8mpevk-toolchain-5.4-zeus.sh
NXP i.MX Release Distro SDK installer version 5.4-zeus
======================================================
Enter target directory for SDK (default: /opt/fsl-imx-wayland/5.4-zeus): 
/opt/Yocto/5.4-zeus

Once done, execute following command in the working shell (or append it into ~/.bashrc) :

. /opt/Yocto/5.4-zeus/environment-setup-aarch64-poky-linux

And I can build the isp-imx  with ./build-all-isp.sh (i..e ./build-all-isp.sh Release partial)

Best regards,
K.

[Cbrobson]

Hello @khang_letruong ,

Thank you for your response! Indeed, I just had to reinstall the SDK and the build completed successfully. I can now begin working on generating my modified .xml and.drv files for the new sensor.

Thanks again, and I hope I can return the favour in the future as I learn more about this process.

Regards,

Cody