I accidently programmed in a KL27 file from a pervious board revision, in to new board with K32L2A. Obviously I don't expect KL27 code to run on the K32L2A.
What I don't understand is why the K32L2A is now mostly dead?
Using a PE Micro FX I can initiate a Mass Erase of the K32L2A and that starts the internal ROM USB Bootloader. I can program in the correct K32L2A code via the bootloader. The bootloader acts as if everything was completed successfully. However the unit is still dead, as it doesn't appear to start the new code even with a power cycle.
What is not being cleared out by a Mass Erase?
The only thing I can do with the PE Micro FX is mass erase, nothing else about it functions with this errantly programmed K32L2A.
Hello @bobpaddock ,
Thanks for your post. I wonder if there was any error message when you performed the mass erase operation. If so, could you please take a screenshot and show it to me?
Could you please send me the KL27 file that was wrongly programmed before? I'll check if there are any new findings.
Best Regards,
Celeste
The PE Pod is configured to do a mass erase on connect, which it does. At this point the bootloader starts. The the Pod's GUI just sets there saying "Initializing" with a spinning symbol.
Have to physically disconnect and restart it after that.
How do I get the KL27 file to you? I don't want to post it here in the forum.
Hello @bobpaddock ,
Thank you for your reply.
After the ROM bootloader is started, how do you program it? Do you use blhost? What is the return after entering the following command?
blhost --port COMx -d -- get-property 1
The usage of blhost: MCUBLHOSTUG.pdf
I understand that it is inconvenient for you to send the KL27 file through the community channel. You may submit a private case and describe your problem, and engineer will reply and provide related resource by email.
Please follow up below steps to submit a case
1. go to SUPPORTHOME, click on "Submit a Ticket" in the middle of this page.
Support | NXP Semiconductors
2.Login, Or Register with your business email
I hope it will help.
BRs,
Celeste