HI Sebasira
Did you ever manage to get this code to work. I'm working on getting it to work at the moment as well.
I get the same issue, the transmit method returns ERR_QED or error the message is queued. However I have found that the performance is sporadic so the first message I send will transmit onto the bus and I can see it on a scope and then on the next transmit I will get ERR_QED. This however could be because I'm not getting an acknowledgement message back which could mean the issue is a bit timing issue.
Hi David!
Well, I actually quit this project years ago... But the last test I performed, worked just fine... if you want I can look-up for the code I finally used. It was very simple, just some test, I've never pass that stage because I get involved in another work.
I never get that error or any error. But I also never test the communication with other hardware, just the inside loop-back. If you check the control registers, you'll find a bit to set it up.
So I send and receive whatever I've sent. I tested the address bits and masks in order see if it was really working and it was.
Maybe the code can help. I'll look for it and post it here.
Best Regards!
Hi
Thanks for the response, my code also works using loopback mode it just refuses to work in transmission to other nodes. I'm going to fiddle with the bit time this afternoon and see if the battle can be won there.
The reason the ISR is never executed in this driver is that the ISR routine is not given a vector number.
they have written it as interrupt void CAN_transmitISR
insteaed of interrupt 97 void CAN_transmitISR
or at least that was the case with the version of the mscan driver from freescale that I used.