On Wed, May 18, 2011 at 10:24 AM, Marc Kleine-Budde <[email protected]> wrote: > On 05/18/2011 02:59 PM, Mark Slicker wrote: >> Marc, >> >> Thanks for your quick response. I reverted to my old kernel/file >> system and did a simple test just to make sure there are no hardware >> problems, everything seems ok, and the single packet is received. But >> with the new configuration, no packet is received. I did the following >> command to set up the can: >> >> /sbin/ip link set can0 type can bitrate 500000 > > you have to use "ifconfig can0 up" afterwords... :) >
Thanks, that solves one problem for me, I can see the message now. It seems silly but interface changed at lot here since I last used SocketCAN. >> And then I run my application, which listens for a message, and on my >> pc I send a single packet. Actually in ifconfig now it shows no >> packets received or transmitted and no errors, not sure what caused >> the errors before, but I can be certain that it is a software problem >> now. > > What happens if you send a single CAN frame on the at91? Are you > properly switching on any transceivers in you board file? > I'm just using the default board setup for sam9263-ek which I think does this correctly. I ran the other program again, this one uses libsocketcan for configuration, and I see the errors again, I didn't write this code so I have look into this issue more. Thanks again, Mark _______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
