in the documentation of the CAN driver's state machine are transitions from CAN_STARTING and READY to itselfs by calling canStart(). In code it is an illegal call/transition due to osalDbgAssert
Code: Select all
void canStart(CANDriver *canp, const CANConfig *config) {
osalDbgCheck(canp != NULL);
osalSysLock();
osalDbgAssert(canp->state == CAN_STOP, "invalid state");
Is this a bug?
Thanks