Teensy 4.x w/1062 coming out in Encrypted version

[Defragster]

Currently in Beta - only Teensy.exe Loader knows the process and steps for parsing an encrypted .eHex file and determining when it is required for upload and then programming it into a 1062 Teensy.

First step would be having TyComm 'delegate' uploading as a .hex file will not work when locked and an .eHex is required.

Currently using TyComm for SerMon and doing 'Ctrl+R' verify builds then with Teensy.exe active I hit 'gui Bootloader' to drop the USB connection and put Teensy in Bootloader which inspires the Teensy>exe to upload.

NOTE: the "Reset" process of triggering bootloader than triggering start really 'confuses' Teensy.exe as it catches the bootloader event - then gets blocked by TyComm and Teensy.exe does odd timeout when the Teensy disappears and starts running.

Also there isn't a single thread with all the Locked 1062 info - it started with TD 1.55 and is extending into TD 1.56 b1 and b2 so far. Expected hardware availability before December 2021.

[Koromix]

Thanks for the info, will eventually look into it :)

[Defragster]

Encrypted 1062's are soon if not already online - DIY bootloader chips have chipped - even it seems SFun MicroMod making one too?
Not sure if updated Teensy Loader to expose the steps is pending or do-able. When locked it seems not only must the HEX key be identified as needed - but perhaps a stub code needed to interface to the locked chip in some fashion?
To date have only tried using Teensy.exe for uploads - not sure what error TyComm might see.
Have been using IDE without integration or TSET from editor windows batch file with --delegate. Not tried 'integration with --delegate' option?
Perhaps a Teensy 1062 option by Serial# to 'delegate' uploads? Can the TeensyCLI tool be called so that loader isn't needed?

[tluliak]

Paul has posted some additional information on the .ehex file format here. Is there currently a version of TeensyCLI that will write .ehex to locked boards?