https://community.nxp.com/t5/S32K/s32k144/m-p/1730023#M27407 <P>Hello, bootlaoder communication burning. After modifying the hardware, I found that when burning the program, sometimes I found that all can messages were 0 and could not be burned. I asked if it was possible that there was a problem with the can chip or that the mcu BootLoader area was damaged, and what could be the reason for this</P> Wed, 27 Sep 2023 01:58:09 GMT zhouqicheng 2023-09-27T01:58:09Z https://community.nxp.com/t5/S32K/s32k144/m-p/1730023#M27407 <P>Hello, bootlaoder communication burning. After modifying the hardware, I found that when burning the program, sometimes I found that all can messages were 0 and could not be burned. I asked if it was possible that there was a problem with the can chip or that the mcu BootLoader area was damaged, and what could be the reason for this</P> Wed, 27 Sep 2023 01:58:09 GMT https://community.nxp.com/t5/S32K/s32k144/m-p/1730023#M27407 zhouqicheng 2023-09-27T01:58:09Z https://community.nxp.com/t5/S32K/s32k144/m-p/1731832#M27480 <P>Hi <a href="https://community.nxp.com/t5/user/viewprofilepage/user-id/205585">@zhouqicheng</a>&nbsp;</P> <P>this is very general description. There could be a lot of reasons for this. First step is to attach a debugger and check if the bootloader is still in place and then check where the code is hanging or what actually happened. Without this, I'm not able to help.</P> <P>Regards,</P> <P>Lukas</P> Fri, 29 Sep 2023 07:09:08 GMT https://community.nxp.com/t5/S32K/s32k144/m-p/1731832#M27480 lukaszadrapa 2023-09-29T07:09:08Z