[Ovmsdev] Preparing for v3 development

Fri Jun 30 10:45:30 HKT 2017

Stephen,

I am simply using ‘HEAD’ from esp-idf github (MASTER branch). IDF code is still changing quite a lot, and it seems simpler to just keep in pace with their bleeding edge (at least while we are still in development mode). For something more stable, the v2.1 branch also seems fine.

Code here:

https://github.com/espressif/esp-idf.git <https://github.com/espressif/esp-idf.git>

API reference here:

https://esp-idf.readthedocs.io/en/latest/ <https://esp-idf.readthedocs.io/en/latest/>

For those with DEVKIT-C, that can also be used for OVMS v3 framework development. You can use it as is (by using menuconfig to set 4MB flash and disable OTA feature).

Alternatively, you can put DEVKIT-C on a breadboard with a Winbond W25Q128 16MB <https://www.aliexpress.com/item/W25Q128-25Q128FVAIG-New-authentic-W25Q128FVDAIG-SPI-FALSH-DIP-8PIN-300MIL-128M-bit-16M-byte-Winbond-W25Q128FV/1772836905.html?spm=2114.13010608.0.0.hkAt9E> flash chip (to make it behave like a standard OVMS v3 16MB arrangement). If you want to play with CAN on DEVKIT-C, you’ll need a 16MHz crystal <https://www.aliexpress.com/item/24PCS-6Mhz-8Mhz-12Mhz-16Mhz-20Mhz-32Mhz-Mhz-Crystal-Oscillator-HC-49S-each-4pcs/32412045228.html?spm=2114.13010608.0.0.8iCkpy>, a SN65HVD230 3.3v transceiver <https://www.aliexpress.com/item/SN65HVD230-CAN-bus-transceiver-communication-module-for-arduino/32686393467.html?spm=2114.13010608.0.0.OgM0uT>, and a few simple passive components. Really not hard.

I don’t think the code will ever be at a level I’m 100% happy with it, but what I have now is a good start and ready for other people to have a look at, comment, and add to. I’ve just had to spend so much time on the hardware and peripheral validation, I haven’t had much of a chance to bring that code over as libraries to the main framework (and my test code is messy/hacky as hell). Anyway, I’ll tidy up what I can over this weekend, and publish Monday latest:

https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3 <https://github.com/openvehicles/Open-Vehicle-Monitoring-System-3>

Regards, Mark.

P.S. For those of you who want to play with the ESP32 module in general (for other projects), I can highly recommend the test boards that have started to appear <https://www.aliexpress.com/item/ESP32-test-board-small-batch-burn-fixture-for-Le-Xin-ESP-WROOM-32-module/32802723152.html?spm=2114.13010608.0.0.NEV0WU> - these things allow you to click in the ESP32 WROOM32 module directly, for flashing, burning fuses, and general play, without soldering. The ESP32 WROOM modules <https://www.aliexpress.com/item/ESP-WROOM-32-ESP32-ESP-32S-Bluetooth-and-WIFI-Dual-Core-CPU-with-Low-Power-Consumption/32801223509.html> themselves now are under US$6, and Devkit-C style clones <https://www.aliexpress.com/item/MH-ET-LIVE-ESP32-Development-Board-WiFi-Bluetooth-Ultra-Low-Power-Consumption-Dual-Core-ESP-32/32813121497.html> are about US$1 more.

> On 30 Jun 2017, at 8:12 AM, Stephen Casner <casner at acm.org> wrote:
> 
> Mark, what version of ESP-IDF are you using for the framework
> preparation?  We need to install the same in order to be ready to take
> in code and add to it.
> 
>                                                        -- Steve
> _______________________________________________
> 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.openvehicles.com/pipermail/ovmsdev/attachments/20170630/f062b6c2/attachment.htm>