It's a good idea to reset the cpu before starting the main application
code. However it is difficult to reliably reset the cpu in software.
This changes the software to actually do a cpu hardware reset prior to
launching the main application - after each bootup the code checks to
see if the application should be started before entering the main
bootloader code. This helps ensure the application code is started in
a "pristine" cpu state.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
The bootloader is only called after a reset - it doesn't need to worry
about another bootloader launching it. This reduces the code size by
a small amount.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
Use Klipper's nodeid to canbus_id scheme (canbus_id = nodeid * 2 +
0x100). Instead, use a nodeid offset of 128 to avoid collisions with
Klipper.
Signed-off-by: Kevin O'Connor <kevin@koconnor.net>
This broadcasts a command to clear the id for all nodes running
the bootloader, which should prevent ID collisions.
Signed-off-by: Eric Callahan <arksine.code@gmail.com>
This is just to avoid confusion between RX_EOF and the command trailer.
Having both as 0x03 could potential lead to issues.
Signed-off-by: Eric Callahan <arksine.code@gmail.com>
This method isn't necessary as the bootloader shouldnt need to discover
multiple node ids. Change the decoded node ID offset to 0x200 in an
effort to avoid collisions with nodes assigned by Klipper.
Signed-off-by: Eric Callahan <arksine.code@gmail.com>
Bring in the latest changes from Klipper. The STM32F4 variants are
still unsupported at this time.
Signed-off-by: Eric Callahan <arksine.code@gmail.com>
