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
Hi @zhouqicheng
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.
Regards,
Lukas