Details
-
Bug
-
Resolution: Unresolved
-
P2: Important
-
None
-
Qt for MCUs 2.1.1, Qt for MCUs 2.1
Description
When flashing an application with Qt Creator (motor_cluster example for example) for NXP MIXRT1170 built with Qt for MCUs 2.1., clicking the "run" button second time while the initial flashing is still in process, leaves the board into a "faulty state" where after successful subsequent flashing the application might be running and even touches might work but nothing is displayed on the screen.
That is rather easy to accidentally do as flashing via Qt Creator does not give any visual feedback of the flashing progress as it outputs a bit later and buttons are not disabled while flashing is in process.
As a workaround:
It's possible to recover from the 'faulty state' by doing mass erase via MCUXpresso and after that flashing an NXP example of latest platform SDK and debugging that example in MCUXpresso.
After that flashing the motor_cluster example via command prompt and Qt Creator was done successfully. Doing mass erase alone did not fix the issue.
If this turns out to be issue somewhere else than in Qt for MCUs/Qt Creator, it could be good to mention in the documentation that such issue might happen and add instructions how to recover from this issue.