Colibri T20 256MB V1.2B Flash Image doesn't work

Hello
We have been using Colibri T20 256MB V1.2A and due to end of life, we have got some Colibri T20 256MB V1.2B
We have used the Colibri Evaluation board, Update tool on Windows and our standard flash image to flash them, but after reboot, it seems that nothing has happened.
It looks like it hasn’t written to and Flashdisk folder disappears.
I have tried over 10 and all are like this.
Same image works perfectly on version A.

Please let me know what I need to do?

Thanks

Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!

Did you like my answer?

:+1: :-1:


Hello,

Thank you for reaching out with your issue regarding the Colibri T20 256MB V1.2B modules. It seems like the flash image that works on the V1.2A modules is not functioning as expected on the V1.2B version. Here are some steps you can take to troubleshoot and resolve this problem:

  1. Verify Image Compatibility: Ensure that the image you are using is compatible with the V1.2B hardware. Even though the hardware revisions are similar, there might be subtle differences requiring a specific image version or additional configuration.

  2. Check the Flashing Process: Double-check that the flashing process is executed correctly. Confirm that the update tool is compatible with the V1.2B module and that all necessary steps are followed precisely.

  3. Inspect Boot Configuration: The boot configuration might need adjustments when moving between hardware revisions. Verify that the bootloader settings are correct and compatible with the V1.2B module.

  4. Review Known Issues: Look for any product change notifications or known issues related to the V1.2B version. There might be documented issues affecting the flashing process or the module’s behavior.

  5. Test with a Basic Image: Try flashing a basic, unmodified image provided by Toradex to see if the issue persists. This can help determine if the problem is with the image itself or the flashing process.

By following these steps, you should be able to identify the root cause of the issue and take appropriate action to ensure the image is correctly flashed onto the V1.2B modules.

If you have any further questions, feel free to ask.

Best regards,
Toradex AI Assistant

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

Problem while flashing the image 2.5 Beta 3 in colibri t20.

How can I make sure that Image is compatible?
What should be the Boot configuration?
Where can I get a basic image for this version?

Could you please specify the version of the Update tool you are using, the BSP version of your ‘standard flash image,’ and provide details on how exactly you are performing the flashing process?

Please also check this PCN

Hello Alex

How can I check the BSP version of our flash image?
I use the evaluation board, when powered, select Update tool fro Start menu.
Select update.
Meanwhile I have the flash image on a USB stick plugged in and select the flash image file from there.
Then it restarts.
Our flash image was created on version 1.2A.

Best regards
Shiva

The BSP v1.2 is 11 years old and no longer supported. The mentioned PCN clearly indicates that the minimum software requirement is BSP 2.2. Therefore, we recommend rebuilding your flash image based on the latest BSP release (v2.5)

Hello,
I downloaded the BSP 2.2 for WinCE7.
How can I update my existing Colibri T20 V1.2A with this BSP to then the flash image and program new Colibri T20 V1.2B with this image?
Thanks

Hello
I haven’t been able to find any documentation on the website.
Could you please answer these questions, so we can use the last batch we bought from you.

  1. How should I update the BSP on existing Colibri T20 V1.2 A to BSP 2.5?
  2. Would the image built on BSP v 2.5 then work on Colibri T20 V1.2 B?
    Thanks
    @alex.tx

You can download the OS image from here and then update your module using the NVFlash tool. This should work on the Colibri T20 V1.2B. Afterward, you will need to reinstall your custom software and reapply registry modifications (if required). Once completed, you can use the Update Tool to create a backup of your current setup and then use this backup to program additional modules.

Hi @alex.tx
Our custom software flash image is made on Colibri T20 V1.2A, that has older BSP version.
Do I update the Colibri T20 V1.2A with the OS image V2.4 (we have WinCE7) ? and then put our program on and then the flash image created would work on Colibri T20 V1.2B?
Thanks

Yes, it should work. If not, you can achieve the same using a V1.2B module: flash the OS image version 2.4 to it, add your application, apply any required registry customizations, and then use the Update Tool to create a backup of this ‘golden’ image. This image can then be used to program new Colibri T20 V1.2B modules.

@alex.tx The NVflash doesn’t run on WinCE and when I try running on Windows nothing happens.
How do I use it to update the OS image?
There is no guide on the website.
Thanks

@alex.tx Thanks for the quick response.
Just to confirm it can not be done through the Update Tool?

Most likely not, though I haven’t tested it. There is a significant gap between BSP v1.2 and v2.5. You should use the latest version of the Update Tool and we cannot guarantee it will work flawlessly on your old BSP . It is better to start from scratch by flashing the latest BSP using the recovery mechanism.

How can I check the BSP version after I put the new OS image on the Colibri?
Thanks

You can either check the boot log from the debug UART or start the Update Tool on the target system and click the ‘Version Info’ button

Hello @alex.tx
The application file I have doesn’t run on the new OS image.
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 OS image version 2.4 ?
If yes, what should be the new solution platform?
Thanks

Hello @shivaOD !

Since this is a different issue than the one discussed in the previous ticket, could you please open a new post for it? This will help us track your request properly. When doing so, please include as much context as possible about your setup and the changes you’ve made.

Thank you!