March 2018 - OvmsDev - Open Vehicles

time stands still?
by Greg D. 20 Mar '18

20 Mar '18

2 1

Memory leak
by Stephen Casner 20 Mar '18

20 Mar '18

I see there are a couple of tasks that allocated memory but did not free it. These are the tasks identified by TCB address in the module memory listing: OVMS# mo m Free 8-bit 32968/283136, 32-bit 27588/55864, SPIRAM 0/0 --Task-- Total DRAM D/IRAM IRAM SPIRAM +/- DRAM D/IRAM IRAM SPIRAM no task 5276 0 0 0 +5276 +0 +0 +0 esp_timer 55300 0 644 0 +55300 +0 +644 +0 main 40072 0 0 0 +40072 +0 +0 +0 ipc0 10848 0 0 0 +10848 +0 +0 +0 Housekeeping 17588 44112 0 0 +17588 +44112 +0 +0 ipc1 12 0 0 0 +12 +0 +0 +0 tiT 136 1676 0 0 +136 +1676 +0 +0 NetManTask 8 2196 0 0 +8 +2196 +0 +0 wifi 0 1600 0 0 +0 +1600 +0 +0 eventTask 0 12960 0 0 +0 +12960 +0 +0 3FFE3E78 0 1396 0 0 +0 +1396 +0 +0 Tmr Svc 0 27808 0 0 +0 +27808 +0 +0 3FFEAFE4 0 88 0 0 +0 +88 +0 +0 AsyncConsole 0 20 27488 0 +0 +20 +27488 +0 OVMS# mo t Number of Tasks = 16 Stack: Now Max Total Heap 32-bit SPIRAM Task 3FFAFAB0 1 esp_timer 0 61770 65278 55300 644 0 Task 3FFBDFC4 2 eventTask 0 63886 65278 12960 0 0 Task 3FFC6630 3 CanRxTask 0 61610 65278 0 0 0 Task 3FFCDA54 4 ipc0 0 64702 65278 10848 0 0 Task 3FFCE054 5 ipc1 0 64702 65278 12 0 0 Task 3FFCFE7C 8 IDLE 0 64742 65278 0 0 0 Task 3FFD0410 9 IDLE 0 64746 65278 0 0 0 Task 3FFD1DA4 10 Tmr Svc 0 61678 65278 27808 0 0 Task 3FFD9DC8 14 Housekeeping 0 62478 65278 61700 0 0 Task 3FFCE2C0 16 tiT 0 63506 65278 1812 0 0 Task 3FFE327C 17 SIMCOMTask 0 61638 65278 0 0 0 Task 3FFF0654 22 AsyncConsole 0 62510 65278 20 27488 0 Task 3FFE8464 25 wifi 0 63474 65278 1600 0 0 Task 3FFF1828 26 pmT 0 64398 65278 0 0 0 Task 3FFE82CC 29 NetManTask 0 60254 65278 2204 0 0 Task 3FFEC408 30 mdns 0 62906 65278 0 0 0 OVMS# -- Steve

3 5

wifi not coming all the way up?
by Stephen Casner 20 Mar '18

20 Mar '18

When I start wifi client, it looks like it has acquired the link, but not done DHCP to get an address? -- Steve OVMS # wifi mode client Revelstoke Starting WIFI as a client to Revelstoke... I (742914) wifi: wifi firmware version: ebd3e5d I (742914) wifi: config NVS flash: enabled I (742914) wifi: config nano formating: disabled I (742914) wifi: Init dynamic tx buffer num: 16 I (742914) wifi: Init data frame dynamic rx buffer num: 16 I (742914) wifi: Init management frame dynamic rx buffer num: 16 I (742914) wifi: wifi driver task: 3fff1044, prio:23, stack:4096 I (742914) wifi: Init static rx buffer num: 4 I (742914) wifi: Init dynamic rx buffer num: 16 I (742914) wifi: wifi power manager task: 0x3ffe81d8 prio: 21 stack: 2560 I (742924) wifi: mode : sta (30:ae:a4:37:1b:84) I (745344) wifi: n:1 0, o:1 0, ap:255 255, sta:1 0, prof:1 I (745994) wifi: state: init -> auth (b0) I (746004) wifi: state: auth -> assoc (0) I (746014) wifi: state: assoc -> run (10) I (746054) wifi: connected with Revelstoke, channel 1 I (749014) wifi: pm start, type:0 OVMS # net Interface#0: lo0 (ifup=1 linkup=1) IPv4: 127.0.0.1/255.0.0.0 gateway 127.0.0.1 DNS: None Default Interface: None OVMS #

