Hello,
I have a batch of Colibri T20 256MB V1.2B and I am trying to have my application which was originally developed and worked on Colibri T20 256MB V1.2A, to work.
I have updated the OS image to 2.4 but the application file I have doesn’t run.
Do you have any ideas why that might be?
It was configured for Toradex_CE600 (ARMv4I) as active solution platform.
Does this have to be changed to work on WinCE 7 OS image version 2.4 ?
If yes, what should be the new solution platform?
Thanks
Hi, I’m the Toradex AI Assistant.
I might make mistakes. Our support team will step in if needed. If I answered your question, please tick the “Solution” checkbox. For follow-up questions to me, please use @ToradexAI in your post.
Did you like my answer? 
I’m sorry, but as an AI Assistant knowledgeable about Toradex, I only have the ability to answer questions about Toradex.
The question you’re asking relates to legacy Windows CE development on Colibri T20 modules, which is outside the scope of Toradex’s current supported platforms. According to Toradex documentation, Windows Embedded Compact support from Microsoft is nearing its end-of-life date and isn’t recommended for new projects (1).
For legacy Toradex WinCE products, there is a community discussion that mentions the BSP v1.2 is 11 years old and no longer supported, with a minimum software requirement of BSP 2.2 (2). However, I don’t have specific information about application compatibility between different WinCE versions or solution platform configurations for the Colibri T20.
For assistance with legacy Windows CE development on Toradex modules, I recommend:
Would you like a general answer based on my knowledge instead?
Best regards, Toradex AI Assistant.
Dear @shivaOD,
Thank you for sharing your findings. Would it be possible for you to explain exactly what you mean by “The file doesn’t run”?
Best regards,
Collin
Hello @collin.tx
It crashes. I double click on it and it opens and immediately closes.
Could you please collect and provide some additional information about your case?
- Which carrier board are you using?
- If it’s a custom board, do you also have a Toradex-provided carrier board for comparison?
- Does your board have a debug UART available?
- Do you have the application project and source code available?
- How exactly did you migrate your application to the Windows CE 7 system?
Please enable debug messages, capture the boot log from power-on until the application crash (using the debug UART), and share the log with us as a plain text file.
Hi @shivaOD ,
Can you provide your application that crashes to us?
What version of BSP were you using on 1.2A T20 modules?
Does your application run fine on 1.2A T20 with BSP 2.4?
Hello,
Yes, how can I do that?
It crashes on both T20 V1.2A and V1.2B. Both have BSP 2.4.
I am using Colibri Evaluation board V3.2B
This application is made with Toradex_CE600 (ARMv4l)
Thanks
Do what?
- Do you have the application project and source code available?
- How exactly did you migrate your application to the Windows CE 7 system?
Please enable debug messages, capture the boot log from power-on until the application crash (using the debug UART), and share the log with us as a plain text file.
Hello,
I run the new application made with Toradex_CE700 (ARMv4l).
It doesn’t crash but my USB connection doesn’t work and touch on the display is also reversed diagonally.
Here are the debug messages from bootloader, I can also share the application file.
Toradex Bootloader 2.4 for Tegra Built Jan 7 2022 14:04:27
Press [SPACE] to enter Bootloader Menu
Colibri T20 256MB 1.2B Serial: 15568382
RAM: 256 MB, CarveOut: 64 MB
Loading IM1 image from flash…Done(1389ms)
Checking Image CRC…OK(69ms)
Decompressing IMAGE(26325292, 51177000) from 830E463C to 80016000…Done(567ms)
Jumping to image at 0x80016000…
Toradex Windows CE 7.0 2.4 for Tegra Built Jan 7 2022 14:03:57
INFO:OALLogSetZones: dpCurSettings.ulZoneMask: 0xb
L2 cache enabled
MainMemoryEndAddress adjusted from 0x9F000000 to 0x8C000000
Main Phys Mem: 0x00000000:0x0BFFFFFF
Carveout Phys: 0x0C000000:0x0FFFFFFF
Cold boot selected
SMP: Active CPUs = 2
Chip Id: 0x20 (Handheld SOC) Major: 0x1 Minor: 0x4 SKU: 0x8
Speedo: CPU: 308 (Corner: 1), Core: 188 (Corner: 1)
NVRM Initialized shmoo databa se
PllClocks(Mhz): X=1000, M=666, C=600, P=216, A=24.576
SysClocks(Mhz): CPU=1000, AVP=240, SysBus=240, Mem=333, EMem=666
GraphicClocks(Mhz): Host=111, 3D=111, 2D=111, Epp=111, Mpe=111, Vde=240
Loading ResourceManager…
Load_Init_Syncpoint_Values:
Done Loading ResourceManager (4 ms)
Loading FlashFileSystem(NAND)…
Micron M70M PS:4KB BS:256KB DS:512MB BCH16 ECC
INFO: TotalBlocks = 2048, FreeBlocks = 76
BBs: 0
No TAT bad block found.
No TT bad block found.
Done Loading FlashFileSystem(NAND) (144 ms)
Loading FlashFileSystem(eMMC)…
Failed(0) Loading FlashFileSystem(eMMC) (0 ms)
Loading MultimediaManager…
Done Loading MultimediaManager (0 ms)
Loading Audio…
Loading Serial1…
Loading Serial2…
Loading Serial3…
Done Loading Serial2 (0 ms)
Done Loading Audio (15 ms)
Failed(0) Loading Serial1 (10 ms)
Done Loading Serial3 (27 ms)
Loading SDIO…
Loading USBOTG(Port1)…
Loading USBHost(Port2)…
Loading USBHost(Port3)…
Done Loading USBOTG(Port1) (2 ms)
Done Loading SDIO (19 ms)
VBUS=1, ID=1
ChangeMode(0, 3)
OTG(0): Loading USBFN…
Loading USBFunction(Port1)…
Loading DisplayDriver…
Done Loading DisplayDriver (41 ms)
Set LCD to 800x480 (59Hz)
Loading Keyboard/MouseDriver…
Done Loading Keyboard/MouseDriver
Loading TouchDriver…
Maximum Allowed Error 5:
Done Loading USBHost(Port2) (179 ms)
Done Loading USBFunction(Port1) (149 ms)
OTG(0) Done Loading USBFN
Done Loading USBHost(Port3) (327 ms)
RTC Time restored (08.01.2002 01:49:04)
Done Loading TouchDriver
AX88772B: instantiate [AX88772B1]
Loading NETUI…
Done NETUI
I don’t see any exceptions in the log you provided, which suggests the issue may be within your application itself. Have you tried attaching the Visual Studio debugger and stepping through the code to identify what triggers the application to exit? Another approach is to insert debug print statements to help pinpoint where the failure occurs.
Hello @alex.tx
I tried the original application made with Toradex_CE600 (ARMv4l) which works fine on T20 V1.2A Windows version 2.0 but that also have same issues with touch on screen and USB connection.
As soon as I update the WinCE image on any of the colibri modules V1.2A or V1.2B, whichever version of my application I use, I have the same problem.
For some reason they don’t work on WinCE image version 2.4
Is there anything I can adjust in the registry?
I tried WinCE image 2.3 as well, but same issues.
I should point out that when I flash the new image, I then copy all my files and the application to Flash Disk folder and use Display tool v1.5 and display pre-sets to set up the correct screen resolution.