Hello,
We have a custom board based on AM3352 that operates one of our embedded devices. The arago-tmp-external-arm-toolchain architecture develops an .swu image that is based on the Yocto project and uses bitbake to pull in the necessary layers to generate the build file (.swu). This file is then programmed to the custom board and allows the board/embedded device to operate. The application is a custom GUI that is developed using Qt 5.11.3, from which bitbake pulls in the necessary ".bb" and ".conf" files at run time to generate the bitbake image.
The issue we are experiencing is that once we update the custom splash screen image used for the application (within Qt), then generate a new .swu build image for the device and program it, upon boot up of the device (containing the new .swu image), the device displays the remnant/old splash screen for approximately 1-2 seconds then displays the new splash screen. This is on the embedded device/machine side. It seems that it has cached the previous splash screen.
What is odd is that when the application is ran in Qt to test the new splash screen, the new splash screen displays immediately and the remnant/old splash screen does not display at all, which is what we expect. The issue only arises on the device/machine side once the .swu image is generated to program the embedded device, and the device is booted up. Again, this seems to be related to a cache issue on the board side but I am not entirely sure.
Is there any where to check if the generated bitbake image is using a previously cached splash screen image? Is there anyway for bitbake to clear any cached splash screen images? Please comment/reply on any additional information that may be needed to further diagnose.
