Hello, On 10/18/2010 11:42 PM, Jargalan Nermunkh wrote: > I am pretty new to CAN / linux kernel and I have been working with a custom > board with the mcp2515. I managed to get it up and running with the help of > this and the socket-core mailing list. The boards use the TI OMAP-L138 and > using the davinci spi driver found here:
We have a omap (i.e. beagle board) somewhere in our lab, I'll ask the hardware guy to if he can attach the mcp2515 to it. > http://arago-project.org/git/people/?p=sneha/linux-davinci-staging.git;a=shortlog;h=refs/heads/davinci-spi-rewrite > The patch seems to fix another issue I was having with missing frames > (mcp2515 auto clears rx0, rx1 flags after its read): > http://www.mail-archive.com/[email protected]/msg01747.html You mean without the patches mentioned above, I mean the unpachted 2.6.35.x, your can controller was missing frames? After applying these patches that problem was fixed? > The CAN interface is brought up by "ip link set can0 up txqueuelen 1000 type > can bitrate 1000000" > One board collects incoming can frames with "candump -l can0" and another > board sends data using "cangen -vv -g 0 -I 255 -L 8 -D i can0". > Snippet from candump: Can you ensure with a 3rd system, preferred with a different CAN core, that the frames send to the bus are correct? Which driver is active in your setup? Does this happen with both versions of the driver? > (1273660526.261745) can0 255#6B00000000000000 > (1273660526.262940) can0 255#6C00000000000000 > (1273660526.264550) can0 255#6D00000000000000 > (1273660526.266156) can0 255#6E00000000000000 > (1273660526.267738) can0 255#6F00000000000000 > (1273660526.268450) can0 255#6F00000000000000 > (1273660526.269255) can0 004#0001000000000000 <-- > (1273660526.270810) can0 255#7100000000000000 > (1273660526.272564) can0 255#7200000000000000 > (1273660526.274213) can0 255#7300000000000000 > (1273660526.275806) can0 255#7400000000000000 > (1273660526.277356) can0 255#7500000000000000 > (1273660526.278987) can0 255#7600000000000000 > (1273660526.280579) can0 255#7700000000000000 > ... > (1273660526.679990) can0 255#D600000000000000 > (1273660526.681331) can0 255#D700000000000000 > (1273660526.682890) can0 255#D800000000000000 > (1273660526.684471) can0 255#D900000000000000 > (1273660526.686086) can0 255#DA00000000000000 > (1273660526.687702) can0 255#DB00000000000000 > (1273660526.688442) can0 255#DB00000000000000 > (1273660526.689668) can0 000#0000000000000000 <-- > (1273660526.690836) can0 255#DD00000000000000 > (1273660526.692557) can0 255#DE00000000000000 > (1273660526.694161) can0 255#DF00000000000000 > (1273660526.695781) can0 255#E000000000000000 > (1273660526.697432) can0 255#E100000000000000 > (1273660526.699022) can0 255#E200000000000000 > (1273660526.700622) can0 255#E300000000000000 > (1273660526.702224) can0 255#E400000000000000 > Not sure where this could be coming from any guidance on how to debug this > would be grateful. I'm going now to bed, but tomorrow I'm going to do some stress tests with 1 Mbit. g'night, Marc -- Pengutronix e.K. | Marc Kleine-Budde | Industrial Linux Solutions | Phone: +49-231-2826-924 | Vertretung West/Dortmund | Fax: +49-5121-206917-5555 | Amtsgericht Hildesheim, HRA 2686 | http://www.pengutronix.de |
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Socketcan-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/socketcan-users
