November 2021 - OvmsDev - Open Vehicles

Netmanager priority issue solved
by Michael Balzer 05 Jul '23

05 Jul '23

TL;DR: you need to pull my latest esp-idf changes. I've finally found & solved the strange priority changes for our netmanager task (i.e. being raised suddenly from origin 5 to 18/22): the bug was in the esp-idf posix threads mutex implementation. I had suspected the mutex priority inheritance for a while, so added a way to retrieve the internal mutex hold count for our task list. Using this I noticed the hold count would always & only raise by 2 whenever any kind of mongoose connection was closed. That lead me to checking the thread concurrency protection for mongoose mbufs, because every mongoose connection has two mbufs associated (rx & tx), each having a posix mutex. The bug was: posix mutexes were deleted after locking (taking) them. FreeRTOS mutexes must not be deleted while being taken, that breaks the priority inheritance (more precisely the disinheritance), with the visible effect being the mutex hold count not returning to zero. As a side effect, this may also solve the strange event task starvations (hope so…). I was investigating this as I suspected some busy loop in the netmanager context. With the netman running at prio 22, that would effectively block almost all other processing including the timer service. I've found & fixed one potential busy loop trigger in the netman that would have been caused by the netman task still running while all interfaces had been lost -- not sure if that could happen, but it would explain the effects. So please watch your crash debug info & report if the issue still turns up. Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

5 19

IOS app reported GSM signal strength
by Craig Leres 17 Oct '22

17 Oct '22

I've noticed for awhile but never asked the question; why does the IOS app report wifi signal strength when I'm connected to wifi as gsm signal strength? I would expect gsm to always be gsm and maybe wifi would also be shown (and identified as such) when present. Note that I run my modules in wifi client-only mode. Craig

2 2

OVMS v3.3 hardware
by Mark Webb-Johnson 23 Feb '22

23 Feb '22

For the 4G modem options we need to go through FCC, CE, and ROHS certification. Minimising/eliminating the changes to the main board simplifies this (and brings down the exorbitant costs) but if there is anything urgent / necessary, now is the time to do it. The goal here is to maintain 100% compatibility with existing OVMS main boards, to keep this is a simple and relatively cheap upgrade of the modem board. So far, I have come up with this minimal list: Main board v3.3: Improve soldering of micro USB port. Bigger solder pads, and more solder to secure it better. Modem board v1.3: Add support for SIM7600 module. Modem board v1.3: Fix support for DTR sleep/awake support. Is there anything else required for this update? Regards, Mark.

4 37

TLS CA question
by Stephen Casner 29 Jan '22

29 Jan '22

I find that I need to enable the following option in my testing of the possible replacement of MEDTLS with WolfSSL, otherwise I get an "ASN no signer to confirm" error: WOLFSSL_ALT_CERT_CHAIN allows CA's to be presented by peer, but not part of a valid chain. Default wolfSSL behavior is to require validation of all presented peer certificates. This also allows loading intermediate CA's as trusted and ignoring no signer failures for CA's up the chain to root. The alternate certificate chain mode only requires that the peer certificate validate to a trusted CA. Is that expected for the trust arrangements we are using? A possibly related question: do we expect the server to validate clients, or only the clients to validate the server? -- Steve

4 60

MCP2515 driver bug?
by Mark Webb-Johnson 20 Jan '22

20 Jan '22

