January 2018 - OvmsDev - Open Vehicles

OVMS v3 CAN testing
by Mark Webb-Johnson 14 Jan '18

14 Jan '18

FYI: this is what I use for CAN bus testing: DB9 wired with all three -L lines together, and all three -H lines together, then a 120R termination resistor across CAN1. I also have external 12V power wired to a socket, but that is optional. With this in place, a TX and CAN1 produces RX on CAN2 and CAN3, etc. Regards, Mark

1 0

HUD Demo
by Greg D. 13 Jan '18

13 Jan '18

Hi folks, Our first sunny day here in quite a while, so I thought it would be a good time to take a quick video of the obd2ecu task (OBDII ECU translator) driving a HUD display. This is a rough draft - I'll make a more polished video when my kids visit in a few weeks and can help with the camera work. https://www.youtube.com/watch?v=AEyjckZBgOs Enjoy! Greg

2 2

Playing with SPI RAM
by Mark Webb-Johnson 13 Jan '18

13 Jan '18

Before: OVMS > module memory ============================ Free 8-bit 4291676/4507468, 32-bit 1608/16760, blocks dumped = 0 task=no task total= 38116 0 0 0 change= +38116 +0 +0 +0 task=esp_timer total= 49628 0 644 0 change= +49628 +0 +644 +0 task=main total= 9868 0 0 26924 change= +9868 +0 +0 +26924 task=ipc0 total= 11096 0 0 0 change= +11096 +0 +0 +0 task=Housekeeping total= 44032 0 0 12 change= +44032 +0 +0 +12 task=ipc1 total= 12 0 0 0 change= +12 +0 +0 +0 task=Tmr Svc total= 16 0 0 0 change= +16 +0 +0 +0 task=tiT total= 0 0 0 128 change= +0 +0 +0 +128 task=AsyncConsole total= 20 0 14404 12000 change= +20 +0 +14404 +12000 ============================ The change: class OvmsCommand { public: void* operator new(size_t sz) { return heap_caps_malloc(sz, MALLOC_CAP_SPIRAM); } void operator delete (void* ptr) { return free(ptr); } After: OVMS > module memory ============================ Free 8-bit 4291676/4507468, 32-bit 1608/16760, blocks dumped = 0 task=no task total= 38116 0 0 0 change= +38116 +0 +0 +0 task=esp_timer total= 28708 0 644 20916 change= +28708 +0 +644 +20916 task=main total= 9868 0 0 26924 change= +9868 +0 +0 +26924 task=ipc0 total= 11096 0 0 0 change= +11096 +0 +0 +0 task=Housekeeping total= 37984 0 0 6060 change= +37984 +0 +0 +6060 task=ipc1 total= 12 0 0 0 change= +12 +0 +0 +0 task=Tmr Svc total= 16 0 0 0 change= +16 +0 +0 +0 task=tiT total= 0 0 0 128 change= +0 +0 +0 +128 task=AsyncConsole total= 12020 0 14404 0 change= +12020 +0 +14404 +0 ============================ So, simply moving OvmsCommand objects to SPI RAM saves us about 26KB of internal RAM. Our goal would be to move as much of our infrequently accessed stuff as possible to SPI RAM. This would free up as much internal ram as possible for things like stacks, DMA, etc. Here are the restrictions on SPI RAM that Espressif point out: The use of external RAM has a few restrictions: When disabling flash cache (for example, because the flash is being written to), the external RAM also becomes inaccessible; any reads from or writes to it will lead to an illegal cache access exception. This is also the reason that ESP-IDF will never allocate a tasks stack in external RAM. External RAM cannot be used as a place to store DMA transaction descriptors or as a buffer for a DMA transfer to read from or write into. Any buffers that will be used in combination with DMA must be allocated using heap_caps_malloc(size, MALLOC_CAP_DMA) (and can be freed using a standard free() call.) External RAM uses the same cache region as the external flash. This means that often accessed variables in external RAM can be read and modified almost as quickly as in internal ram. However, when accessing large chunks of data (>32K), the cache can be insufficient and speeds will fall back to the access speed of the external RAM. Moreover, accessing large chunks of data can ‘push out’ cached flash, possibly making execution of code afterwards slower. External RAM cannot be used as task stack memory; because of this, xTaskCreate and similar functions will always allocate internal memory for stack and task TCBs and xTaskCreateStatic-type functions will check if the buffers passed are internal. However, for tasks not calling on code in ROM in any way, directly or indirectly, the menuconfig option SPIRAM_ALLOW_STACK_EXTERNAL_MEMORY <http://esp-idf.readthedocs.io/en/latest/api-reference/kconfig.html#config-s…> will eliminate the check in xTaskCreateStatic, allowing task stack in external RAM. Using this is not advised, however. Because there are a fair few situations that have a specific need for internal memory, but it is also possible to use malloc() to exhaust internal memory, there is a pool reserved specifically for requests that cannot be resolved from external memory; allocating task stack, DMA buffers and memory that stays accessible when cache is disabled is drawn from this pool. The size of this pool is configurable in menuconfig. I’m not having much luck trying to globally override the new() and delete() memory allocators, so I’m now thinking of making a base class with new and delete operators, plus some other utility functions to make spi ram allocation easier. Then whenever we want to make one of our objects allocatable from spiram we simply derive from that base class. That class could pickup on the menuconfig hardware version (3.0 WROOM-32 vs 3.1 WROVER) and turn on/off SPIRAM appropriately. Here is how Espressif do it: IRAM_ATTR void *heap_caps_malloc_default( size_t size ) { if (malloc_alwaysinternal_limit==MALLOC_DISABLE_EXTERNAL_ALLOCS) { return heap_caps_malloc( size, MALLOC_CAP_DEFAULT | MALLOC_CAP_INTERNAL); } else { void *r; if (size <= malloc_alwaysinternal_limit) { r=heap_caps_malloc( size, MALLOC_CAP_DEFAULT | MALLOC_CAP_INTERNAL ); } else { r=heap_caps_malloc( size, MALLOC_CAP_DEFAULT | MALLOC_CAP_SPIRAM ); } if (r==NULL) { //try again while being less picky r=heap_caps_malloc( size, MALLOC_CAP_DEFAULT ); } return r; } } We want to do the opposite - try to allocate from SPIRAM if it is available. There is a heap_caps_malloc_prefer that could do it for us. Thoughts? Regards, Mark.

2 2

Stack sizes
by Mark Webb-Johnson 13 Jan '18

13 Jan '18

It seems that we are continuously having to increase stack sizes. So, I went on a hunt to try to find out why… I put a abort() in the metrics_list() function. Spun up a wifi connection, an ovms_server_v2 connection, and then 'cmd.pl 7 'metric list’. Here are the stack frame details: (gdb) bt #0 0x40088dac in invoke_abort () at /Users/mark/esp/esp-idf/components/esp32/./panic.c:125 #1 0x40088e7a in abort () at /Users/mark/esp/esp-idf/components/esp32/./panic.c:134 #2 0x40123765 in metrics_list (verbosity=1024, writer=0x3fff6b94, cmd=0x3ffb6584, argc=0, argv=0x0) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_metrics.cpp:49 #3 0x4011e1a9 in OvmsCommand::Execute (this=0x3ffb6584, verbosity=1024, writer=0x3fff6b94, argc=0, argv=0x0) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_command.cpp:257 #4 0x4011e29d in OvmsCommand::Execute (this=0x3ffb64f0, verbosity=1024, writer=0x3fff6b94, argc=1, argv=0x3fff54d4) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_command.cpp:302 #5 0x4011e290 in OvmsCommand::Execute (this=0x3ffc3cc4 <MyCommandApp+4>, verbosity=1024, writer=0x3fff6b94, argc=2, argv=0x3fff54d4) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_command.cpp:298 #6 0x4011e2c4 in OvmsCommandApp::Execute (this=0x3ffc3cc0 <MyCommandApp>, verbosity=1024, writer=0x3fff6b94, argc=2, argv=0x3fff54d0) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_command.cpp:507 #7 0x401292a8 in Execute (rl=0x3fff6b9c, argc=2, argv=0x3fff54d0) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_shell.cpp:47 #8 0x400db2cd in new_line_handler (pThis=0x3fff6b9c) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/microrl/./microrl.c:626 #9 0x400db333 in microrl_insert_char (pThis=0x3fff6b9c, ch=10) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/microrl/./microrl.c:674 #10 0x401292f7 in OvmsShell::ProcessChar (this=0x3fff6b94, c=10 '\n') at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_shell.cpp:62 #11 0x400f57d8 in OvmsServerV2::ProcessCommand (this=0x3fff433c, payload=<optimized out>) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_server_v2/src/ovms_server_v2.cpp:411 #12 0x400f9b54 in OvmsServerV2::ProcessServerMsg (this=0x3fff433c) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_server_v2/src/ovms_server_v2.cpp:336 #13 0x400fa263 in OvmsServerV2::ServerTask (this=0x3fff433c) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_server_v2/src/ovms_server_v2.cpp:244 #14 0x400f4325 in OvmsServer_task (pvParameters=0x3fff433c) at /Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_server/./ovms_server.cpp:43 Stack level 0, frame at 0x3fff53f0: pc = 0x40088dac in invoke_abort (/Users/mark/esp/esp-idf/components/esp32/./panic.c:125); saved pc = 0x40088e7a called by frame at 0x3fff5410 source language c. Arglist at 0x3fff53d0, args: Locals at 0x3fff53d0, Previous frame's sp is 0x3fff53f0 Saved registers: ar56 at 0x3fff53c0, ar57 at 0x3fff53c4, ar58 at 0x3fff53c8, ar59 at 0x3fff53cc, ar60 at 0x3fff53f0, ar61 at 0x3fff53f4, ar62 at 0x3fff53f8, ar63 at 0x3fff53fc, a0 at 0x3fff53c0, a2 at 0x3fff53c8, a3 at 0x3fff53cc, a4 at 0x3fff53f0, a5 at 0x3fff53f4, a6 at 0x3fff53f8, a7 at 0x3fff53fc Stack level 1, frame at 0x3fff5410: pc = 0x40088e7a in abort (/Users/mark/esp/esp-idf/components/esp32/./panic.c:134); saved pc = 0x40123765 called by frame at 0x3fff5430, caller of frame at 0x3fff53f0 source language c. Arglist at 0x3fff53f0, args: Locals at 0x3fff53f0, Previous frame's sp is 0x3fff5410 Saved registers: ar48 at 0x3fff53e0, ar49 at 0x3fff53e4, ar50 at 0x3fff53e8, ar51 at 0x3fff53ec, ar52 at 0x3fff5410, ar53 at 0x3fff5414, ar54 at 0x3fff5418, ar55 at 0x3fff541c, a0 at 0x3fff53e0, a2 at 0x3fff53e8, a3 at 0x3fff53ec, a4 at 0x3fff5410, a5 at 0x3fff5414, a6 at 0x3fff5418, a7 at 0x3fff541c Stack level 2, frame at 0x3fff5430: pc = 0x40123765 in metrics_list (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_metrics.cpp:49); saved pc = 0x4011e1a9 called by frame at 0x3fff5450, caller of frame at 0x3fff5410 source language c++. Arglist at 0x3fff5410, args: verbosity=1024, writer=0x3fff6b94, cmd=0x3ffb6584, argc=0, argv=0x0 Locals at 0x3fff5410, Previous frame's sp is 0x3fff5430 Saved registers: ar40 at 0x3fff5400, ar41 at 0x3fff5404, ar42 at 0x3fff5408, ar43 at 0x3fff540c, ar44 at 0x3fff5430, ar45 at 0x3fff5434, ar46 at 0x3fff5438, ar47 at 0x3fff543c, a0 at 0x3fff5400, a2 at 0x3fff5408, a3 at 0x3fff540c, a4 at 0x3fff5430, a5 at 0x3fff5434, a6 at 0x3fff5438, a7 at 0x3fff543c Stack level 3, frame at 0x3fff5450: pc = 0x4011e1a9 in OvmsCommand::Execute (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_command.cpp:257); saved pc = 0x4011e29d called by frame at 0x3fff5470, caller of frame at 0x3fff5430 source language c++. Arglist at 0x3fff5430, args: this=0x3ffb6584, verbosity=1024, writer=0x3fff6b94, argc=0, argv=0x0 Locals at 0x3fff5430, Previous frame's sp is 0x3fff5450 Saved registers: ar32 at 0x3fff5420, ar33 at 0x3fff5424, ar34 at 0x3fff5428, ar35 at 0x3fff542c, ar36 at 0x3fff5450, ar37 at 0x3fff5454, ar38 at 0x3fff5458, ar39 at 0x3fff545c, a0 at 0x3fff5420, a2 at 0x3fff5428, a3 at 0x3fff542c, a4 at 0x3fff5450, a5 at 0x3fff5454, a6 at 0x3fff5458, a7 at 0x3fff545c Stack level 4, frame at 0x3fff5470: pc = 0x4011e29d in OvmsCommand::Execute (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_command.cpp:302); saved pc = 0x4011e290 called by frame at 0x3fff5490, caller of frame at 0x3fff5450 source language c++. Arglist at 0x3fff5450, args: this=0x3ffb64f0, verbosity=1024, writer=0x3fff6b94, argc=1, argv=0x3fff54d4 Locals at 0x3fff5450, Previous frame's sp is 0x3fff5470 Saved registers: ar24 at 0x3fff5440, ar25 at 0x3fff5444, ar26 at 0x3fff5448, ar27 at 0x3fff544c, ar28 at 0x3fff5470, ar29 at 0x3fff5474, ar30 at 0x3fff5478, ar31 at 0x3fff547c, a0 at 0x3fff5440, a2 at 0x3fff5448, a3 at 0x3fff544c, a4 at 0x3fff5470, a5 at 0x3fff5474, a6 at 0x3fff5478, a7 at 0x3fff547c Stack level 5, frame at 0x3fff5490: pc = 0x4011e290 in OvmsCommand::Execute (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_command.cpp:298); saved pc = 0x4011e2c4 called by frame at 0x3fff54b0, caller of frame at 0x3fff5470 source language c++. Arglist at 0x3fff5470, args: this=0x3ffc3cc4 <MyCommandApp+4>, verbosity=1024, writer=0x3fff6b94, argc=2, argv=0x3fff54d4 Locals at 0x3fff5470, Previous frame's sp is 0x3fff5490 Saved registers: ar16 at 0x3fff5460, ar17 at 0x3fff5464, ar18 at 0x3fff5468, ar19 at 0x3fff546c, ar20 at 0x3fff5490, ar21 at 0x3fff5494, ar22 at 0x3fff5498, ar23 at 0x3fff549c, a0 at 0x3fff5460, a2 at 0x3fff5468, a3 at 0x3fff546c, a4 at 0x3fff5490, a5 at 0x3fff5494, a6 at 0x3fff5498, a7 at 0x3fff549c Stack level 6, frame at 0x3fff54b0: pc = 0x4011e2c4 in OvmsCommandApp::Execute (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_command.cpp:507); saved pc = 0x401292a8 called by frame at 0x3fff54d0, caller of frame at 0x3fff5490 source language c++. Arglist at 0x3fff5490, args: this=0x3ffc3cc0 <MyCommandApp>, verbosity=1024, writer=0x3fff6b94, argc=2, argv=0x3fff54d0 Locals at 0x3fff5490, Previous frame's sp is 0x3fff54b0 Saved registers: ar8 at 0x3fff5480, ar9 at 0x3fff5484, ar10 at 0x3fff5488, ar11 at 0x3fff548c, ar12 at 0x3fff54b0, ar13 at 0x3fff54b4, ar14 at 0x3fff54b8, ar15 at 0x3fff54bc, a0 at 0x3fff5480, a2 at 0x3fff5488, a3 at 0x3fff548c, a4 at 0x3fff54b0, a5 at 0x3fff54b4, a6 at 0x3fff54b8, a7 at 0x3fff54bc Stack level 7, frame at 0x3fff54d0: pc = 0x401292a8 in Execute (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_shell.cpp:47); saved pc = 0x400db2cd called by frame at 0x3fff5530, caller of frame at 0x3fff54b0 source language c++. Arglist at 0x3fff54b0, args: rl=0x3fff6b9c, argc=2, argv=0x3fff54d0 Locals at 0x3fff54b0, Previous frame's sp is 0x3fff54d0 Saved registers: ar0 at 0x3fff54a0, ar1 at 0x3fff54a4, ar2 at 0x3fff54a8, ar3 at 0x3fff54ac, ar4 at 0x3fff5510, ar5 at 0x3fff5514, ar6 at 0x3fff5518, ar7 at 0x3fff551c, a0 at 0x3fff54a0, a2 at 0x3fff54a8, a3 at 0x3fff54ac, a4 at 0x3fff5510, a5 at 0x3fff5514, a6 at 0x3fff5518, a7 at 0x3fff551c Stack level 8, frame at 0x3fff5530: pc = 0x400db2cd in new_line_handler (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/microrl/./microrl.c:626); saved pc = 0x400db333 called by frame at 0x3fff5560, caller of frame at 0x3fff54d0 source language c. Arglist at 0x3fff54d0, args: pThis=0x3fff6b9c Locals at 0x3fff54d0, Previous frame's sp is 0x3fff5530 Saved registers: ar56 at 0x3fff54c0, ar57 at 0x3fff54c4, ar58 at 0x3fff54c8, ar59 at 0x3fff54cc, ar60 at 0x3fff5540, ar61 at 0x3fff5544, ar62 at 0x3fff5548, ar63 at 0x3fff554c, a0 at 0x3fff54c0, a2 at 0x3fff54c8, a3 at 0x3fff54cc, a4 at 0x3fff5540, a5 at 0x3fff5544, a6 at 0x3fff5548, a7 at 0x3fff554c Stack level 9, frame at 0x3fff5560: pc = 0x400db333 in microrl_insert_char (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/microrl/./microrl.c:674); saved pc = 0x401292f7 called by frame at 0x3fff5580, caller of frame at 0x3fff5530 source language c. Arglist at 0x3fff5530, args: pThis=0x3fff6b9c, ch=10 Locals at 0x3fff5530, Previous frame's sp is 0x3fff5560 Saved registers: ar48 at 0x3fff5520, ar49 at 0x3fff5524, ar50 at 0x3fff5528, ar51 at 0x3fff552c, ar52 at 0x3fff5560, ar53 at 0x3fff5564, ar54 at 0x3fff5568, ar55 at 0x3fff556c, a0 at 0x3fff5520, a2 at 0x3fff5528, a3 at 0x3fff552c, a4 at 0x3fff5560, a5 at 0x3fff5564, a6 at 0x3fff5568, a7 at 0x3fff556c Stack level 10, frame at 0x3fff5580: pc = 0x401292f7 in OvmsShell::ProcessChar (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_shell.cpp:62); saved pc = 0x400f57d8 called by frame at 0x3fff5e20, caller of frame at 0x3fff5560 source language c++. Arglist at 0x3fff5560, args: this=0x3fff6b94, c=10 '\n' Locals at 0x3fff5560, Previous frame's sp is 0x3fff5580 Saved registers: ar40 at 0x3fff5550, ar41 at 0x3fff5554, ar42 at 0x3fff5558, ar43 at 0x3fff555c, ar44 at 0x3fff5e00, ar45 at 0x3fff5e04, ar46 at 0x3fff5e08, ar47 at 0x3fff5e0c, a0 at 0x3fff5550, a2 at 0x3fff5558, a3 at 0x3fff555c, a4 at 0x3fff5e00, a5 at 0x3fff5e04, a6 at 0x3fff5e08, a7 at 0x3fff5e0c Stack level 11, frame at 0x3fff5e20: pc = 0x400f57d8 in OvmsServerV2::ProcessCommand (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_server_v2/src/ovms_server_v2.cpp:411); saved pc = 0x400f9b54 called by frame at 0x3fff5ee0, caller of frame at 0x3fff5580 source language c++. Arglist at 0x3fff5580, args: this=0x3fff433c, payload=<optimized out> Locals at 0x3fff5580, Previous frame's sp is 0x3fff5e20 Saved registers: ar32 at 0x3fff5570, ar33 at 0x3fff5574, ar34 at 0x3fff5578, ar35 at 0x3fff557c, ar36 at 0x3fff5ec0, ar37 at 0x3fff5ec4, ar38 at 0x3fff5ec8, ar39 at 0x3fff5ecc, a0 at 0x3fff5570, a2 at 0x3fff5578, a3 at 0x3fff557c, a4 at 0x3fff5ec0, a5 at 0x3fff5ec4, a6 at 0x3fff5ec8, a7 at 0x3fff5ecc Stack level 12, frame at 0x3fff5ee0: pc = 0x400f9b54 in OvmsServerV2::ProcessServerMsg (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_server_v2/src/ovms_server_v2.cpp:336); saved pc = 0x400fa263 called by frame at 0x3fff5f80, caller of frame at 0x3fff5e20 source language c++. Arglist at 0x3fff5e40, args: this=0x3fff433c Locals at 0x3fff5e40, Previous frame's sp is 0x3fff5ee0 Saved registers: ar24 at 0x3fff5e10, ar25 at 0x3fff5e14, ar26 at 0x3fff5e18, ar27 at 0x3fff5e1c, ar28 at 0x3fff5f60, ar29 at 0x3fff5f64, ar30 at 0x3fff5f68, ar31 at 0x3fff5f6c, a0 at 0x3fff5e10, a2 at 0x3fff5e18, a3 at 0x3fff5e1c, a4 at 0x3fff5f60, a5 at 0x3fff5f64, a6 at 0x3fff5f68, a7 at 0x3fff5f6c Stack level 13, frame at 0x3fff5f80: pc = 0x400fa263 in OvmsServerV2::ServerTask (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_server_v2/src/ovms_server_v2.cpp:244); saved pc = 0x400f4325 called by frame at 0x0, caller of frame at 0x3fff5ee0 source language c++. Arglist at 0x3fff5ee0, args: this=0x3fff433c Locals at 0x3fff5ee0, Previous frame's sp is 0x3fff5f80 Saved registers: ar16 at 0x3fff5ed0, ar17 at 0x3fff5ed4, ar18 at 0x3fff5ed8, ar19 at 0x3fff5edc, ar20 at 0x3fff5f80, ar21 at 0x3fff5f84, ar22 at 0x3fff5f88, ar23 at 0x3fff5f8c, a0 at 0x3fff5ed0, a2 at 0x3fff5ed8, a3 at 0x3fff5edc, a4 at 0x3fff5f80, a5 at 0x3fff5f84, a6 at 0x3fff5f88, a7 at 0x3fff5f8c Stack level 14, frame at 0x0: pc = 0x400f4325 in OvmsServer_task (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_server/./ovms_server.cpp:43); saved pc = 0x40000000 Outermost frame: outermost caller of frame at 0x3fff5f80 source language c++. Arglist at 0x3fff5f80, args: pvParameters=0x3fff433c Locals at 0x3fff5f80, Previous frame's sp is 0x0 Saved registers: ar16 at 0x3fff5f70, ar17 at 0x3fff5f74, ar18 at 0x3fff5f78, ar19 at 0x3fff5f7c, a0 at 0x3fff5f70, a2 at 0x3fff5f78, a3 at 0x3fff5f7c Here are the stack frame pointers: OvmsServer_task Stack level 14, frame at 0x0: OvmsServerV2::ServerTask Stack level 13, frame at 0x3fff5f80: 160 bytes OvmsServerV2::ProcessServerMsg Stack level 12, frame at 0x3fff5ee0: 192 bytes OvmsServerV2::ProcessCommand Stack level 11, frame at 0x3fff5e20: 2208 bytes OvmsShell::ProcessChar Stack level 10, frame at 0x3fff5580: 32 bytes microrl_insert_char Stack level 9, frame at 0x3fff5560: 48 bytes new_line_handler Stack level 8, frame at 0x3fff5530: 92 bytes Execute Stack level 7, frame at 0x3fff54d0: 32 bytes OvmsCommandApp::ExecuteStack level 6, frame at 0x3fff54b0: 32 bytes OvmsCommand::Execute Stack level 5, frame at 0x3fff5490: 32 bytes OvmsCommand::Execute Stack level 4, frame at 0x3fff5470: 32 bytes OvmsCommand::Execute Stack level 3, frame at 0x3fff5450: 32 bytes metrics_list Stack level 2, frame at 0x3fff5430: 32 bytes abort Stack level 1, frame at 0x3fff5410: 32 bytes invoke_abort Stack level 0, frame at 0x3fff53f0 That frame #11 stands out like a sore thumb. Here are the details: (gdb) info frame Stack level 11, frame at 0x3fff5e20: pc = 0x400f57d8 in OvmsServerV2::ProcessCommand (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_server_v2/src/ovms_server_v2.cpp:411); saved pc = 0x400f9b54 called by frame at 0x3fff5ee0, caller of frame at 0x3fff5580 source language c++. Arglist at 0x3fff5580, args: this=0x3fff433c, payload=<optimized out> Locals at 0x3fff5580, Previous frame's sp is 0x3fff5e20 Saved registers: ar32 at 0x3fff5570, ar33 at 0x3fff5574, ar34 at 0x3fff5578, ar35 at 0x3fff557c, ar36 at 0x3fff5ec0, ar37 at 0x3fff5ec4, ar38 at 0x3fff5ec8, ar39 at 0x3fff5ecc, a0 at 0x3fff5570, a2 at 0x3fff5578, a3 at 0x3fff557c, a4 at 0x3fff5ec0, a5 at 0x3fff5ec4, a6 at 0x3fff5ec8, a7 at 0x3fff5ecc (gdb) info locals bs = 0x3fff6b94 val = {static npos = <optimized out>, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0x9c85f1ef '\377' <repeats 200 times>...}, _M_string_length = 2512534878, {_M_local_buf = "\377\377\377\377\063\234\351\347W\243\303*\242\004\000\017", _M_allocated_capacity = 4294967295}} command = <optimized out> sep = 1 vehicle = 0x0 buffer = {<std::basic_ostream<char, std::char_traits<char> >> = {<std::basic_ios<char, std::char_traits<char> >> = {<std::ios_base> = { _vptr$ios_base = 0x3f4168bc <vtable for std::__cxx11::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >+32>, static boolalpha = std::_S_boolalpha, static dec = std::_S_dec, static fixed = std::_S_fixed, static hex = std::_S_hex, static internal = std::_S_internal, static left = std::_S_left, static oct = std::_S_oct, static right = std::_S_right, static scientific = std::_S_scientific, static showbase = std::_S_showbase, static showpoint = std::_S_showpoint, static showpos = std::_S_showpos, static skipws = std::_S_skipws, static unitbuf = std::_S_unitbuf, static uppercase = std::_S_uppercase, static adjustfield = std::_S_adjustfield, static basefield = std::_S_basefield, static floatfield = std::_S_floatfield, static badbit = std::_S_badbit, static eofbit = std::_S_eofbit, static failbit = std::_S_failbit, static goodbit = std::_S_goodbit, static app = std::_S_app, static ate = std::_S_ate, static binary = std::_S_bin, static in = std::_S_in, static out = std::_S_out, static trunc = std::_S_trunc, static beg = std::_S_beg, static cur = std::_S_cur, static end = std::_S_end, _M_precision = 6, _M_width = 0, _M_flags = 4098, _M_exception = std::_S_goodbit, _M_streambuf_state = std::_S_goodbit, _M_callbacks = 0x0, _M_word_zero = {_M_pword = 0x0, _M_iword = 0}, _M_local_word = {{_M_pword = 0x0, _M_iword = 0}, {_M_pword = 0x0, _M_iword = 0}, {_M_pword = 0x0, _M_iword = 0}, {_M_pword = 0x0, _M_iword = 0}, { _M_pword = 0x0, _M_iword = 0}, {_M_pword = 0x0, _M_iword = 0}, {_M_pword = 0x0, _M_iword = 0}, {_M_pword = 0x0, _M_iword = 0}}, _M_word_size = 8, _M_word = 0x3fff5c84, _M_ios_locale = { static none = 0, static ctype = 1, static numeric = 2, static collate = 4, static time = 8, static monetary = 16, static messages = 32, static all = 63, _M_impl = 0x3ffc4c2c <(anonymous namespace)::c_locale_impl>, static _S_classic = 0x3ffc4c2c <(anonymous namespace)::c_locale_impl>, static _S_global = 0x3ffc4c2c <(anonymous namespace)::c_locale_impl>, static _S_categories = <optimized out>, static _S_twinned_facets = 0x3f415488 <std::locale::_S_twinned_facets>}}, _M_tie = 0x0, _M_fill = 0 '\000', _M_fill_init = false, _M_streambuf = 0x3fff5c24, _M_ctype = 0x3ffc4878 <(anonymous namespace)::ctype_c>, _M_num_put = 0x3ffc4850 <(anonymous namespace)::num_put_c>, _M_num_get = 0x3ffc4858 <(anonymous namespace)::num_get_c>}, _vptr$basic_ostream = 0x3f4168a8 <vtable for std::__cxx11::basic_ostringstream<char, std::char_traits<char>, std::allocator<char> >+12>}, _M_stringbuf = {<std::basic_streambuf<char, std::char_traits<char> >> = { _vptr$basic_streambuf = 0x3f4167cc <vtable for std::__cxx11::basic_stringbuf<char, std::char_traits<char>, std::allocator<char> >+8>, _M_in_beg = 0x0, _M_in_cur = 0x0, _M_in_end = 0x0, _M_out_beg = 0x0, _M_out_cur = 0x0, _M_out_end = 0x0, _M_buf_locale = {static none = 0, static ctype = 1, static numeric = 2, static collate = 4, static time = 8, static monetary = 16, static messages = 32, static all = 63, _M_impl = 0x3ffc4c2c <(anonymous namespace)::c_locale_impl>, static _S_classic = 0x3ffc4c2c <(anonymous namespace)::c_locale_impl>, static _S_global = 0x3ffc4c2c <(anonymous namespace)::c_locale_impl>, static _S_categories = <optimized out>, static _S_twinned_facets = 0x3f415488 <std::locale::_S_twinned_facets>}}, _M_mode = std::_S_out, _M_string = {static npos = <optimized out>, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0x3fff5c50 ""}, _M_string_length = 0, {_M_local_buf = "\000\377\377\377y\031\b@\000\000\000\000\250\177\b@", _M_allocated_capacity = 4294967040}}}} (gdb) info args this = 0x3fff433c payload = <optimized out> Also frame #12: (gdb) info frame Stack level 12, frame at 0x3fff5ee0: pc = 0x400f9b54 in OvmsServerV2::ProcessServerMsg (/Users/mark/Documents/ovms/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/ovms_server_v2/src/ovms_server_v2.cpp:336); saved pc = 0x400fa263 called by frame at 0x3fff5f80, caller of frame at 0x3fff5e20 source language c++. Arglist at 0x3fff5e40, args: this=0x3fff433c Locals at 0x3fff5e40, Previous frame's sp is 0x3fff5ee0 Saved registers: ar24 at 0x3fff5e10, ar25 at 0x3fff5e14, ar26 at 0x3fff5e18, ar27 at 0x3fff5e1c, ar28 at 0x3fff5f60, ar29 at 0x3fff5f64, ar30 at 0x3fff5f68, ar31 at 0x3fff5f6c, a0 at 0x3fff5e10, a2 at 0x3fff5e18, a3 at 0x3fff5e1c, a4 at 0x3fff5f60, a5 at 0x3fff5f64, a6 at 0x3fff5f68, a7 at 0x3fff5f6c (gdb) info locals line = {static npos = <optimized out>, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0x3fff68a8 "MP-0 C7,metric list"}, _M_string_length = 19, {_M_local_buf = "\023\000\000\000\000\000\000\000\270^\377?\270^\377?", _M_allocated_capacity = 19}} b = 0x3fff5e20 "MP-0 C7,metric list" len = <optimized out> code = 67 'C' payload = {static npos = <optimized out>, _M_dataplus = {<std::allocator<char>> = {<__gnu_cxx::new_allocator<char>> = {<No data fields>}, <No data fields>}, _M_p = 0x3fff5ea8 "7,metric list"}, _M_string_length = 13, {_M_local_buf = "7,metric list\000\000", _M_allocated_capacity = 1701653559}} (gdb) info args this = 0x3fff433c Here is the size of that std::ostringstream: std::ostringstream buffer; ESP_LOGI(TAG,"std::ostringstream buffer is %d bytes",sizeof(buffer)); I (41478) ovms-server-v2: std::ostringstream buffer is 200 bytes 200 bytes, not 2,000 bytes, so something else is going on here. Anyway, changing it to a dynamically (new/delete) allocated buffer, drops stack usage of that frame to 1,824 bytes (was 2,208 so that is 384 bytes saved). That uint8_t b[line.length()+1] in OvmsServerV2::ProcessServerMsg() is also nasty - it will grow stack usage depending on line length. So, we’ll fix that as well. 192 bytes -> 160 bytes. Things to note: Each stack call is a minimum of 32 bytes. Not so bad, really - we’d need to nest calls 32 deep to get 1KB stack usage. Local variables are scary. They can be unexpectedly large. Best to new/free them, to guarantee just 4 bytes each. The OvmsCommand::Execute recursion I was worried about is not so bad. Probably 100 bytes of stack, or so, for most commands. We could improve that by getting rid of the recursion (it is elegant, but not strictly necessary), but it doesn’t seem to be a big win. I’m still looking for 150+ bytes in OvmsServerV2::ProcessServerMsg(), and 1,900+ bytes in OvmsServerV2::ProcessCommand(). Those would be big. Regards, Mark.

3 5

<enter> not working with vfs edit?
by Greg D. 12 Jan '18

12 Jan '18

Is anyone else having trouble with the vfs editor? I can't seem to enter a newline anymore. The status line at the bottom complains of an unknown command 10 (presumably control-J). If I try an explicit control-M, it says the same. Did I fat-finger something in my config (I removed SSH, Telnet, and several other items to save RAM recently), or did something else change? This is with two different terminals - make monitor on the development laptop, and putty on my in-car Raspberry Pi. Greg

4 3

Higher resolution events
by Tom Parker 10 Jan '18

10 Jan '18

Hi, To implement the Leaf's remote climate control, I need to send a frame, wait 50ms and then repeat another frame every 100ms for 25 repetitions. On the v2 hardware I implemented this with a 50ms delay and the ticker10th function. I wasn't able to find any delay functions in v3 so either I didn't look hard enough, nothing needs one, or busy-waiting isn't the right thing to do. Ticker10th isn't implemented. I could refactor the existing ticker task to fire 10 times a second instead of once per second, or I could register a new task for the climate control and cancel it after the the 25 repetitions. Or maybe something else altogether is appropriate? Thoughts?

4 7

SD CARD
by Mark Webb-Johnson 10 Jan '18

10 Jan '18

Any electronics guys out there can help out with SD CARD? It is frustrating as hell. The last part of the hardware puzzle. Once we solve this, we can hit the button to start making these. China and I have been struggling with this for the last month, with little progress. We are just following the standard Espressif schematics for this. Here is Espressif’s master document on it: https://github.com/espressif/esp-idf/tree/master/examples/storage/sd_card <https://github.com/espressif/esp-idf/tree/master/examples/storage/sd_card> Our circuit has been built for 4 wire SD mode, using the standard pins and pullups (as documented by Espressif). Result is that it is unreliable. Fails to mount 90% of SD CARDS, and those that do mount fail and corrupt data when writing lots of data out. The core problem (we think) is that the GPIO2 and GPIO12 pins used for SD CARD are also required to be at specific values during boot (to select different boot modes). Espressif suggest to work around this using the transistor logic they have for controlling boot mode pins using the USB-to-serial converter and DTR + RTS async control pins. We want 4-wire, but let’s start with a simple 1-wire diagram on a breadboard (as per Espressif instructions): ESP32 pin SD card pin SPI pin Notes GPIO14 (MTMS) CLK SCK 10k pullup in SD mode GPIO15 (MTDO) CMD MOSI 10k pullup, both in SD and SPI modes GPIO2 D0 MISO 10k pullup in SD mode, pull low to go into download mode (see note below!) GPIO4 D1 N/C not used in 1-line SD mode; 10k pullup in 4-line SD mode GPIO12 (MTDI) D2 N/C not used in 1-line SD mode; 10k pullup in 4-line SD mode (see note below!) GPIO13 (MTCK) D3 CS not used in 1-line SD mode, but card's D3 pin must have a 10k pullup N/C CD optional, not used in the example N/C WP optional, not used in the example Also: Connect GPIO0 and GPIO2 using a jumper (so transistors drive GPIO2 and GPIO0 low when entering download mode (10K pullup otherwise) 3.3V connect to SDCARD GND connect to SDCARD We have a variety of ESP32 development modules to try this with. Espressif said that the original DEVKIT C had a problem with the boot pin control lines and transistor logic (but never said what exactly that problem was). With original (old) ESP32 DEVKIT C, I can’t get it to work reliably at all. Sometimes ok. Sometimes not. With OVMS test code (that writes a lot of data), it never works. With our OVMS boards, all versions, I can’t get it to work reliably at all. Sometimes ok. Sometimes not. With OVMS test code (that writes a lot of data), it never works. I don’t think it ever worked. Just before our test was so simple that it didn’t show the problem. So, I just purchased one of these: https://www.banggood.com/ESP32-Development-Board-WiFiBluetooth-Ultra-Low-Po… <https://www.banggood.com/ESP32-Development-Board-WiFiBluetooth-Ultra-Low-Po…> Geekcreit® ESP32 Development Board WiFi+Bluetooth Ultra Low Power Consumption Dual Cores ESP-32 ESP-32S Board (Very similar to DEVKIT C, but more modern) It works 100%. Although after flashing it cannot boot (waiting for download) - need to disconnect GPIO0 - GPIO2 link, reset, then reconnect GPIO0-GPIO2 link. Then perfect. I think our problem is related to that transistor auto-flash reset circuitry. GPIO2 is the line for data transfer, so if problem will cause data corruption and unreliable (like we are seeing). Espressif SD CARD notes here: https://github.com/espressif/esp-idf/tree/master/examples/storage/sd_card <https://github.com/espressif/esp-idf/tree/master/examples/storage/sd_card> Schematic for Geekcreit board is here: https://www.dropbox.com/s/jefwxxtufgwg0ex/esp32_Schematic%20Prints.pdf?dl=0 <https://www.dropbox.com/s/jefwxxtufgwg0ex/esp32_Schematic%20Prints.pdf?dl=0> Schematic for latest version of Espressif DEVKIT C board is here: http://espressif.com/sites/default/files/documentation/esp32_hardware_desig… <http://espressif.com/sites/default/files/documentation/esp32_hardware_desig…> The original DEVKIT C (v1) had 1K resistors on that circuit. This is the version I have. The Geekcreit has 10K resistors on that circuit. OVMS has 10K resistors on that circuit. The latest DEVKIT C (v3) has 12K resistors on that circuit. DEVKIT C v1 schematic is here: http://dl.espressif.com/dl/schematics/ESP32-DevKitJ-v1_sch.pdf <http://dl.espressif.com/dl/schematics/ESP32-DevKitJ-v1_sch.pdf> DEVKIT C v2 schematic is here: http://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-2.pdf <http://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-2.pdf> The latest Espressif ROVER KIT development board schematic is here: https://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-3.pdf <https://dl.espressif.com/dl/schematics/ESP-WROVER-KIT_SCH-3.pdf> Note that they are now using 100K resistors, and a separate transistor on IO0 (to allow it to be independently controlled after boot). I am reasonably certain our SD CARD problem concerns the GPIO0-GPIO2 link. Can you look at these, and see if you can find the difference? Apart from resistor sizes (which Espressif keep messing around with), I can’t see the practical difference. Regards, Mark.

4 12

SD CARD vs 16MB flash
by Mark Webb-Johnson 09 Jan '18

09 Jan '18

Using Espressif standard SD CARD example program, modified to write "Hello\n” 10 million times, and then read it back 10 million times... Here is what I get with OVMS v3 developer-release hardware using release version of ESP IDF v2.1: I (50) boot: ESP-IDF v2.1.1-8-g5ae2c0d0 2nd stage bootloader I (51) boot: compile time 08:28:36 I (83) boot: Enabling RNG early entropy source... I (84) boot: SPI Speed : 40MHz I (84) boot: SPI Mode : DIO I (94) boot: SPI Flash Size : 16MB … I (910) cpu_start: Pro cpu start user code I (967) cpu_start: Starting scheduler on PRO CPU. I (972) example: Initializing SD card I (972) cpu_start: Starting scheduler on APP CPU. E (1112) sdmmc_cmd: sdmmc_card_init: send_scr returned 0x107 E (1112) example: Failed to initialize the card (263). Make sure SD card lines have pull-up resistors in place. Using latest (bleeding edge, not released) ESP IDF v3.1, using 1 line mode: I (31) boot: ESP-IDF v3.1-dev-168-ga1b59679 2nd stage bootloader I (31) boot: compile time 08:35:38 I (42) boot: Enabling RNG early entropy source... I (42) boot: SPI Speed : 40MHz I (42) boot: SPI Mode : DIO I (45) boot: SPI Flash Size : 16MB … I (195) cpu_start: Pro cpu up. I (199) cpu_start: Starting app cpu, entry point is 0x40080e38 I (0) cpu_start: App cpu up. I (209) heap_init: Initializing. RAM available for dynamic allocation: I (216) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM I (222) heap_init: At 3FFB2A48 len 0002D5B8 (181 KiB): DRAM I (228) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM I (235) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (241) heap_init: At 40089270 len 00016D90 (91 KiB): IRAM I (247) cpu_start: Pro cpu start user code I (265) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. I (267) example: Initializing SD card I (267) example: Using SDMMC peripheral Name: SB16G Type: SDHC/SDXC Speed: default speed Size: 15193MB CSD: ver=1, sector_size=512, capacity=31116288 read_bl_len=9 SCR: sd_spec=2, bus_width=5 I (347) example: Opening file I (347) example: write count = 0 ... I (25397) example: write count = 1000000 ... I (50417) example: write count = 2000000 ... I (75737) example: write count = 3000000 ... I (101277) example: write count = 4000000 ... I (127417) example: write count = 5000000 ... I (154087) example: write count = 6000000 ... I (180247) example: write count = 7000000 ... I (206977) example: write count = 8000000 ... I (232807) example: write count = 9000000 ... I (259647) example: File written I (259647) example: Renaming file I (259657) example: Reading file I (259657) example: read count = 0 ... I (278507) example: read count = 1000000 ... I (297367) example: read count = 2000000 ... I (316427) example: read count = 3000000 ... I (335347) example: read count = 4000000 ... I (354327) example: read count = 5000000 ... I (373157) example: read count = 6000000 ... I (391637) example: read count = 7000000 ... I (410097) example: read count = 8000000 ... I (428517) example: read count = 9000000 ... I (446807) example: Read from file: 'Hello' I (446807) example: Card unmounted and using v3.1 with 4-line mode: I (247) cpu_start: Pro cpu start user code I (265) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. I (267) example: Initializing SD card I (267) example: Using SDMMC peripheral Name: SB16G Type: SDHC/SDXC Speed: default speed Size: 15193MB CSD: ver=1, sector_size=512, capacity=31116288 read_bl_len=9 SCR: sd_spec=2, bus_width=5 I (347) example: Opening file I (357) example: write count = 0 ... I (24187) example: write count = 1000000 ... I (47637) example: write count = 2000000 ... I (71277) example: write count = 3000000 ... I (94927) example: write count = 4000000 ... I (119567) example: write count = 5000000 ... I (143517) example: write count = 6000000 ... I (168297) example: write count = 7000000 ... I (192597) example: write count = 8000000 ... I (216847) example: write count = 9000000 ... I (240587) example: File written I (240727) example: Renaming file I (240727) example: Reading file I (240737) example: read count = 0 ... I (257697) example: read count = 1000000 ... I (274507) example: read count = 2000000 ... I (291327) example: read count = 3000000 ... I (308117) example: read count = 4000000 ... I (325157) example: read count = 5000000 ... I (341647) example: read count = 6000000 ... I (358397) example: read count = 7000000 ... I (375097) example: read count = 8000000 ... I (391787) example: read count = 9000000 ... I (408247) example: Read from file: 'Hello' I (408247) example: Card unmounted Smiling so much my face hurts... This has been such a PITA, but it looks like Espressif have finally solved it with their latest pre-release SDK. Very little performance difference between 1 line and 4 line modes (4 line is about 8% faster), so probably not worth using up those GPIO lines for that. I’m working with Espressif to see if this fix can be back-ported to v2.1. I doubt it, but no harm asking… This all, of course, brings into top priority the work Steve and I are doing trying to get OVMS v3 firmware working against ESP IDF v3.x. Here’s a hastily hacked together kludge based on bleeding edge ESP IDF v3.1: OVMS > metrics list m.version m.version 3.0.0/factory/main build (idf v3.1-dev-168-ga1b59679) Jan 8 2018 10:09:53 OVMS > sd mount Name: SB16G Type: SDHC/SDXC Speed: default speed Size: 15193MB CSD: ver=1, sector_size=512, capacity=31116288 read_bl_len=9 SCR: sd_spec=2, bus_width=5 Mounted SD CARD OVMS > vfs ls /sd .Spotlight-V100 .fseventsd component.mk sd_card_example_main.c FOO.TXT OVMS > vfs cp /sd/FOO.txt /sd/FOO2.txt VFS copy complete OVMS > vfs ls /sd .Spotlight-V100 .fseventsd component.mk sd_card_example_main.c FOO2.TXT FOO.TXT That FOO.TXT file is about 60MB in size. Now finalising hardware with the china manufacturer. I think at this point, it is worth: Use 1 line SD CARD (which frees up GPIOs SD_DATA1/SD_DATA2/SD_DATA3, but also avoids the conflict between GPIO12/SD_DATA2 and VDD_SDIO bootstrap pin). Add some capacitors for power line smoothing, as per Espressif’s example in their test board. Double-check power on SIMCOM module, to ensure it is as expected (following issues reported with low-amperage USB ports). Change to use Analog Lamb WROOM-32 module and their 16MB flash + 4MB ram. Change #4 should be the only controversial one. It has the advantages of much more RAM, and no need for external flash, but the disadvantage is that we would have to move GPIOs for simcom async (as those are using by Analog Lamb for their chip). It also depends on Analog Lamb’s lead time, and future plans for this module. Regards, Mark

3 3

WiFi mode off reboot
by Greg D. 09 Jan '18

09 Jan '18

Hi folks, Another crash. Not repeatable, but wanted to report it before I head up stairs to end the day. I had booted the module, modem off, obdii ecu started, v2 server enabled but not connected. Wifi was started but the local network is hidden, so it wasn't connected. This is all in the startup event script. OBDWiz dongle running, all fine. The plan was to let it run for the night, to catch any longer-term reboots, so I needed to turn off the wifi in order to keep the screen from filling up with 'incorrect scan type' messages. Hit wifi mode off, and it crashed (see below). Doesn't appear to be a memory issue. Tried it a second time, and wifi stopped as normal. {sigh} Definitely time for bed... Greg OVMS > wifi mode off Stopping wifi station... ESP_ERROR_CHECK failed: esp_err_t 0x3002 at 0x400d6945 0x400d6945: _ZN9esp32wifi17EventWifiScanDoneENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPv at /home/greg/greg/ovms/Open-Vehicle-Monitoring-System-3-master/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/esp32wifi/./esp32wifi.cpp:462 (discriminator 1) file: "/home/greg/greg/ovms/Open-Vehicle-Monitoring-System-3-master/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/esp32wifi/./esp32wifi.cpp" line 462 func: void esp32wifi::EventWifiScanDone(std::__cxx11::string, void*) expression: esp_wifi_scan_get_ap_records(&apCount, list) Backtrace: 0x40088810:0x3ffbb580 0x40088b8d:0x3ffbb5a0 0x400d6945:0x3ffbb5c0 0x400d75d8:0x3ffbb690 0x40101965:0x3ffbb6d0 0x40101bbe:0x3ffbb700 0x40101c61:0x3ffbb750 0x40102089:0x3ffbb9a0 0x4013e991:0x3ffbb9c0 0x4013e9d5:0x3ffbb9e0 0x40088810: invoke_abort at /home/greg/esp/esp-idf/components/esp32/./panic.c:519 0x40088b8d: _esp_error_check_failed at /home/greg/esp/esp-idf/components/esp32/./panic.c:531 0x400d6945: _ZN9esp32wifi17EventWifiScanDoneENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPv at /home/greg/greg/ovms/Open-Vehicle-Monitoring-System-3-master/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/components/esp32wifi/./esp32wifi.cpp:462 (discriminator 1) 0x400d75d8: _ZNKSt12_Mem_fn_baseIM9esp32wifiFvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPvELb1EEclIJS6_S7_EvEEvPS0_DpOT_ at /home/greg/esp/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:600 (inlined by) _ZNSt5_BindIFSt7_Mem_fnIM9esp32wifiFvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPvEEPS1_St12_PlaceholderILi1EESD_ILi2EEEE6__callIvJOS7_OS8_EJLj0ELj1ELj2EEEET_OSt5tupleIJDpT0_EESt12_Index_tupleIJXspT1_EEE at /home/greg/esp/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:1074 (inlined by) _ZNSt5_BindIFSt7_Mem_fnIM9esp32wifiFvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPvEEPS1_St12_PlaceholderILi1EESD_ILi2EEEEclIJS7_S8_EvEET0_DpOT_ at /home/greg/esp/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:1133 (inlined by) _ZNSt17_Function_handlerIFvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPvESt5_BindIFSt7_Mem_fnIM9esp32wifiFvS5_S6_EEPSA_St12_PlaceholderILi1EESF_ILi2EEEEE9_M_invokeERKSt9_Any_dataOS5_OS6_ at /home/greg/esp/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:1871 0x40101965: _ZNKSt8functionIFvNSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPvEEclES5_S6_ at /home/greg/esp/xtensa-esp32-elf/xtensa-esp32-elf/include/c++/5.2.0/functional:2271 0x40101bbe: _ZN10OvmsEvents11SignalEventENSt7__cxx1112basic_stringIcSt11char_traitsIcESaIcEEEPv at /home/greg/greg/ovms/Open-Vehicle-Monitoring-System-3-master/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_events.cpp:144 0x40101c61: _ZN10OvmsEvents17SignalSystemEventEP14system_event_t at /home/greg/greg/ovms/Open-Vehicle-Monitoring-System-3-master/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_events.cpp:167 0x40102089: _ZN10OvmsEvents18ReceiveSystemEventEPvP14system_event_t at /home/greg/greg/ovms/Open-Vehicle-Monitoring-System-3-master/Open-Vehicle-Monitoring-System-3/vehicle/OVMS.V3/main/./ovms_events.cpp:155 0x4013e991: esp_event_post_to_user at /home/greg/esp/esp-idf/components/esp32/./event_loop.c:94 0x4013e9d5: esp_event_loop_task at /home/greg/esp/esp-idf/components/esp32/./event_loop.c:94 Rebooting...

2 2

Kia Soul status.
by Geir Øyvind Vælidalo 08 Jan '18

08 Jan '18

Just a small status update on the Kia Soul porting. My OVMS V3 is now connecting to the V2 server via my WiFi-network at home. I’ve got the first data from the new hardware through to the OVMS app on my iPhone. Fantastic job guys! As soon as my health is ok again, I can start testing the hardware in my car and verify the data and fix the bugs. The Kia Soul should be almost on par with the V2, with a few things added. Just wish I had a case... And I need to get a twin sim-card (I got free SMS and lots of data included 🙂 ) so it can be online away from home. Oh, and a passive GPS-antenna. This is looking good! Geir

3 7