5 19

Making secure
by Stephen Casner 19 Mar '18

19 Mar '18

I need to go to a concert now and have not done server yet. Someone else can do it, or I'll be back about 5:30 PDT. -- Steve

3 8

Server v2 hang / crash / ?
by Greg D. 19 Mar '18

19 Mar '18

2 1

Command prompt in secure mode
by Stephen Casner 19 Mar '18

19 Mar '18

At Mark's request I have implemented a change to the command prompt after switching to secure mode: OVMS > ena Password: Secure mode OVMS # As implemented in this commit, the color also changes from green to red, but that is only a proposal. I also looked at blue, but on my terminal it's not so distinct from black. If preferred, we can have both modes be green. Actually, as I thought about this, I wondered whether our console welcome banner and prompt should be different from green since all the info-level log messages are green. But there are not many ANSI color choices and they don't look the same on all terminals, so we can't get carried away with this. -- Steve

4 7

Problems with AP + Client mode
by Greg D. 19 Mar '18

19 Mar '18

Hi folks, Are any of you having trouble with AP+Client mode? A couple of observations.... AP mode, by itself, works great. AP+Client, however, seems to depend on whether the client side gets connected or not. If it does, I can also connect to the AP, and when connected, navigate the webserver. If the client side doesn't get connected (the specified SSID isn't available), my phone can connect to the AP, but accessing the webserver never works (times out). This is with the simcom modem unconnected (antenna removed). I also have the DNS server address fixed to '9.9.9.9 8.8.8.8', to remove that from being an issue. If I go into the webserver (when it's working) and configure the client SSID to connect to any available, neither the client nor the AP come up after a module reset. This is apparently due to an error during the Auto execution, where the 'wifi mode apclient' command is failing due to not having the client ssid specified (it's coded as required, should be optional). As I noted earlier, if the module comes up and the client SSID isn't immediately available, the ability for it to connect later is limited. Mark suggested this is because the wifi client isn't scanning channels other than the one the AP mode is on, so it's a matter of luck if the client AP happens to come up on the right one. (Here, that never seems to occur :( ). If the AP+Client does come up (client SSID is available), and later the modem gets connected, connection to the v2 server hangs. Seems like the internal routing of traffic is getting confused, or rather, the module is getting a new IP address, but the server's connection is not bounced. (Enhancement request: Have the network status command to note which interface is considered active.) IMHO, we really shouldn't even try to run the modem if the server is connected via the wifi client, because, besides messing up the network configuration, it's also causing a slow drain on the modem's data plan (I'm seeing the Rx/Tx counters increment) for no benefit. Sometimes I get a spew of 'job queue overflow' errors (see below). Not sure of all the conditions, but tapping the Status tab seems the most often cause, though it can be tapped without causing the error too. Under conditions where the AP+Client had the client connected and the AP able to associate, but not able to access the webserver, I was able to get to the webserver if I joined the same network as the client and surfed to the module's address there. Lots of test cases here. I really need a test matrix to be sure I can reproduce the issues and successes later... Part of the puzzle is that the retries built into the software often recover things, so it's hard to know what's a fatal failure, and what is recoverable in time, and so may be less serious for the end user. Finally, I have seen circumstances where the simcom model gets into a state where it comes up and starts connecting, but after a few frames (less than 10) gets stuck with an increasing number of framing errors, but no progress on receive. Eventually it will reset and try again, and after some number of these, sometimes finally connect (and mess up the wifi that was running happily all along). Greg I (473446) simcom: Power Cycle I (479406) simcom: State: Enter PoweredOn state I (498456) simcom: State: Enter MuxStart state I (498456) gsm-mux: Start MUX I (498466) gsm-mux: Channel #0 is open I (498466) gsm-mux: Channel #1 is open I (498476) gsm-mux: Channel #2 is open I (498476) gsm-mux: Channel #3 is open I (498486) gsm-mux: Channel #4 is open I (499446) simcom: State: Enter NetWait state I (503836) webserver: HTTP POST /api/execute I (503836) webcommand: HttpCommandStream[0x3fff96c0]: 20240 bytes free, executing: simcom status I (509506) simcom: CREG Network Registration: RegisteredRoaming I (510446) simcom: State: Enter NetStart state I (511596) simcom: PPP Connection is ready to start I (512446) simcom: State: Enter NetMode state I (512446) gsm-ppp: Initialising... I (512456) webserver: HTTP GET /home I (515616) gsm-ppp: StatusCallBack: None I (515616) gsm-ppp: status_cb: Connected I (515616) gsm-ppp: our_ipaddr = 10.170.146.142 I (515616) gsm-ppp: his_ipaddr = 10.64.64.64 I (515616) gsm-ppp: netmask = 255.255.255.255 I (515616) gsm-ppp: our6_ipaddr = :: I (515616) netmanager: Set DNS#0 9.9.9.9 I (515616) netmanager: Set DNS#1 8.8.8.8 I (515616) time: Starting SNTP client I (517746) webserver: HTTP GET /home I (520476) webserver: HTTP GET /status W (526166) websocket: WebSocketHandler[0x3fff5f2c]: job queue overflow W (526416) websocket: WebSocketHandler[0x3fff5f2c]: job queue overflow W (526446) websocket: WebSocketHandler[0x3fff5f2c]: job queue overflow W (526666) websocket: WebSocketHandler[0x3fff5f2c]: job queue overflow W (526916) websocket: WebSocketHandler[0x3fff5f2c]: job queue overflow W (527166) websocket: WebSocketHandler[0x3fff5f2c]: job queue overflow W (527416) websocket: WebSocketHandler[0x3fff5f2c]: job queue overflow W (527446) websocket: WebSocketHandler[0x3fff5f2c]: job queue overflow

3 8

Simcom restart crash
by Greg D. 19 Mar '18

19 Mar '18

1 0

Command security
by Stephen Casner 18 Mar '18

18 Mar '18

Mark asked me to check whether the 'secure' flag is set appropriately in the various command invocation contexts. I began with the console command list where there are a number of questionable settings. My assumption going in is that all someone should be able to do before enabling is to look at status that does not include sensitive info. However, there are several commands that do more. All of these commands are at least partially enabled in non-secure mode: OVMS > ? boot BOOT framework echo Test getchar enable Enter secure mode event EVENT framework exit End console session help Ask for help metrics METRICS framework module MODULE framework network NETWORK framework notify NOTIFICATION framework obdii OBDII framework server OVMS Server Connection framework simcom SIMCOM framework time TIME framework vehicle Vehicle framework The harmless ones are 'boot', which just shows status, 'echo', 'exit' and 'help'. Of course, 'enable' needs to be here to change state. But I have questions about all the others: 1. obdii, server and simcom appear to allow their full functionality, including starting and stopping operations, in non-secure mode. That seems wrong. 2. event, metrics and notify all allow tracing to be turned on or off. Is that safe? 3. time allows setting the time in non-secure mode. That may not be critical in this system, but could mess up timed activities. 4. Setting the vehicle module should require being enabled, no? 5. Is it OK to list the metrics in non-secure mode? Is any of that information sensitive enough that it should be prevented? (We don't have the option to show some metrics and not others at this point.) 6. The module command only allowed the subcommand 'factory' which did not allow any subcommand, so the right fix there is to just make the whole command require secure mode. This observation exposed a bug in the code to construct the usage string, which I fixed. So, basically, the question is what do we want someone to be able to do in non-secure mode? -- Steve

3 3

ota questions
by Michael Balzer 18 Mar '18

18 Mar '18

Working on the OTA web UI. Some questions: a) Flashing and changing the boot partition outputs some irritating overflow and "??" log messages: OVMS > ota flash vfs /sd/ovms3.done Current running partition is: ota_0 Target partition is: ota_1 Source image is 1480592 bytes in size Preparing flash partition... Flashing image partition... Setting boot partition... OTA flash was successful Flashed 1480592 bytes from /sd/ovms3.done Next boot will be from 'ota_1' I (1316956) esp_image: segment 0: paddr=0x00810020 vaddr=0x3f400020 size=0x5879c (362396) map I (1317156) esp_image: segment 1: paddr=0x008687c4 vaddr=0x3ffb0000 size=0x0382c ( 14380) I (1317156) esp_image: segment 2: paddr=0x0086bff8 vaddr=0x40080000 size=0x00400 ( 1024) 0x40080000: _WindowOverflow4 at /home/balzer/esp/esp-idf/components/freertos/./xtensa_vectors.S:1685 I (1317166) esp_image: segment 3: paddr=0x0086c400 vaddr=0x40080400 size=0x03c10 ( 15376) I (1317176) esp_image: segment 4: paddr=0x00870018 vaddr=0x400d0018 size=0xfb154 (1028436) map 0x400d0018: _flash_cache_start at ??:? I (1317746) esp_image: segment 5: paddr=0x0096b174 vaddr=0x40084010 size=0x0e5b4 ( 58804) 0x40084010: spi_flash_mmap at /home/balzer/esp/esp-idf/components/spi_flash/./flash_mmap.c:293 I (1317776) esp_image: segment 6: paddr=0x00979730 vaddr=0x400c0000 size=0x00034 ( 52) I (1317776) esp_image: segment 0: paddr=0x00810020 vaddr=0x3f400020 size=0x5879c (362396) map I (1317976) esp_image: segment 1: paddr=0x008687c4 vaddr=0x3ffb0000 size=0x0382c ( 14380) I (1317986) esp_image: segment 2: paddr=0x0086bff8 vaddr=0x40080000 size=0x00400 ( 1024) 0x40080000: _WindowOverflow4 at /home/balzer/esp/esp-idf/components/freertos/./xtensa_vectors.S:1685 I (1317986) esp_image: segment 3: paddr=0x0086c400 vaddr=0x40080400 size=0x03c10 ( 15376) I (1317996) esp_image: segment 4: paddr=0x00870018 vaddr=0x400d0018 size=0xfb154 (1028436) map 0x400d0018: _flash_cache_start at ??:? I (1318566) esp_image: segment 5: paddr=0x0096b174 vaddr=0x40084010 size=0x0e5b4 ( 58804) 0x40084010: spi_flash_mmap at /home/balzer/esp/esp-idf/components/spi_flash/./flash_mmap.c:293 I (1318606) esp_image: segment 6: paddr=0x00979730 vaddr=0x400c0000 size=0x00034 ( 52) … OVMS > ota boot ota_1 Boot from ota_1 at 0x00810000 (size 0x00400000) I (301766) esp_image: segment 0: paddr=0x00810020 vaddr=0x3f400020 size=0x5879c (362396) map I (301966) esp_image: segment 1: paddr=0x008687c4 vaddr=0x3ffb0000 size=0x0382c ( 14380) I (301976) esp_image: segment 2: paddr=0x0086bff8 vaddr=0x40080000 size=0x00400 ( 1024) 0x40080000: _WindowOverflow4 at /home/balzer/esp/esp-idf/components/freertos/./xtensa_vectors.S:1685 I (301976) esp_image: segment 3: paddr=0x0086c400 vaddr=0x40080400 size=0x03c10 ( 15376) I (301986) esp_image: segment 4: paddr=0x00870018 vaddr=0x400d0018 size=0xfb154 (1028436) map 0x400d0018: _flash_cache_start at ??:? I (302556) esp_image: segment 5: paddr=0x0096b174 vaddr=0x40084010 size=0x0e5b4 ( 58804) 0x40084010: spi_flash_mmap at /home/balzer/esp/esp-idf/components/spi_flash/./flash_mmap.c:293 I (302596) esp_image: segment 6: paddr=0x00979730 vaddr=0x400c0000 size=0x00034 ( 52) Can these safely be ignored? The flashed partitions seem to work correctly. b) How do you get back to the factory partition if something went so wrong you can't use the "ota" command? I would have expected "make flash" to reset the boot partition to "factory", as all flashes are only done there, but it doesn't. So if you're on another partition with a broken firmware, how do you recover? Is there a way to set the boot partition using esptool.py? c) ota flash http still gives me a DNS lookup error on any other host than api.openvehicles.com and fails to download from api.openvehicles.com, regardless of the type of network (wifi/modem). OVMS > ota flash http www.google.com/ovms3.bin Current running partition is: factory Target partition is: ota_0 Download firmware from www.google.com/ovms3.bin to ota_0 Error: Request failed W (666891) net: DNS lookup on www.google.com failed err=200 OVMS > ota flash http api.openvehicles.com/test.bin Current running partition is: factory Target partition is: ota_0 Download firmware from api.openvehicles.com/test.bin to ota_0 […dead, needs reset] Is this a local problem of mine? Regards, Michael -- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26

4 26