I’m working on an implementation of IP stack over CAN for the Tesla Roadster. IP frames are encoded as a length followed by a sequence of CAN frames, all on the same ID. This runs over a 1MHz bus, so presumably the traffic volume could be high at times. I was having problems with this running on CAN2, so tried CAN1 and it worked perfectly. Here are some simple dumps of a single PING packet (and single PING response packet): ID #111 is used to transmit an IP packet, and ID #110 is used to receive an IP packet. The special empty data frame is an acknowledgment. Using latest master branch code (3.2.016-196-g0aad1a9f/ota_1/edge (build idf v3.3.4-848-g1ff5e24b1 Jun 2 2021 09:28:58)). So, first let’s test with traffic on CAN1 (active, 1Mbps), and listening on CAN2 (listen, 1Mbps): TCPDUMP: 05:57:55.980291 IP (tos 0x0, ttl 64, id 43101, offset 0, flags [DF], proto ICMP (1), length 84) 10.10.99.3 > 10.10.99.2: ICMP echo request, id 23372, seq 1, length 64 0x0000: 4500 0054 a85d 4000 4001 b832 0a0a 6303 E..T.]@.@..2..c. 0x0010: 0a0a 6302 0800 7df8 5b4c 0001 5361 b860 ..c...}.[L..Sa.` 0x0020: 19f5 0e00 0809 0a0b 0c0d 0e0f 1011 1213 ................ 0x0030: 1415 1617 1819 1a1b 1c1d 1e1f 2021 2223 .............!"# 0x0040: 2425 2627 2829 2a2b 2c2d 2e2f 3031 3233 $%&'()*+,-./0123 0x0050: 3435 3637 4567 05:57:56.436190 IP (tos 0x0, ttl 64, id 14937, offset 0, flags [none], proto ICMP (1), length 84) 10.10.99.2 > 10.10.99.3: ICMP echo reply, id 23372, seq 1, length 64 0x0000: 4500 0054 3a59 0000 4001 6637 0a0a 6302 E..T:Y..@.f7..c. 0x0010: 0a0a 6303 0000 85f8 5b4c 0001 5361 b860 ..c.....[L..Sa.` 0x0020: 19f5 0e00 0809 0a0b 0c0d 0e0f 1011 1213 ................ 0x0030: 1415 1617 1819 1a1b 1c1d 1e1f 2021 2223 .............!"# 0x0040: 2425 2627 2829 2a2b 2c2d 2e2f 3031 3233 $%&'()*+,-./0123 0x0050: 3435 3637 4567 Traffic (as shown on PC the other end of the can log tcp connection): tx: #111 54 00 tx: #111 45 00 00 54 a8 5d 40 00 tx: #111 40 01 b8 32 0a 0a 63 03 tx: #111 0a 0a 63 02 08 00 7d f8 tx: #111 5b 4c 00 01 53 61 b8 60 tx: #111 19 f5 0e 00 08 09 0a 0b tx: #111 0c 0d 0e 0f 10 11 12 13 tx: #111 14 15 16 17 18 19 1a 1b tx: #111 1c 1d 1e 1f 20 21 22 23 tx: #111 24 25 26 27 28 29 2a 2b tx: #111 2c 2d 2e 2f 30 31 32 33 tx: #111 34 35 36 37 rx: #110 rx: #110 54 00 rx: #110 45 00 00 54 3a 59 00 00 rx: #110 40 01 66 37 0a 0a 63 02 rx: #110 0a 0a 63 03 00 00 85 f8 rx: #110 5b 4c 00 01 53 61 b8 60 rx: #110 19 f5 0e 00 08 09 0a 0b rx: #110 0c 0d 0e 0f 10 11 12 13 rx: #110 14 15 16 17 18 19 1a 1b rx: #110 1c 1d 1e 1f 20 21 22 23 rx: #110 24 25 26 27 28 29 2a 2b rx: #110 2c 2d 2e 2f 30 31 32 33 rx: #110 34 35 36 37 CAN1 active: 1T11 111 54 00 1R11 110 1CER TX_Queue T11 111 40 01 b8 32 0a 0a 63 03 1T11 111 45 00 00 54 a8 5d 40 00 1T11 111 40 01 b8 32 0a 0a 63 03 1CER TX_Queue T11 111 5b 4c 00 01 53 61 b8 60 1T11 111 0a 0a 63 02 08 00 7d f8 1T11 111 5b 4c 00 01 53 61 b8 60 1CER TX_Queue T11 111 0c 0d 0e 0f 10 11 12 13 1T11 111 19 f5 0e 00 08 09 0a 0b 1T11 111 0c 0d 0e 0f 10 11 12 13 1CER TX_Queue T11 111 1c 1d 1e 1f 20 21 22 23 1T11 111 14 15 16 17 18 19 1a 1b 1T11 111 1c 1d 1e 1f 20 21 22 23 1CER TX_Queue T11 111 2c 2d 2e 2f 30 31 32 33 1T11 111 24 25 26 27 28 29 2a 2b 1T11 111 2c 2d 2e 2f 30 31 32 33 1T11 111 34 35 36 37 1R11 110 54 00 1R11 110 45 00 00 54 3a 59 00 00 1R11 110 40 01 66 37 0a 0a 63 02 1R11 110 0a 0a 63 03 00 00 85 f8 1R11 110 5b 4c 00 01 53 61 b8 60 1R11 110 19 f5 0e 00 08 09 0a 0b 1R11 110 0c 0d 0e 0f 10 11 12 13 1R11 110 14 15 16 17 18 19 1a 1b 1R11 110 1c 1d 1e 1f 20 21 22 23 1R11 110 24 25 26 27 28 29 2a 2b 1R11 110 2c 2d 2e 2f 30 31 32 33 1R11 110 34 35 36 37 CAN2 listen: 2R11 111 54 00 2R11 110 2R11 111 45 00 00 54 a8 5d 40 00 2R11 111 40 01 b8 32 0a 0a 63 03 2R11 111 0a 0a 63 02 08 00 7d f8 2R11 111 5b 4c 00 01 53 61 b8 60 2R11 111 19 f5 0e 00 08 09 0a 0b 2R11 111 0c 0d 0e 0f 10 11 12 13 2R11 111 14 15 16 17 18 19 1a 1b 2R11 111 1c 1d 1e 1f 20 21 22 23 2R11 111 24 25 26 27 28 29 2a 2b 2R11 111 2c 2d 2e 2f 30 31 32 33 2R11 111 34 35 36 37 2R11 110 54 00 2CER Error intr=10 rxpkt=14 txpkt=0 errflags=0x23401c01 rxerr=0 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=0 txfail=0 wdgreset=0 errreset=0 2R11 110 40 01 66 37 0a 0a 63 02 2R11 110 19 f5 0e 00 08 09 0a 0b 2R11 110 34 35 36 37 2R11 110 45 00 00 54 3a 59 00 00 Conclusion is that the CAN1 traffic looks fine, and the PING packet gets a good reply. All successful. But the CAN2 listen is missing a few packets and the last packet is out of order. Now, let’s test with traffic on CAN2 (active, 1Mbps), and listening on CAN1 (listen, 1Mbps): TCPDUMP: 06:00:33.004060 IP (tos 0x0, ttl 64, id 58240, offset 0, flags [DF], proto ICMP (1), length 84) 10.10.99.3 > 10.10.99.2: ICMP echo request, id 23393, seq 1, length 64 0x0000: 4500 0054 e380 4000 4001 7d0f 0a0a 6303 E..T..@.@.}...c. 0x0010: 0a0a 6302 0800 7cc8 5b61 0001 f161 b860 ..c...|.[a...a.` 0x0020: 8b0f 0000 0809 0a0b 0c0d 0e0f 1011 1213 ................ 0x0030: 1415 1617 1819 1a1b 1c1d 1e1f 2021 2223 .............!"# 0x0040: 2425 2627 2829 2a2b 2c2d 2e2f 3031 3233 $%&'()*+,-./0123 0x0050: 3435 3637 4567 Traffic (as shown on PC the other end of the can log tcp connection): tx: #111 54 00 tx: #111 45 00 00 54 e3 80 40 00 tx: #111 40 01 7d 0f 0a 0a 63 03 tx: #111 0a 0a 63 02 08 00 7c c8 tx: #111 5b 61 00 01 f1 61 b8 60 tx: #111 8b 0f 00 00 08 09 0a 0b tx: #111 0c 0d 0e 0f 10 11 12 13 tx: #111 14 15 16 17 18 19 1a 1b tx: #111 1c 1d 1e 1f 20 21 22 23 tx: #111 24 25 26 27 28 29 2a 2b tx: #111 2c 2d 2e 2f 30 31 32 33 tx: #111 34 35 36 37 rx: #110 rx: #110 54 00 rx: #110 45 00 00 54 3a 5a 00 00 rx: #110 0a 0a 63 03 00 00 84 c8 rx: #110 8b 0f 00 00 08 09 0a 0b rx: #110 34 35 36 37 rx: #110 40 01 66 36 0a 0a 63 02 CAN2 active: 2T11 111 54 00 2R11 110 2CER TX_Queue T11 111 40 01 7d 0f 0a 0a 63 03 2T11 111 45 00 00 54 e3 80 40 00 2T11 111 40 01 7d 0f 0a 0a 63 03 2CER TX_Queue T11 111 5b 61 00 01 f1 61 b8 60 2T11 111 0a 0a 63 02 08 00 7c c8 2T11 111 5b 61 00 01 f1 61 b8 60 2CER TX_Queue T11 111 0c 0d 0e 0f 10 11 12 13 2T11 111 8b 0f 00 00 08 09 0a 0b 2T11 111 0c 0d 0e 0f 10 11 12 13 2CER TX_Queue T11 111 1c 1d 1e 1f 20 21 22 23 2T11 111 14 15 16 17 18 19 1a 1b 2T11 111 1c 1d 1e 1f 20 21 22 23 2CER TX_Queue T11 111 2c 2d 2e 2f 30 31 32 33 2T11 111 24 25 26 27 28 29 2a 2b 2T11 111 2c 2d 2e 2f 30 31 32 33 2T11 111 34 35 36 37 2R11 110 54 00 2R11 110 45 00 00 54 3a 5a 00 00 2CER Error intr=15 rxpkt=3 txpkt=12 errflags=0x23401c01 rxerr=0 txerr=0 rxinval=0 rxovr=0 txovr=0 txdelay=5 txfail=0 wdgreset=0 errreset=0 2R11 110 0a 0a 63 03 00 00 84 c8 2R11 110 8b 0f 00 00 08 09 0a 0b 2R11 110 34 35 36 37 2R11 110 40 01 66 36 0a 0a 63 02 CAN1 listen: 1R11 111 54 00 1R11 110 1R11 111 45 00 00 54 e3 80 40 00 1R11 111 40 01 7d 0f 0a 0a 63 03 1R11 111 0a 0a 63 02 08 00 7c c8 1R11 111 5b 61 00 01 f1 61 b8 60 1R11 111 8b 0f 00 00 08 09 0a 0b 1R11 111 0c 0d 0e 0f 10 11 12 13 1R11 111 14 15 16 17 18 19 1a 1b 1R11 111 1c 1d 1e 1f 20 21 22 23 1R11 111 24 25 26 27 28 29 2a 2b 1R11 111 2c 2d 2e 2f 30 31 32 33 1R11 111 34 35 36 37 1R11 110 54 00 1R11 110 45 00 00 54 3a 5a 00 00 1R11 110 40 01 66 36 0a 0a 63 02 1R11 110 0a 0a 63 03 00 00 84 c8 1R11 110 5b 61 00 01 f1 61 b8 60 1R11 110 8b 0f 00 00 08 09 0a 0b 1R11 110 0c 0d 0e 0f 10 11 12 13 1R11 110 14 15 16 17 18 19 1a 1b 1R11 110 1c 1d 1e 1f 20 21 22 23 1R11 110 24 25 26 27 28 29 2a 2b 1R11 110 2c 2d 2e 2f 30 31 32 33 1R11 110 34 35 36 37 Conclusion is that the CAN2 transmit traffic looks fine, but no PING reply received via CAN. The CAN1 listen shows the reply just fine. Here is that last CAN1 listen, with timestamps: 1622696433.080107 1R11 111 54 00 1622696433.081657 1R11 110 1622696433.227479 1R11 111 45 00 00 54 e3 80 40 00 1622696433.228318 1R11 111 40 01 7d 0f 0a 0a 63 03 1622696433.245727 1R11 111 0a 0a 63 02 08 00 7c c8 1622696433.246214 1R11 111 5b 61 00 01 f1 61 b8 60 1622696433.248219 1R11 111 8b 0f 00 00 08 09 0a 0b 1622696433.248772 1R11 111 0c 0d 0e 0f 10 11 12 13 1622696433.250774 1R11 111 14 15 16 17 18 19 1a 1b 1622696433.251338 1R11 111 1c 1d 1e 1f 20 21 22 23 1622696433.253380 1R11 111 24 25 26 27 28 29 2a 2b 1622696433.253944 1R11 111 2c 2d 2e 2f 30 31 32 33 1622696433.265937 1R11 111 34 35 36 37 1622696433.269221 1R11 110 54 00 1622696433.272095 1R11 110 45 00 00 54 3a 5a 00 00 1622696433.272125 1R11 110 40 01 66 36 0a 0a 63 02 1622696433.272156 1R11 110 0a 0a 63 03 00 00 84 c8 1622696433.272193 1R11 110 5b 61 00 01 f1 61 b8 60 1622696433.272245 1R11 110 8b 0f 00 00 08 09 0a 0b 1622696433.272277 1R11 110 0c 0d 0e 0f 10 11 12 13 1622696433.272314 1R11 110 14 15 16 17 18 19 1a 1b 1622696433.272354 1R11 110 1c 1d 1e 1f 20 21 22 23 1622696433.272387 1R11 110 24 25 26 27 28 29 2a 2b 1622696433.272420 1R11 110 2c 2d 2e 2f 30 31 32 33 1622696433.272452 1R11 110 34 35 36 37 It is 1Mbps, with 30us or so between each packet. This is the only traffic on the bus. Everything else is turned off. Roughly 12 packets each way. Surely even if we were hitting a performance limit, our buffers can handle 12 packets? The good news is that I have a good environment to replicate this issue now, so any fix should be easy to test. I haven’t worked on the MCP2515 driver in our code in a long time, but it certainly seems something is messed up and that could be badly affecting vehicle modules using anything other than CAN1. I will start to look at this over the weekend, but has anyone got any ideas/suggestions? Perhaps the bit timing registers are off by a small amount (so it works on CAN1 but not on CAN2)? Or something more serious in our driver? Regards, Mark.

