buckeye-current-software / can-bootloader Goto Github PK

The code for reattempting a bootload on a failure does not work currently. Suspecting the issue is the file byte stream reaching the end and not being reset.

If a bus normally runs at 500 kbit/sec, the command message must be sent over 500 Kb/sec in order to cause a C2000 device to enter bootload mode. The program then must be sent over 1 Mb/sec

Ability to change between bootloading on Kvaser bus 0 and 1.

Better error messages and more information returned to the user when an issue occurs.

Once the bootload finishes and the utility waits for the bootload success CAN message, the utility will read the first received message and check the content of that message instead of the correct message ID. Therefore, the utility thinks the bootload fails even though it succeeded

Not necessary but will make it so the utility follows Rust standards more closely.

The CanLib library function canReadWait is supposed to take a pointer to a i32 which is modified to the message ID for the received message once it returns. However, the value is always 0 regardless of ID of received message currently. This will cause the program to immediately start bootload flow when it's supposed to wait for the bootload ready command from the F28035 microcontroller being bootloaded.