Update WEC Image for TLS 1.2 Support

Well the time has come, I’ve been running WEC7 v1.4 for the longest time and it appears that I need to update the WEC software to gain the TLS 1.2 support in order to keep sending emails from my deployed systems. I’m currently using EASendMail for Compact Framework v3.5 to send outlook emails and it’s now giving me the following error.
“TLS 1.0 and 1.1 are not supported. Please upgrade/update your client to support TLS 1.2.”

It appears that I can’t simply update to the latest .dll provided by EASendMail and that I’ll actually have to update the underlying system…

Using the update tool to update the OS is something I havent’ tried yet, and I fear that I’ll break something in the process. The issue is that I’ve got systems deployed using the Colibri iMX6DL on a custom carrier board, so running a recovery tool will NOT be an easy task.

If I recall, whenever I would create a new system, I could use the Toradex easy installer and had the image with the registry all on one flash drive, so loading the OS onto a new board was easy and it’d come up with all my registry settings necessary for FTP, etc. and then I’d use the ISAPI to reassign password credentials because of each boards encryption (i think).

  1. Does anybody have an SMTP client they use for emails that hopefully won’t require this OS update? I really don’t know much regarding the OS support for TLS v1.2 versus having a different email library/dll to handle the emails.

  2. Is there a way for me to retain the registry settings and perhaps file structure of the deployed systems and simply update the OS underneath it all.

  3. If I can use the backup.i6r registry when updating the OS, are there any new registry values that are required that may be skipped on being written into the new registry?

  4. Can this all be done remotely? My systems have remote FTP access, Telnet access, and I’m running both the CE remote display and VNC for remote desktop redundancy. I’m concerned that if I do update a system and it doesn’t support adding files to the filesystem, then I’ll lose the CE Remote Display capability when it boots and if something goes wrong, I won’t be able to fix the issue.

Sorry for the long post, but I need suggestions and/or a more clear path for how to properly get my systems working again.



You can update you system using an UpdateTool. In this case you don’t need to put your device in a recovery mode. However this tool is using filesystem so you need ether USB stick/ SF card or have an access to SMB server.

New BSP has some new and/or modified registry keys so restoring registry from older BSP may create a problems. I’d recommend to export your original registry and registry from the new BSP using RegEdit. And then manually merge them using your favorite diff tool.