muellie wrote:Version 1 is damaged and everything seems to be working fine (except the CAN itself (ERROR-Active)) on MCP2515 side.
Take care of the misleading "ERROR-Active" Flag. It is not a problem.
From the MCP2515 data-sheet (http://ww1.microchip.com/downloads/en/d ... 21801d.pdf) , you can read :
6.6 Error States wrote:each CAN node is in one of the three error states according to the value of the internal
3. Bus-off (transmitter only).
The error-active state is the usual state where the node can transmit messages and active error frames (made of dominant bits) without any restrictions.
In the error-passive state, messages and passive error frames (made of recessive bits) may be transmitted.
The bus-off state makes it temporarily impossible for the station to participate in the bus communication. During this state, messages can neither be received or transmitted. Only transmitters can go bus-off.
So, error active state means that fault detection is active (and thus will generate an interrupt if it occurs), not that it has already been detected. When the fault counters increase, it will switch to error passive, meaning it will deactivate the fault reporting. Finally, if there is too much errors on the bus, it will switch to bus off, that will stop the device.
I haven't got an hmdi monitor nor my CAN module with me for some days, so will not be able to check if hdmi plugged in is a problem. Everything I have done right now what headless by SSH.