[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <4D50F75A.5040700@grandegger.com>
Date: Tue, 08 Feb 2011 08:57:14 +0100
From: Wolfgang Grandegger <wg@...ndegger.com>
To: Tomoya MORINAGA <tomoya-linux@....okisemi.com>
CC: socketcan-core@...ts.berlios.de, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: Re: About bittiming calculation result
Hi Tomoya,
On 02/08/2011 02:27 AM, Tomoya MORINAGA wrote:
> On Tuesday, February 08, 2011 12:53 AM, Wolfgang Grandegger wrote:
>
>> BTW, it's always possible to specify optimized bit-timing
>> parameters directly, e.g. the following seem better:
>>
>> 800000 60 12 4 4 4 3 793650 0.8% 80.0% 81.0% 1.2%
>>
>> You could set these with:
>>
>> $ ip link set can0 type can \
>> tq 60 prop-seg 12 phase-seg1 4 phase-seg2 4 sjw 4
>
> I can confirm 800K comms works well using the above.
Cool, I got these magic values from a CAN hardware expert.
> I wish Can-core could calculate like above.
Me too! I also got some indication on how to improve our algorithm in
case the bit-rate does not match. Hope to find some time soon to work
on this issue.
>>> seg1/seg2/sjw/prop_seg must be more than 1 ?
> BTW, according to EG20T PCH data sheet,
> CAN bit-timing parameters(BRP, Prop_Seg, Phase_Seg1, Phase_Seg2, SJW) must not be set 0.
OK, then please provide a patch setting tseg1_min to 2.
Wolfgang.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists