[Ovmsdev] Can buses stop after some time

[Michael Balzer]

I already changed the charge alerts to inline calls, but of course the stack footprint is a bit higher with notifications.

Regards,
Michael


Am 12.05.2018 um 15:03 schrieb Mark Webb-Johnson:
>
> I think this is the new charge alerts in vehicle.{h, cpp}. They call the command ‘STAT’, which may consume a lot of stack (executing commands does).
>
> I suggest you change vehicle stack size to 6144. That is the default now in sdkconfig.default.hw31 that I just pushed. You will need to make menuconfig and
> find it in the vehicle support section of open vehicles component. Diff sdkconfig support/sdkconfig.default.hw31 to see the changes.
>
> Regards, Mark.
>
>> On 11 May 2018, at 10:15 PM, Mark Webb-Johnson <mark at webb-johnson.net <mailto:mark at webb-johnson.net>> wrote:
>>
>> Can you:
>>
>>     diff sdkconfig support/sdkconfig.default.hw31
>>
>>
>> and make sure the same? Maybe stack sizes are different?
>>
>> Or maybe something in your vehicle type is using up a lot of stack. Try ‘module tasks’ to see.
>>
>> Regards, Mark.
>>
>>> On 11 May 2018, at 9:42 PM, Robin O'Leary <ovmsdev at caederus.org <mailto:ovmsdev at caederus.org>> wrote:
>>>
>>> On Fri, May 11, 2018 at 08:08:10PM +0800, Mark Webb-Johnson wrote:
>>>> I think —tags is missing?
>>>> I normally ‘git fetch origin —tags as the first step.
>>>
>>> Ah, thanks, that fixed the the version label.
>>>
>>> My build still crashes though, this time with another stack overflow:
>>>
>>> OVMS# ***ERROR*** A stack overflow in task OVMS Vehicle has been detected.
>>> abort() was called at PC 0x40092f00 on core 1
>>>
>>> Backtrace: 0x40092cec:0x3ffdcaf0 0x40092ee7:0x3ffdcb10 0x40092f00:0x3ffdcb30 0x4008f33c:0x3ffdcb50 0x40090f90:0x3ffdcb70 0x40090f46:0xa5a5a5a5
>>>
>>> Rebooting...
>>>
>>> 0x40092cec invoke_abort + 24 in section .iram0.text
>>> 0x40092ee7 abort + 39 in section .iram0.text
>>> 0x40092f00 vApplicationStackOverflowHook + 20 in section .iram0.text
>>> 0x4008f33c vTaskSwitchContext + 200 in section .iram0.text
>>> 0x40090f90 _frxt_dispatch in section .iram0.text
>>> 0x40090f46 _frxt_int_exit + 70 in section .iram0.text
>>>
>>>
>>> btw, something helpfully mapped the character sequence "[dash][dash]tags"
>>> in your message to "[en-dash]tags"; if you cut-and-paste that directly
>>> to a command line, you get a rather confusing error:
>>>
>>> $ git fetch origin —tags
>>> fatal: Couldn't find remote ref —tags
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>>
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.openvehicles.com <mailto:OvmsDev at lists.openvehicles.com>
>> http://lists.openvehicles.com/mailman/listinfo/ovmsdev
>
>
>
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.openvehicles.com
> http://lists.openvehicles.com/mailman/listinfo/ovmsdev

-- 
Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal
Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180512/ba08813d/attachment.htm>