[Ovmsdev] Awfully quiet out there

Mark Webb-Johnson mark at webb-johnson.net
Thu Feb 15 09:51:26 HKT 2018


My store seems ok:

OVMS > vfs ls /store
ovms_config
obd2ecu
play

OVMS > metrics list m.version
m.version                                3.0.0/factory/main build (idf v3.1-dev-391-g8d8d62da) Feb 13 2018 14:05:21

Anybody else seeing this issue?

Regarding the CONFIG_LWIP_SO_REUSE, in menuconfig you can use ‘/‘ to search for it. The parameter is in Component Config / LWIP.

Regards, Mark.

> On 15 Feb 2018, at 4:25 AM, Greg D <gregd2350 at gmail.com> wrote:
> 
> Updated ok, but I find that my config has been reset.  Poking around, I find that it /store seems to be whacked!
> 
> OVMS > vfs ls /store
> ��������.���
> ��������.���
> ��������.���
> ��������.���
> ��������.���
> ��������.���
> ��������.���
> ��������.���
> ��������.���
> ��������.���
> ��������.���
> ��������.���
> <snip>
> ovms_config
> 
> What happened?
> 
> Also, I didn't see CONFIG_LWIP_SO_REUSE come up as a config item on the first make.  Is this one I need to edit manually?  Is that related to the above?
> 
> Thanks,
> 
> Greg
> 
> 
> Mark Webb-Johnson wrote:
>> I did the merge. Unfortunately, Espressif broke mDNS by changing the API, so I’ve also had to change OVMS v3 firmware to match.
>> 
>> This means developers need to update both ESP IDF and OVMS v3 source trees, before mDNS will compile.
>> 
>> cd  ~/esp/esp-idf
>> git pull
>> git submodule update
>> 
>> cd ~/ovms/vehicle/OVMS.V3
>> git pull
>> make
>> 
>> (changing paths as appropriate)
>> 
>> Or just disable the OVMS mDNS component if you are not using it.
>> 
>> It all compiles and seems to run for me now. There are a bunch of new configuration options. The only one I would like enabled (disabled by default) is CONFIG_LWIP_SO_REUSE=y.
>> 
>> Regards, Mark.
>> 
>>> On 12 Feb 2018, at 3:02 PM, Stephen Casner <casner at acm.org <mailto:casner at acm.org>> wrote:
>>> 
>>> Mark,
>>> 
>>> I think the merge you propose should work.  As I mentioned, I'm in
>>> discussion with @projectgus to get my code merged into the mainline.
>>> 
>>>                                                        -- Steve
>>> 
>>> On Mon, 12 Feb 2018, Mark Webb-Johnson wrote:
>>> 
>>>> Steve,
>>>> 
>>>> I’m seeing weird heap corruption when I do PSRAM enabled builds and have heap debugging enabled. When I turn off the heap debugging, everything runs fine.
>>>> 
>>>> I notice this:
>>>> 
>>>> https://github.com/espressif/esp-idf/issues/1582 <https://github.com/espressif/esp-idf/issues/1582> <https://github.com/espressif/esp-idf/issues/1582 <https://github.com/espressif/esp-idf/issues/1582>>
>>>> 
>>>> and some associated fixes by Espressif to master.
>>>> 
>>>> Any issues with us merging in upstream Espress ESP IDF master to our clone? See if that resolves the problem?
>>>> 
>>>> Regards, Mark.
>>>> 
>>>>> On 12 Feb 2018, at 2:15 AM, Stephen Casner <casner at acm.org <mailto:casner at acm.org>> wrote:
>>>>> 
>>>>> It's been several days since I've seen any messages on this list.  I
>>>>> suppose that Mark has been occupied by the hardware changes.  Myself,
>>>>> I've finished the things I was working on (with the possible exception
>>>>> of adding an immediate-send option back into Mongoose), but I've
>>>>> entered a PR to get the code I added to esp-idf to support the
>>>>> per-task heap allocation commands accepted into the mainline and have
>>>>> been refining the code in response to change requests.
>>>>> 
>>>>>                                                       -- Steve
>>>>> _______________________________________________
>>>>> OvmsDev mailing list
>>>>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>>>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
>>>> 
>>> _______________________________________________
>>> OvmsDev mailing list
>>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
>> 
>> 
>> 
>> _______________________________________________
>> OvmsDev mailing list
>> OvmsDev at lists.teslaclub.hk <mailto:OvmsDev at lists.teslaclub.hk>
>> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev <http://lists.teslaclub.hk/mailman/listinfo/ovmsdev>
> 
> _______________________________________________
> OvmsDev mailing list
> OvmsDev at lists.teslaclub.hk
> http://lists.teslaclub.hk/mailman/listinfo/ovmsdev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.teslaclub.hk/pipermail/ovmsdev/attachments/20180215/c2655ae6/attachment-0001.html>


More information about the OvmsDev mailing list