System: Windows 8 64-Bit
Bootloader: 0238a718704229933317e30673bccd5dfe052687
Adapter: matthiasbock/cantact-fw@2c134e8c17ae35662a07742602fc836b6df9f45d
When bootloader_flash - invoked with the -r argument - completes successfully, the payload firmware is started and - in my case - floods the bus with CAN frames. At the same time there is no receiver running on the PC. This causes the CANtact's red LED to light up (error indicator). When bootloader_invoke is then invoked, it fails to invoke the bootloader, presumably because the outgoing frames are never sent to the CAN bus.
The problem is resolved by disconnecting the CANtact and re-attaching it.
It might help to close the CAN channel upon program exit, but the Python client lacks an implementation of the SLCAN close channel command.
System: Windows 8 64-Bit Bootloader: 0238a718704229933317e30673bccd5dfe052687 Adapter: matthiasbock/cantact-fw@2c134e8c17ae35662a07742602fc836b6df9f45d
When bootloader_flash - invoked with the -r argument - completes successfully, the payload firmware is started and - in my case - floods the bus with CAN frames. At the same time there is no receiver running on the PC. This causes the CANtact's red LED to light up (error indicator). When bootloader_invoke is then invoked, it fails to invoke the bootloader, presumably because the outgoing frames are never sent to the CAN bus.
The problem is resolved by disconnecting the CANtact and re-attaching it.
It might help to close the CAN channel upon program exit, but the Python client lacks an implementation of the SLCAN close channel command.