hi Michael,

Good try, but the whole system hangs, so I'm guessing that we're stuck in an infinite interrupt loop. But that suggests that the issue is related to unbalanced interrupt processing somehow.

I'm going to try for some diagnostic logging once it gets stuck, and see if I can identify its state. The absolute reproducibility of the base issue leads me to think the reported empty interrupt issue (your prior email) is probably not it, but rather the driver is not handling some confluence of events properly. I have no trouble running the HUD display, for example, but it doesn't produce the rapid transmit frames of the OBDWiz dongle. Something about the transmit side is messing up the receive... I wonder if we're getting an interrupt for both the last Tx frame being sent and the VIN request PID being received at the same time? Transmit interrupts don't check for receive, and vice-versa.

Will report back later today...

Greg

Michael Balzer wrote:

Greg,

here's another report of level triggering solving the issue: https://community.nxp.com/thread/456907

Can you please give that a try? I.e. change line 77 to:

gpio_set_intr_type((gpio_num_t)m_intpin, GPIO_INTR_LOW_LEVEL);

I'll also get a DB9 plug to implement Marks test solution.

Regards,
Michael

Am 14.01.2018 um 17:52 schrieb Michael Balzer:

Hmmmm, I think level triggered interrupt would help here.

We currently let the interrupt trigger on the negative edge (line 77). Maybe GPIO_INTR_LOW_LEVEL can help?
-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________
OvmsDev mailing list
OvmsDev@lists.teslaclub.hk
http://lists.teslaclub.hk/mailman/listinfo/ovmsdev