- OvmsDev - Open Vehicles

webserver (?) crash
by Greg D. 20 Mar '18

20 Mar '18

Hi folks, Ok, so the new code seems to be working half-way decently. But I think there's a memory issue with the webserver. After poking at home and status a couple of times, my browser (chrome or Firefox) drop from a nicely formatted screen to something very text-like. Links and words, no buttons. Then another poke or two and the module crashed. I've done it a few times, and the crash usually seem to be with the Status button, which, looking at the console, seems to have an auto-repeat on it. I managed to get the repeated "job queue overflow" once, followed after hitting home a few times, a similar crash as below. This was one of the quicker crashes (browser didn't get to the text-mode state), using AP mode wifi. Browser in this case was Chrome. I have a suspicion that the issue with the text-mode stuff is a leak somewhere triggered by Firefox, with its CSS fetches. Greg OVMS> OVMS> I (12641) housekeeping: System considered stable (free: 35212 bytes) I (17331) simcom: State: Enter PoweredOn state I (30481) wifi: n:1 0, o:1 1, ap:1 1, sta:1 0, prof:1 I (30491) wifi: station: 40:4e:36:8a:44:c0 join, AID=1, g, 20 I (30491) esp32wifi: AP station connected: id: 1, MAC: 40:4e:36:8a:44:c0 I (37121) webserver: HTTP GET /home I (37371) simcom: State: Enter MuxStart state I (37371) gsm-mux: Start MUX I (40411) webserver: HTTP GET /status I (47611) webserver: HTTP GET /shell I (51031) webserver: HTTP GET /home I (53891) webserver: HTTP GET /status I (59031) webserver: HTTP GET /home I (61581) webserver: HTTP GET / I (61661) webserver: HTTP GET /home I (63511) webserver: HTTP GET /home I (65971) webserver: HTTP GET /status OVMS> abort() was called at PC 0x400db927 on core 1 Backtrace: 0x4008f0b8:0x3ffeb8b0 0x4008f28f:0x3ffeb8d0 0x400db927:0x3ffeb8f0 0x4014880c:0x3ffeb910 0x40154899:0x3ffeb930 0x40154a9f:0x3ffeb950 0x40126564:0x3ffeb980 0x401267c7:0x3ffeb9e0 0x40126846:0x3ffeba00 0x4012841f:0x3ffeba50 0x400f6aff:0x3ffebb10 0x400f7262:0x3ffebb40 0x400f6aff:0x3ffebb60 0x400f7c8e:0x3ffebb90 0x400f7d3f:0x3ffebbc0 0x400f80eb:0x3ffebbf0 0x400f834d:0x3ffebc30 0x400f4b2d:0x3ffebc80 0x400e749a:0x3ffebca0 0x400e74d9:0x3ffebcf0 Rebooting... ets Jun 8 2016 00:22:57 rst:0xc (SW_CPU_RESET),boot:0x1f (SPI_FAST_FLASH_BOOT) configsip: 156795334, SPIWP:0xee clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00 mode:DIO, clock div:2 load:0x3fff0018,len:4 load:0x3fff001c,len:4560 ho 0 tail 12 room 4 load:0x40078000,len:0 load:0x40078000,len:13176 entry 0x40078d38 I (647) cpu_start: Pro cpu up. I (648) cpu_start: Starting app cpu, entry point is 0x40081300 I (632) cpu_start: App cpu up. I (651) heap_init: Initializing. RAM available for dynamic allocation: I (658) heap_init: At 3FFAE6E0 len 00001920 (6 KiB): DRAM I (664) heap_init: At 3FFBBAC0 len 00024540 (145 KiB): DRAM I (670) heap_init: At 3FFE0440 len 00003BC0 (14 KiB): D/IRAM I (676) heap_init: At 3FFE4350 len 0001BCB0 (111 KiB): D/IRAM I (684) heap_init: At 40091FDC len 0000E024 (56 KiB): IRAM I (689) cpu_start: Pro cpu start user code I (35) ovms_main: Set default logging level for * to INFO I (36) command: Initialising COMMAND (1000) I (36) boot: Initialising BOOT (1100) I (40) boot: Boot #4 reasons for CPU0=12 and CPU1=12 E (46) boot: Crash #4 detected I (49) events: Initialising EVENTS (1200) I (54) config: Initialising CONFIG (1400) I (59) time: Initialising TIME (1500) I (64) script: Initialising SCRIPTS (1600) I (68) script: Using DUKTAPE javascript engine I (74) metrics: Initialising METRICS (1810) I (78) metrics: Expanding DUKTAPE javascript engine I (88) notify: Initialising NOTIFICATIONS (1820) I (89) notify: Registered notification type info I (94) notify: Registered notification type error I (99) notify: Registered notification type alert I (105) notify: Registered notification type data I (110) location: Initialising LOCATIONS (1900) I (116) location: Expanding DUKTAPE javascript engine I (121) vehicle: Initialising VEHICLE Factory (2000) I (127) pcp: Initialising POWER (4000) I (131) max7317: Initialising MAX7317 EGPIO (4200) I (137) sdcard: Initialising SD CARD (4400) I (142) ota: Initialising OTA (4400) I (146) can: Initialising CAN (4500) I (151) simcom: Initialising SIMCOM (4600) I (155) test: Initialising TEST (5000) I (159) ovms-module: Initialising MODULE (5100) I (165) vfs: Initialising VFS (5200) I (169) ovms-server: Initialising OVMS Server (6000) I (174) ovms-server-v2: Initialising OVMS V2 Server (6100) I (181) ovms-server-v3: Initialising OVMS V3 Server (6200) I (187) obd2ecu: Initialising OBD2ECU (7000) I (192) canopen: Initialising CANopen (7000) I (197) esp32wifi: Initialising ESP32WIFI (8000) I (202) ovms-mdns: Initialising MDNS (8100) I (207) webserver: Initialising WEBSERVER (8200) I (213) telnet: Initialising Telnet (8300) I (217) ssh: Initialising SSH (8300) I (221) re: Initialising RE Tools (8800) I (226) netmanager: Initialising NETMANAGER (8999) I (233) v-track: Registering Vehicle: TRACK (9000) I (237) v-teslaroadster: Registering Vehicle: Tesla Roadster (9000) I (243) v-teslamodels: Registering Vehicle: Tesla Model S (9000) I (250) v-obdii: Registering Vehicle: OBDII (9000) I (256) v-none: Registering Vehicle: NONE (9000) I (261) v-demo: Registering Vehicle: DEMO (9000) I (266) version: Initialising Versioning (9900) I (275) cpu_start: Starting scheduler on PRO CPU. I (0) cpu_start: Starting scheduler on APP CPU. I (321) ovms_main: Executing on CPU core 0 I (321) ovms_main: Mounting CONFIG... W (371) webserver: UpdateGlobalAuthFile: no password set => no auth for web console I (381) ovms_main: Registering default configs... I (381) ovms_main: Starting HOUSEKEEPING... I (381) housekeeping: Initialising HOUSEKEEPING Framework... I (441) housekeeping: Executing on CPU core 1 I (441) housekeeping: reset_reason: cpu0=12, cpu1=12 I (441) housekeeping: Starting PERIPHERALS... I (451) peripherals: Initialising OVMS Peripherals... I (451) peripherals: TCP/IP Adaptor I (461) peripherals: ESP32 system I (461) peripherals: SPI bus I (461) peripherals: MAX7317 I/O Expander I (471) peripherals: ESP32 CAN I (471) peripherals: ESP32 WIFI I (481) peripherals: ESP32 BLUETOOTH I (481) peripherals: ESP32 ADC I (481) peripherals: MCP2515 CAN 1/2 I (501) peripherals: MCP2515 CAN 2/2 I (511) peripherals: SD CARD I (511) peripherals: SIMCOM MODEM I (511) gpio: GPIO[16]| InputEn: 0| OutputEn: 1| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0 I (521) gpio: GPIO[17]| InputEn: 1| OutputEn: 0| OpenDrain: 0| Pullup: 1| Pulldown: 0| Intr:0 I (531) uart: queue free spaces: 10 I (531) ext12v: Powering off external 12V devices I (541) housekeeping: Auto init ext12v (free: 112712 bytes) I (541) ext12v: Powering on external 12V devices I (551) housekeeping: Auto init wifi (free: 112712 bytes) I (551) wifi: wifi firmware version: ebd3e5d I (561) wifi: config NVS flash: enabled I (561) wifi: config nano formating: disabled I (561) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE I (571) system_api: Base MAC address is not set, read default base MAC address from BLK0 of EFUSE I (601) wifi: Init dynamic tx buffer num: 16 I (601) wifi: Init data frame dynamic rx buffer num: 16 I (601) wifi: Init management frame dynamic rx buffer num: 16 I (601) wifi: wifi driver task: 3ffe60f0, prio:23, stack:4096 I (611) wifi: Init static rx buffer num: 4 I (611) wifi: Init dynamic rx buffer num: 16 I (611) wifi: wifi power manager task: 0x3ffe8888 prio: 21 stack: 2560 I (1341) phy: phy_version: 383.0, 79a622c, Jan 30 2018, 15:38:06, 0, 0 I (1341) wifi: mode : sta (30:ae:a4:37:1b:64) + softAP (30:ae:a4:37:1b:65) I (1351) housekeeping: Auto init modem (free: 90568 bytes) I (1351) simcom: State: Enter PoweringOn state I (1351) simcom: Power Cycle I (1361) netmanager: WIFI access point is up I (1361) webserver: Launching Web Server I (1371) esp32wifi: AP started with SSID: ovms, MAC: 30:ae:a4:37:1b:65, IP: 192.168.4.1 I (1371) telnet: Launching Telnet Server I (1381) ssh: Launching SSH Server I (1441) simcom: State: Enter PoweredOn state I (2361) housekeeping: Auto init vehicle (free: 78820 bytes) I (2361) v-teslaroadster: Tesla Roadster v1.x, v2.x and v3.0 vehicle module I (2371) housekeeping: Auto init obd2ecu (free: 73088 bytes) I (2571) housekeeping: Auto init server v2 (free: 64432 bytes) I (2571) ovms-server-v2: OVMS Server V2 registered metric modifier is #1 I (2581) ovms-server-v2: Status: Starting I (2581) ovms-server-v2: OVMS Server v2 running I (2591) housekeeping: Auto init server v3 (free: 60120 bytes) I (2591) housekeeping: Auto init done (free: 60120 bytes) I (2601) housekeeping: Starting USB console... I (2601) uart: queue free spaces: 30 I (2611) ovms-mdns: Starting MDNS Welcome to the Open Vehicle Monitoring System (OVMS) - Async Console I (2651) version: Set version I (4181) wifi: n:1 1, o:1 0, ap:1 1, sta:1 0, prof:1 I (4841) wifi: state: init -> auth (b0) I (4841) wifi: state: auth -> auth (4a0) OVMS>

5 17

Things left to do, before production
by Mark Webb-Johnson 20 Mar '18

20 Mar '18

All components have arrived, and final assembly is happening now. Next week will be firmware flashing, QC, and then packaging. Label looks like this: Last things to do, with the goal of making this as easy as possible for the first guinea pig end users… Modem Stability. I’ve been working on this. Seems ok now; I drive in and out of zero coverage areas often, and it seems to recover. I’ll address any new issues as and when I find them. It would be helpful if others could put these in their cars, and feedback good/bad news. Module Password (via web interface). I’ve asked Michael to handle this, if he has time. Tidy up of ‘secure’ mode. I’ve asked Steve to handle this. OTA. It is workable at the moment. Not automatic, but pretty usable. I’ve committed my last change today so that ‘ota status’ shows the version available on the server (if wifi is up). It would be nice if the web interface could help with this; and particularly nice if we could upload firmware via the web interface directly to flash. I think Michael is working on this (at least the help, if not the upload). Deadline for the above is this Sunday (18th March). End-User Documentation. This is priority now, and deadline is the end of this month to have something good enough for someone to follow to setup the module from scratch. The other production and Fasttech side of things is being handled. We’re gonna have the Fasttech US$20 coupon codes ready to go at launch. Hologram have also offered a US$5 coupon code as a starter for OVMS users (both new and existing), which will be ready at launch as well. Developers can benefit from both. Fasttech will have 100 kits (50 US, 50 EU) and I’ll have 20 (10 US, 10 EU). Normal orders can go through Fasttech - if people need something special (just modems, just main boards, etc) let me know and I’ll handle it directly. So, for me it is now on to end-user documentation. As a reminder, that is in google docs and everyone is welcome to join in and help. The link to view/comment on the document is here: https://docs.google.com/document/d/16JrXR7rybp-18DrEoeh1rg6GqQT_jVBvhaXh2oE… If anyone wants to help directly edit/author some of it, let me know your eMail address and I’ll send an invite with editing privileges. Regards, Mark.

2 5

NetManTask created twice
by Stephen Casner 20 Mar '18

20 Mar '18

Mark, I'm looking for the memory allocated to nonexistant tasks. In my code I added a call to AddTaskToMap() after the creation of the NetManTask. Now I see that the nonexistant task holding 264 bytes was an earlier instance of NetManTask. Do you expect it to be created, killed, and created again? I'm considering making a public function that will query the task list to populate the TaskMap, same as what is done now when the module memory or module tasks command is invoked. Then I would add some calls to that function at one or more places in system startup to try to capture the other unnamed task while it exists. Any suggestions for where to make such a call? The output below is with the aforementioned AddTaskToMap() call added plus some changes in ovms_module to list the tasks in module memory in task number order so the order is consistent from one run to the next and with the nonexistent ones first and marked with asterisk. I can commit these changes if that is OK at this point. -- Steve Free 8-bit 31760/283148, 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 main * 40076 0 0 0 +40076 +0 +0 +0 3FFE5CDC * 0 1396 0 0 +0 +1396 +0 +0 NetManTask * 0 264 0 0 +0 +264 +0 +0 esp_timer 55112 0 644 0 +55112 +0 +644 +0 eventTask 0 7620 0 0 +0 +7620 +0 +0 ipc0 10848 0 0 0 +10848 +0 +0 +0 ipc1 12 0 0 0 +12 +0 +0 +0 Tmr Svc 0 27808 0 0 +0 +27808 +0 +0 Housekeeping 17488 50384 0 0 +17488 +50384 +0 +0 tiT 128 1640 0 0 +128 +1640 +0 +0 AsyncConsole 0 20 27488 0 +0 +20 +27488 +0 mdns 0 112 0 0 +0 +112 +0 +0 wifi 0 1612 0 0 +0 +1612 +0 +0 NetManTask 4 2200 0 0 +4 +2200 +0 +0

3 3

3.1 QC checks
by Mark Webb-Johnson 19 Mar '18

19 Mar '18

In production/qc/production_notes.txt we have the current production/qc notes (for China). Please look over those, and let me have any suggestions for anything to be changed / added? Deadline for submission is tomorrow morning (Asia time). It would be good to include a GPS test. Any ideas for how to do this - manually enabling the GPS? It can be a ‘simcom muxtx’ command if that helps (as check #6 has the modem up and ready). Regards, Mark.

1 0

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

19 Mar '18

2 1

Memory leak
by Stephen Casner 19 Mar '18

19 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 19 Mar '18

19 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 18 Mar '18

18 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. 18 Mar '18

18 Mar '18

2 1

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

18 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