We recently introduced a new custom splashscreen image in our Wince7 T20 devices.
During boot, the splashscreen flickers on some occasions (you can see an example here).
They were supposed to be part of the launch of our new model year software version “MY2023” (which is stated in the splashscreen) and now we had to revert back to the old splashscreen until we solve this.
We already got a copy of your splash screen bmz converted application from the past and we applied it on the set of new bmp images prepared to be compatible with the converter (8bpp, etc).
We have now covered almost all the testing and comparisons on the devices and we are left with two options:
Either the source bmp images or the bmz converter for T20 are at fault, which is what I want to ask you (but it would be a bit strange as the same image does not give the issue on all the devices);
Or some other changes on our custom board we are investigating might be at fault (which again would be strange as the old splashscreen images don’t have this issue, and AFAIK they never had);
All the tests of updating the splash screen device have been performed with the toradex UpdateTool, either the one available on the device (6.0.14) or the copy we hold on our installation USB sticks (6.0.10), without notable differences.
Here I attached most of the files involved:
A short video of the issue
The sections extracted from a device presenting the issue, by using UpdateTool 6.0.14:
ss.res: 0xFC (Reserved Flags) (<- this is 0x0 in another device with same issue because i read the value from the ConfigBlockEditor utility instead of the bootloader)
ss.bsTeg: 0xFFFFFFFF (LCD Buffer Strength Tegra)
set hw
hw.vermaj: 1 (Major Version)
hw.vermin: 2 (Minor Version)
hw.variant: 0 (Variant Numer (stuffing options))
hw.prodid: 20 (Product ID)
set mac
mac.tid: 0x142D (Toradex MAC range ID)
mac.cid: 14763239 (Colibri MAC range ID)
I’ve converted your BMP file into BMZ and tested it with BSP v2.4. Everything works as expected with no artefacts. Please upgrade your BSP to the latest one.
Thank you Alex, I have confirmed that the BMZ you provided shows the same glitch in the same situations as the one we generated on our side.
I don’t think we are going to update our BSP to solve this. It won’t be feasible at least not very soon.
We still have other leads pointing us to the hardware, we will follow them for the moment.
You can do it using eBoot Set ss.pclk command followed by by save ss commands (check this article). Then you can backup settings using the Update tool in command mode and use saved backup for production programming,
