Porting to T20 1.2B - Fail to install OS image 2.4 on a T20 1.2A

Technical Support
, ,
1

Hi there,
We are preparing an OS image to be used in production to prepare new T20 1.2B modules.
I did it by installing Toradex WEC7 OS Image 2.4 on a T20 1.2B sample and adding our customizations to it.

Our application, which will have to live on both the device pool that is on the market (featuring T20 1.2A with OS image 2.1 inside) and the devices that will get produced anew (soon featuring T20 1.2B) currently includes toradex libraries revision 4281 (released on 2018-01-12).

My question is: do we really have to update the Toradex libraries in our application? are there going to be issues by running it with the mentioned revision on a device with OS image 2.4?

I’m asking because we do have tried to update the Toradex libraries in our application and rebuild it. We tested two scenarios:

  • T20 1.2B with OS image 2.4, no major issues to report (yet), so far so good (these would be the new device to produce);
  • T20 1.2A with OS image 2.1 (the devices on the market already), we detected an issue: when the user tries to change date or time from our application UI (which calls windows APIs GetLocalTime and SetLocalTime), the date never gets preserved after a reboot, only the time. If I try to change the date from the WEC “date/time properties” panel instead, it works properly;

Therefore I wanted to try to update the OS image to 2.4 for the T20 1.2A as well, to see if the issue is still present (and if there isn’t any other issue), but I have saved a backup of the OS image 2.4 from the T20 1.2B by pressing “BackupAll”, to update the T20 1.2A with it and after updating the new image on it the module does not boot anymore.
By booting the T20 1.2A on a colibri evaluation board I can see the following boot messages through the COM port:

SplashScreen too big
Toradex Bootloader 2.4 for Tegra Built Jan 7 2022 14:04:27

Press [SPACE] to enter Bootloader Menu

Colibri T20 256MB 1.2A Serial: 3008354
RAM: 256 MB, CarveOut: 64 MB

Prefetch Abort Exeption (IFAR=0x00000000, IFSR=0x00000005)
R0 = 00000000 R1 = 8BCCD640 R2 = 8BEC1D00 R3 = 0000000D
R4 = FFFFFFFF R5 = FFFFFFFF R6 = FFFFFFFF R7 = FFFFFFFF
R8 = FFFFFFFF R9 = FFFFFFFF R10= FFFFFFFF R11= FFFFFFFF
R12= 0000040C SP = FFFFFFFF LR = 8BD31F2C PC = 00000000
Stack Dump:

Data Abort Exeption (DFAR=0x0000000B, DFSR=0x00000005)
R0 = 0000000A R1 = 8BEDBA34 R2 = B0306000 R3 = 00000000
R4 = 8BCB87B4 R5 = FFFFFFFF R6 = 00000000 R7 = FFFFFFFF
R8 = FFFFFFFF R9 = FFFFFFFF R10= FFFFFFFF R11= FFFFFFFF
R12= 00000000 SP = 8BCB8764 LR = 8BCE8908 PC = 8BCE8904
Stack Dump:
0000 0000000A 8BEDBA34 B0306000 00000000
0010 8BCB87B4 FFFFFFFF 00000000 FFFFFFFF
0020 FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFF
0030 00000000 8BCE8908 00000000 B00A1188
0040 8BD31F2C FFFFFFFF FFFFFFFF 8BD31A94
0050 00000001 00000000 00000005 FFFFFFFF
0060 8BD31F2C 00000000 8BCCD640 8BEC1D00
0070 0000000D FFFFFFFF FFFFFFFF FFFFFFFF

Yes, our customizations includes installing a splash screen image we had prepared already, but please note that this image works correctly when using a customized OS image 2.4 on T20 1.2B, or our old customized OS image 2.1 on a T20 1.2A, so the splashscreen itself should not be the issue.

we tried only the latest available toradex libraries so far, I don’t know if there is an intermediate version of them between the one we use and the latest that could work without the date issue.

Please advise.
Thank you

Colibri T20 256MB 1.2A/B
Custom board
WEC7 BSP 2.1/2.4

2

Hi, I’m the Toradex AI Assistant. I’m in early beta, and I would appreciate your feedback.
The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:

Hello,

It appears you are encountering a complex issue involving the Toradex Colibri T20 modules, specifically when updating from WEC7 OS Image 2.1 to 2.4 and dealing with compatibility of Toradex libraries across different hardware revisions. While your question involves WEC7, which is outside the primary focus of my expertise in Embedded Linux, I can still offer some general guidance that might be applicable to your situation.

  1. Toradex Libraries Update: Updating the Toradex libraries in your application is generally recommended to ensure compatibility with the latest OS images and to take advantage of any improvements or bug fixes. However, it’s crucial to test thoroughly in your environment, as you have done, to identify any potential issues that might arise from the update.

  2. Issues with Date and Time Settings: The problem with preserving date settings across reboots could be related to several factors, including the OS image version, library versions, or even hardware-specific behaviors. Given that the issue does not occur when adjusting settings via the WEC “date/time properties” panel, it suggests that the problem might be related to how the APIs are called or handled in your application rather than a fundamental issue with the OS image or libraries.

  3. Splash Screen and Boot Failure: The boot failure and error messages you’re encountering after updating the OS image on a T20 1.2A module could be related to compatibility issues between the bootloader version and the OS image or the specific customizations included in your OS image. The “SplashScreen too big” message suggests that there might be a resource allocation issue, possibly related to differences in memory layout or available memory between the 1.2A and 1.2B hardware revisions.

  4. Troubleshooting Steps:

    • Ensure that the bootloader version is compatible with the OS image version you are trying to install. Sometimes, updating the bootloader is necessary when moving to a significantly different OS image version.
    • Review the customization process for the OS image, especially regarding the splash screen and any other resources that might have specific size or format requirements. It’s possible that what works on one hardware revision might not work seamlessly on another due to subtle differences in hardware or firmware.
    • Consider testing with an intermediate version of the Toradex libraries, if available, to identify a version that does not exhibit the date issue. This could help narrow down the cause and determine whether it’s related to a specific change in the libraries.

Given the specific nature of your issue

Please, also check if these links can help you solve your problem:

Txx Recovery Mode | Toradex Developer Center.

3

Hi @EnricoPompeiani

Please ensure that you are using the latest (and the same) version of the Update tool for both backup and restore. If using the same version does not fix your issue, please enable debug messages over UART, collect the logs, and share them here as text

4

Hi @EnricoPompeiani ,

Have you been able to resolve the issue? If not, may we assist you further?

5

Hi Alex,
Yes, your answer is the solution, I’m sorry I forgot to flag it.
Thank you.

6

We are glad to hear that your problem has been resolved. Thank you for choosing and using our products.