<html><head><meta http-equiv="Content-Type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; line-break: after-white-space;" class=""><blockquote type="cite" class=""><div text="#000000" bgcolor="#FFFFFF" class="">Mark:� Note also the issue with DNS failures getting to the v2 server.� I enabled the modem, got connected, then enabled WiFi (simulating arriving at home), and lost the V2 server.� Disabling Wifi didn't bring it back, and powering off the modem (in preparation for turning it back on) caused the crash.</div></blockquote><div class=""><br class=""></div>Yep, I’m aware of that. Discussed on the list a few days ago - seems to be the DNS server configuration when both WiFi and PPP running at the same time.<br class=""><div><br class=""></div><div><blockquote type="cite" class=""><div text="#000000" bgcolor="#FFFFFF" class="">Second, overall memory usage seems to be at the limit.� What sort of budget do we have for what remains to be done, and how are we going to be packaging the build options for when non-developers want to get their hands on the product?� Will we be able to turn everything on, minus the developer / debug stuff, or will we have a separate SKU for each model car?<br class=""></div></blockquote><div><br class=""></div>The OTA system supports both. I’d prefer everything in one build, but it really depends on the flash footprint we end up with.</div><div><br class=""></div><div>Regards, Mark.</div><div><br class=""><blockquote type="cite" class=""><div class="">On 8 Jan 2018, at 3:05 AM, Greg D. <<a href="mailto:gregd2350@gmail.com" class="">gregd2350@gmail.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">
<meta http-equiv="Content-Type" content="text/html;
charset=us-ascii" class="">
<div text="#000000" bgcolor="#FFFFFF" class="">
Hi Michael, Steve, Mark,<br class="">
<br class="">
Steve, the crash was an abort in <a href="http://new_op.cc" class="">new_op.cc</a>, so perhaps being out of
space is the issue.� Crash and reboot log attached (crash.txt).� One
thing I've been wondering about are the several lines
"_WindowOverflow4 at ??:?" during the boot process.� Is that
indicative of a problem, later to manifest in the crash?<br class="">
<br class="">
My builds include pretty much everything, except for the Leaf,
Twizy, and Soul.� <br class="">
<br class="">
The update included some 20 lines changed to mcp2525.cpp, as well as
a bunch of other stuff, including a lot stuff updated in Canopen and
Kia.� I have a script that does the git fetch master, merge, and
push back to my github fork, the output of which is attached
(update.txt).� <b class="">As a test, I removed Canopen from the build
config, and the crash has disappeared.� </b>CAN-3 also appears to
have come back to life (!), at least initially.� I can still get
CAN-3 to fail if I turn on/off the modem and/or wifi in some
sequence (still trying to pin that down), but that also leads to
another crash (crash2.txt, attached).� <br class="">
<br class="">
Mark:� Note also the issue with DNS failures getting to the v2
server.� I enabled the modem, got connected, then enabled WiFi
(simulating arriving at home), and lost the V2 server.� Disabling
Wifi didn't bring it back, and powering off the modem (in
preparation for turning it back on) caused the crash.<br class="">
<br class="">
So, two questions...� First, why the apparent conflict between
Canopen or wifi/modem and obd2ecu over access to the 3rd CAN bus?�
Why would the modem or wifi have any effect on a CAN bus?<br class="">
<br class="">
Second, overall memory usage seems to be at the limit.� What sort of
budget do we have for what remains to be done, and how are we going
to be packaging the build options for when non-developers want to
get their hands on the product?� Will we be able to turn everything
on, minus the developer / debug stuff, or will we have a separate
SKU for each model car?<br class="">
<br class="">
Thanks,<br class="">
<br class="">
Greg<br class="">
<br class="">
<br class="">
<div class="moz-cite-prefix">Michael Balzer wrote:<br class="">
</div>
<blockquote type="cite" cite="mid:7bb15ca0-edce-61aa-37ff-546500511052@expeedo.de" class="">
<pre wrap="" class="">Greg,
which commits / changes do you mean? The CAN drivers have not been changed since the TX performance fix, which Geir reported having solved his last issues.
The current version is stable over here, but without the SSH component -- I can't use that due to memory getting too low together with the Twizy component.
Regards,
Michael
Am 07.01.2018 um 08:04 schrieb Greg D.:
</pre>
<blockquote type="cite" class="">
<pre wrap="" class="">Hi folks,
I just resync'd with the main repository, and am not receiving frames on
CAN-3 anymore. I see there were changes to the chip driver...
I'm also seeing crashes right after getting connected to WiFi,
immediately after the system tries to start SSH.
Seems like we just took a big step backward. What happened?
Greg
_______________________________________________
OvmsDev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OvmsDev@lists.teslaclub.hk">OvmsDev@lists.teslaclub.hk</a>
<a class="moz-txt-link-freetext" href="http://lists.teslaclub.hk/mailman/listinfo/ovmsdev">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev</a>
</pre>
</blockquote>
<pre wrap="" class=""></pre>
</blockquote>
<br class="">
</div>
<span id="cid:07897FD4-529B-4045-A998-7090A97175EA"><update.txt></span><span id="cid:3D985759-CD9A-421D-AF44-09EECC0F8985"><crash.txt></span><span id="cid:F616F324-AD6D-4D64-9C6D-57A3BC9D4D9C"><crash2.txt></span>_______________________________________________<br class="">OvmsDev mailing list<br class=""><a href="mailto:OvmsDev@lists.teslaclub.hk" class="">OvmsDev@lists.teslaclub.hk</a><br class="">http://lists.teslaclub.hk/mailman/listinfo/ovmsdev<br class=""></div></blockquote></div><br class=""></body></html>