Hi all,
I have a product that uses the Teensy Micromod and have come across a weird issue:
I have a customer running an older firmware that was compiled with TD1.56 and his MM runs the bootloader firmware that shipped with TD1.56 (from what I recall)
I have a new firmware version compiled with TD1.57 and an MM that has the latest bootloader firmware.
The new firmware runs just fine for me.
But for my customer, it will boot up and then crash after a few moments (it's hard to understand from him if it reboots again).
But I am wondering, is it possible that the older bootloader version on his MicroMod with a firmware built to work with the new bootloader version could cause such behavior?
He is using a custom flashing tool based on luni's TeensySharp library.
What can I do in the future to avoid this? Is there a way to update the bootloader firmware without using the TeensyLoader?
I have a product that uses the Teensy Micromod and have come across a weird issue:
I have a customer running an older firmware that was compiled with TD1.56 and his MM runs the bootloader firmware that shipped with TD1.56 (from what I recall)
I have a new firmware version compiled with TD1.57 and an MM that has the latest bootloader firmware.
The new firmware runs just fine for me.
But for my customer, it will boot up and then crash after a few moments (it's hard to understand from him if it reboots again).
But I am wondering, is it possible that the older bootloader version on his MicroMod with a firmware built to work with the new bootloader version could cause such behavior?
He is using a custom flashing tool based on luni's TeensySharp library.
What can I do in the future to avoid this? Is there a way to update the bootloader firmware without using the TeensyLoader?