mcxa145 programming anomalies Good morning, I’ve switched from using the MCXA144VLH microcontroller to the MCXA145VLL and am experiencing some issues with boards featuring this microcontroller. I tried programming a board with the MCXA145 on it, and when I try to start debugging via the IDE (using Cyclone LC), the firmware does not halt at the breakpoint in the main function (as you can see from the screenshot below). The board has never been programmed before. In a second test I carried out, I programmed the microcontroller directly via Cyclone (without going through the IDE), and the programming was successful. If, immediately after this programming, I try again via the IDE, the debugger stops correctly at the breakpoint in the main function. However, as soon as I restart the firmware, the IDE completely loses track of it and the debugger hangs (as shown in the first image). However, as soon as I restart the firmware, the IDE completely loses track of the main function and the debugger crushes(as shown in the first image). The problem I’ve noticed, however, is that the firmware isn’t actually being programmed – neither in the first way nor in the second. Whenever I switch the control unit off and on again, the firmware is lost. I’ve never had this sort of problem with the MCXA144, which runs on the same software. In this case, however, the P0_6 pin in ISP mode is fixed to GND. Could this be the cause? Thanks in advance. Best regards. Re: mcxa145 programming anomalies Hello @Transidico ,
Could you please create a new post under MCX Microcontrollers - NXP Community for the new question? It helps us track different topic.
Thanks in advance.
BR
Celeste Re: mcxa145 programming anomalies Thank you so much, Celeste – you’ve explained it very clearly. I have another question about the WWDT0. These are my settings: I use it to reset the firmware after 250 ms in case it freezes. In certain parts of my firmware, I deliberately include a `while(1)` loop to allow for this reset. Is it the right choice to use the windowed watchdog? I’ve noticed that the watchdog works correctly with one piece of hardware but not with another – is there anything that might be blocking the WWDT, or is there anything I need to be aware of? Thanks again, Celeste Re: mcxa145 programming anomalies Hello @Transidico ,
The situation is different for MCXA144VLH and MCXA145VLL.
For MCXA145VLL, only P0_6 is used as the ISP entry pin. Pin 50 (P3_29) can be used as a normal GPIO.
For MCXA144VLH(LQFP64 package), the device is affected by erratum ERR053147:
Therefore, both P0_6 and P3_29 need to be handled carefully. To avoid unintentionally entering ISP mode, please ensure that P0_6 is high during POR and P3_29 is high during a warm reset.
Hope it can help you.
BR
Celeste Re: mcxa145 programming anomalies Thanks Celeste, I tried it, and now it enters debug mode correctly. I was also wondering if pin 50 should be kept high, or if it can be used as a normal GPIO. Thanks in advance for this answer as well. Best Regards. Re: mcxa145 programming anomalies Hello @Transidico ,
Thanks for your post.
Yes, the behavior looks more like a boot/ISP-entry issue after reset rather than the programmed image actually being lost from Flash.
For normal boot from internal Flash, P0_6 should not be held low during reset. Since P0_6 is tied to GND on your board, please release this pin and repeat the programming, reset, and power-cycle tests.
As a quick check, you can also use MCUXpresso Secure Provisioning Tool and click "Test connection" after a reset or power cycle. If the connection succeeds through the ISP interface, this would indicate that the MCU has entered ISP mode rather than booting the application from internal Flash.
Hope it can help you.
BR
Celeste
View full article