6 22

3.2.018 release
by Mark Webb-Johnson 16 Dec '21

16 Dec '21

We need to get the v3.3 release ready for release now, as the new v3.3 hardware is about to enter production and the factory needs the firmware. Accordingly, I suggest: I have already updated the for-v3.3 branch with all the recent changes from v3.2. We now (today/tomorrow) release the current v3.2 branch as tag 3.2.018, OTA release. This would be the (hopefully) last v3.2 release. After release of that, we branch off master to a v3.2 branch, for historical purposes (and if we need it for anything). We then merge back for-v3.3 into the master branch and start working through the usual daily builds for that to get it ready for production. I think there is still some work to do on pouring the plugins, but the core code (and in particular new modem support) should be ok now. I think we will need to investigate an approach for dual builds for v3.3-or-later and pre-v3.3 hardware, to take advantage of the new ESP32 rev3 chips. I think those will require a different sdkconfig. We can do that automatically in the OTA system, by building the URL based on the ESP32 platform revision. Should we do that with the v3.3 release (even if the builds are for the moment the same), or at a later date? Regards, Mark.

3 25

for-v3.3: ota flash http crashes
by Michael Balzer 23 Nov '21

23 Nov '21

There is another fatal issue with OvmsSyncHttpClient besides the issue with running in the mongoose context: OTA updates are no longer possible. When flashing via HTTP, the OvmsSyncHttpClient tries to allocate memory for a full firmware image, which of course fails: OVMS# ota flash http Current running partition is: factory Target partition is: ota_0 Download firmware from ovms.dexters-web.de/firmware/ota/v3.1/edge/ovms3.bin to ota_0 Guru Meditation Error: Core 1 panic'ed (StoreProhibited). Exception was unhandled. Core 1 register dump: PC : 0x4022438b PS : 0x00060a30 A0 : 0x802245cd A1 : 0x3ffe9c70 A2 : 0x00000000 A3 : 0x3ffe6f5c A4 : 0x00000001 A5 : 0xffffffff A6 : 0x3fabad7c A7 : 0xff000000 A8 : 0x00000000 A9 : 0x3ffe9c50 A10 : 0x00000000 A11 : 0x3ffe6f5c A12 : 0x00000001 A13 : 0x0000000a A14 : 0x00000037 A15 : 0x00000057 SAR : 0x00000018 EXCCAUSE: 0x0000001d EXCVADDR: 0x00000000 LBEG : 0x4008b179 LEND : 0x4008b19b LCOUNT : 0xffffffff ELF file SHA256: 94a8e191baae33a5 Backtrace: 0x4022438b:0x3ffe9c70 0x402245ca:0x3ffe9c90 0x40132f93:0x3ffe9cc0 0x40132e51:0x3ffe9d10 0x40133609:0x3ffe9d40 0x402e7472:0x3ffe9d70 0x4010e229:0x3ffe9d90 0x4010fbd5:0x3ffe9dd0 0x40110015:0x3ffe9e00 0x401102de:0x3ffe9e70 0x4010c51a:0x3ffe9ed0 0x400f5a4f:0x3ffe9ef0 0x400f5afd:0x3ffe9f40 Rebooting... 0x4022438b is in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_S_copy(char*, char const*, unsigned int) (/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/build/build-cc-gcc-final/xtensa-esp32-elf/esp32-psram/libstdc++-v3/include/bits/char_traits.h:243). 0x402245ca is in std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::reserve(unsigned int) (/builds/idf/crosstool-NG/.build/xtensa-esp32-elf/build/build-cc-gcc-final/xtensa-esp32-elf/esp32-psram/libstdc++-v3/include/bits/basic_string.tcc:298). 0x40132f93 is in OvmsSyncHttpClient::ConnectionHeaders(mg_connection*) (/home/balzer/esp/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_http/src/ovms_http.cpp:381). 376 else 377 { 378 if (header.compare(0,15,"Content-Length:") == 0) 379 { 380 m_bodysize = atoi(header.substr(15).c_str()); *381 m_body.reserve(m_bodysize+1);* 382 } 383 else if (header.compare(0,5,"HTTP/") == 0) 384 { 385 size_t space = header.find(' '); 0x40132e51 is in OvmsSyncHttpClient::ConnectionData(mg_connection*, unsigned char*, unsigned int) (/home/balzer/esp/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_http/src/ovms_http.cpp:316). 311 data += len; 312 consumed += len; 313 len = 0; 314 } 315 316 ConnectionHeaders(nc); 317 } 318 319 if (! m_inheaders) 320 { 0x40133609 is in OvmsSyncHttpClient::MongooseCallback(mg_connection*, int, void*) (/home/balzer/esp/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_http/src/ovms_http.cpp:124). 119 m_mgconn = NULL; 120 } 121 break; 122 123 case MG_EV_RECV: 124 mbuf_remove(&nc->recv_mbuf, ConnectionData(nc,(uint8_t*)nc->recv_mbuf.buf, nc->recv_mbuf.len)); 125 break; 126 127 default: 128 break; Can we switch back to using the old async client? Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

