<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
Hi Mark,<br>
<br>
Ok, did some more poking around, being careful to not wiggle too
many things at once. I can get a reliable lockup by doing the
following:<br>
<br>
1. power ext12v off<br>
2. obdii ecu stop<br>
3. power ext12v on<br>
...wait a few seconds <br>
4. obdii ecu start can3<br>
<br>
If I restart obdii too soon, all works. Otherwise, I can repeatedly
disable and re-enable 12v to cycle the HUD, and it will never
connect. The ordering of steps 1 and 2 don't seem to matter.
Unfortunately, I don't see anything in the can status that's
uniquely different between scenarios where its working and not.
Will need some additional diagnostic logging...<br>
<br>
Now, for fun, I hook the OBDII Dongle to the module, and try the
same steps, but instead of turning on the HUD, I try connecting a
few times while the OBDII ECU task is not running (simulating the
HUD's attempts to connect), then start the ecu, then try to
connect. It connects! And this is with the Dongle doing its
multi-speed scan each time. So simply having frames come in while
we're not watching, or frames coming in at the wrong speed does not
cause the hang. Rather, it might be that we've got a window in the
code where incoming traffic <i>colliding with</i> the opening of
the CAN driver is nailing the chip in some critical region. If I
hit it just right, I can sometimes cause this collision with the
Dongle by stopping the ecu, starting the connect, then restarting
the ecu during the connect sequence. Not always, but sometimes.<br>
<br>
Just a guess... I need to dust off the chip document and see if
there are any interesting bits to look at.<br>
<br>
Greg<br>
<br>
<br>
<div class="moz-cite-prefix">Mark Webb-Johnson wrote:<br>
</div>
<blockquote type="cite"
cite="mid:206B7B88-2C5D-4FCF-8CF9-DC9013495F5A@webb-johnson.net">
<div>When the client (HUD, whatever) is trying to connect to the
ECU, it can try 500K, 250K. Or it can try 250K, 500K. I suspect
yours tries the first descending sequence, and hence doesn’t
have any issues as it finds the match at 500K first.</div>
<div><br class="">
</div>
<div>Anyway, this MCP2515 can bus lockup is something we have to
fix. The fact it is reproducible on obd2ecu is good and helpful
for that.</div>
<div><br class="">
</div>
</blockquote>
<br>
</body>
</html>