[Ovmsdev] Developer Manual?

[Fran Terry]

Hi Mark,

Also having the same issues here, if you follow the instructions,the 2.1
branch doesn't contain components/heap, have switched to master branch,
however support/sdkconfig.default.hw31 seems to be missing a lot of
configuration, get asked lots of questions, such as:

'make' warns on undefined variables (MAKE_WARN_UNDEFINED_VARIABLES) [Y/n/?]
(NEW)

*

* Bootloader config

*

Bootloader log verbosity

  1. No output (LOG_BOOTLOADER_LEVEL_NONE)

  2. Error (LOG_BOOTLOADER_LEVEL_ERROR)

> 3. Warning (LOG_BOOTLOADER_LEVEL_WARN)

  4. Info (LOG_BOOTLOADER_LEVEL_INFO)

  5. Debug (LOG_BOOTLOADER_LEVEL_DEBUG)

  6. Verbose (LOG_BOOTLOADER_LEVEL_VERBOSE)

choice[1-6?]: 3

SPI Flash WP Pin when customising pins via efuse (read help)
(BOOTLOADER_SPI_WP_PIN) [7] (NEW)

VDDSDIO LDO voltage

  1. 1.8V (BOOTLOADER_VDDSDIO_BOOST_1_8V) (NEW)

> 2. 1.9V (BOOTLOADER_VDDSDIO_BOOST_1_9V) (NEW)

choice[1-2?]:

I've tried to answer as many as I believe are to be correct, however I
guess the question is, is the master branch correct for esp-idf and does
anyone have a sdkconfig that has all the correct answers for this version?

Thanks

Fran

On 23 April 2018 at 01:33, Mark Webb-Johnson <mark at webb-johnson.net> wrote:

> Michael,
>
> Do you still have the old sdkconfig around? If so, please do a ‘diff -u
> support/sdkconfig.default.hw31 sdkconfig’ so we can see what is different.
>
> Regards, Mark
>
> > On 22 Apr 2018, at 4:44 PM, Michael Stegen <michael at stegen.com> wrote:
> >
> > Mark,
> >
> > Copying support/sdkconfig.default.hw31 to sdkconfig fixed the issue,
> thanks!
> >
> > -Mike
> >
> >
> >
> > Op 21-4-2018 om 16:46 schreef Mark Webb-Johnson:
> >> Can you try copy support/sdkconfig.default.hw31 to sdkconfig to give a
> standard set of defaults (those used for production). You will then need to
> adjust the UART path appropriately.
> >>
> >> Also, please ‘git pull’ on each of the projects, to make sure you have
> the latest sources.
> >>
> >> Regards, Mark.
> >>
> >>> On 21 Apr 2018, at 10:30 PM, Michael Stegen <michael at stegen.com>
> wrote:
> >>>
> >>> Steve,
> >>>
> >>> Thanks for your suggestion.
> >>> I tried it ( git submodule update --init) and it did install mongoose
> in the correct folder.
> >>>
> >>> However, as you already noticed, this was not the solution to the
> problem.
> >>>
> >>> Exact same error also happens on a Ubuntu 16.04 installation i did.
> >>> I'm clearly missing something... but what?
> >>>
> >>> -Mike
> >>>
> >>>
> >>> Op 21-4-2018 om 8:43 schreef Stephen Casner:
> >>>> Mike,
> >>>>
> >>>> Separately cloning mongoose is not the usual procedure.  Normally it
> >>>> is just "git submodule update" after cloning OVMS.  That is not an
> >>>> explanation for the compilation error you encountered, though.
> >>>> Something else is missing.
> >>>>
> >>>>                                                         -- Steve
> >>>>
> >>>> On Fri, 20 Apr 2018, Michael Stegen wrote:
> >>>>
> >>>>> Hi OVMS v3 devs,
> >>>>>
> >>>>> In preparation of receiveing the module, i'm trying to compile what's
> >>>>> currently on github.
> >>>>> But while doing so, i'm running into problems
> >>>>>
> >>>>> I did the following:
> >>>>> Install the toolchain (windows)
> >>>>>
> >>>>> cd ~/esp
> >>>>> git clone --recursive https://github.com/openvehicles/esp-idf.git
> >>>>> cd ..
> >>>>> git clone https://github.com/openvehicles/Open-Vehicle-
> Monitoring-System-3.git
> >>>>> then in the  /components/mongoose/ folder did:
> >>>>> git clone https://github.com/openvehicles/mongoose.git
> >>>>>
> >>>>> It now does compile up to the following error message:
> >>>>>
> >>>>> In file included from
> >>>>> C:/msys32/home/Mike/Open-Vehicle-Monitoring-System-3/
> vehicle/OVMS.V3/components/simcom/src/simcom.h:34:0,
> >>>>>                  from
> >>>>> C:/msys32/home/Mike/Open-Vehicle-Monitoring-System-3/
> vehicle/OVMS.V3/main/ovms_peripherals.h:67,
> >>>>>                  from
> >>>>> C:/msys32/home/Mike/Open-Vehicle-Monitoring-System-3/
> vehicle/OVMS.V3/components/esp32can/src/esp32can.cpp:42:
> >>>>> C:/msys32/home/Mike/Open-Vehicle-Monitoring-System-3/
> vehicle/OVMS.V3/components/simcom/src/gsmpppos.h:63:5:
> >>>>> error: 'ppp_pcb' does not name a type
> >>>>>      ppp_pcb*     m_ppp;
> >>>>>      ^
> >>>>> C:/msys32/home/Mike/Open-Vehicle-Monitoring-System-3/
> vehicle/OVMS.V3/components/simcom/src/gsmpppos.h:64:18:
> >>>>> error: field 'm_ppp_netif' has incomplete type 'netif'
> >>>>>      struct netif m_ppp_netif;
> >>>>>                   ^
> >>>>>
> >>>>> Any idea what i'm missing?
> >>>>>
> >>>>> -Mike
> >>>> _______________________________________________
> >>>> OvmsDev mailing list
> >>>> 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
> >
> >
> > _______________________________________________
> > OvmsDev mailing list
> > 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
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openvehicles.com/pipermail/ovmsdev/attachments/20180603/57515939/attachment.html>