2 6

Readthedocs broken
by Mark Webb-Johnson 15 Nov '21

15 Nov '21

The readthedocs service we use appears to be broken at the moment. Issue reported here (and in a dozen or more other places): https://github.com/readthedocs/readthedocs.org/issues/8616#issuecomment-955… <https://github.com/readthedocs/readthedocs.org/issues/8616#issuecomment-955…> There is a workaround, to pin the docutils<0.18 version, but I think better to just wait for readthedocs to fix the issue as it is affecting so many builds. If they haven’t fixed it in the next few days then I’ll try to apply the workaround. Regards, Mark.

3 3

OVMS v3.3 Certified
by Mark Webb-Johnson 09 Nov '21

09 Nov '21

Guys, I am overjoyed to be able to report that we sailed through certification, with no changes required to our design. CE, and FCC. Bluetooth, wifi, GPS, 2G, 3G, 4G, ROHS, and EMC. It will take another couple of weeks to get the paperwork through, but the hurdle seems over and hardware design is finalised. We can now move on to production (which is helpful, as almost everywhere is running very low on OVMS stock). The pressure is now on finalising the v3.3 firmware to match. Regards, Mark.

2 2

Update from master
by Shane ＠ Kilve Engineering 02 Nov '21

02 Nov '21

Hi all I ve just done an update from ovms master and gone to do a build and got given lots of options to select? Now my builds won’t connect to v2 server Regards Shane shane@Shanes-MacBook-Pro OVMS.V3 % make Toolchain path: /Users/shane/.espressif/tools/xtensa-esp32-elf/1.22.0-97-gc752ad5-5.2.0/xtensa-esp32-elf/bin/xtensa-esp32-elf-gcc Toolchain version: crosstool-ng-1.22.0-97-gc752ad5 Compiler version: 5.2.0 GENCONFIG * * Restart config... * * * System Options * Stack size for command execution (OVMS_SYS_COMMAND_STACK_SIZE) [6144] 6144 Task priority for command execution (OVMS_SYS_COMMAND_PRIORITY) [5] (NEW) Queue size for file logging (OVMS_LOGFILE_QUEUE_SIZE) [100] 100 Task priority for file logging (OVMS_LOGFILE_TASK_PRIORITY) [2] 2 * * Include the GPL licensed MONGOOSE networking library (web server, etc) * Include the GPL licensed MONGOOSE networking library (web server, etc) (OVMS_SC_GPL_MONGOOSE) [Y/n/?] y Enable MONGOOSE filesystem support (MG_ENABLE_FILESYSTEM) [Y/n/?] y Enable MONGOOSE directory listing support (MG_ENABLE_DIRECTORY_LISTING) [Y/n/?] y Enable MONGOOSE SSL/TLS support (MG_ENABLE_SSL) [Y/n/?] y Select the MONGOOSE SSL/TLS library to use > 1. mbedTLS (MG_SSL_IF_MBEDTLS) (NEW) 2. WolfSSL (MG_SSL_IF_WOLFSSL) (NEW) choice[1-2?]: 2 Enable MONGOOSE debug logging (MG_ENABLE_DEBUG) [N/y/?] n * * Library Support * Select the OVMS javascript library to use 1. No javascript support (OVMS_SC_JAVASCRIPT_NONE) > 2. Use the MIT licensed DUKTAPE library (OVMS_SC_JAVASCRIPT_DUKTAPE) choice[1-2?]: 2 Include the GPL licensed WOLFSSH and WOLFSSL libraries (ssh server) (OVMS_SC_GPL_WOLF) [Y/n/?] y Include ZIP archive support (OVMS_SC_ZIP) [Y/n/?] y JavaScript (DukTape) task stack size (OVMS_SC_JAVASCRIPT_DUKTAPE_STACK) [12288] 12288 JavaScript (DukTape) task queue size (OVMS_SC_JAVASCRIPT_DUKTAPE_QUEUE_SIZE) [40] 40 JavaScript (DukTape) task priority (OVMS_SC_JAVASCRIPT_DUKTAPE_PRIORITY) [3] 3 Enable Javascript (Duktape) dedicated heap memory management (OVMS_SC_JAVASCRIPT_DUKTAPE_HEAP_UMM) [Y/n/?] (NEW) Javascript/Duktape default size of dedicated memory chunk (KB) (OVMS_SC_JAVASCRIPT_DUKTAPE_HEAP_UMM_DEFAULTSIZE) [512] (NEW) Javascript/Duktape size of a memory block (bytes) (OVMS_SC_JAVASCRIPT_DUKTAPE_HEAP_UMM_BLOCKSIZE) [32] (NEW) # # configuration written to /Users/shane/Open-Vehicle-Monitoring-System-3-MGEV/vehicle/OVMS.V3/sdkconfig # App "ovms3" version: 3.2.014-1137-g8bc1c599-dirty Python requirements from /Users/shane/esp-idf/requirements.txt are satisfied. Building partitions from /Users/shane/Open-Vehicle-Monitoring-System-3-MGEV/vehicle/OVMS.V3/partitions.csv... CC build/bootloader/bootloader_support/src/bootloader_clock.o CC build/bootloader/bootloader_support/src/bootloader_common.o CC build/bootloader/bootloader_support/src/bootloader_flash.o CC build/bootloader/bootloader_support/src/bootloader_flash_config.o CC build/bootloader/bootloader_support/src/bootloader_init.o

2 1