[Ovmsdev] Newbie question & initial report

[Stephen Casner]

On Sun, 8 Oct 2017, Mark Webb-Johnson wrote:

> I think that is because no network connection available (wifi). Can
> you try with wifi up, running, and an IP address assigned?

OVMS > ota flash http
Current running partition is: factory
Target partition is: ota_0
Download firmware from api.openvehicles.com/firmware/ota/v3/main/ovms3.bin to ota_0
Checksum is ae7b3ab032f6a5be7a8789650c76ea52 and expected file size is 927777
Preparing flash partition...
Downloading... (100943 bytes so far)
Downloading... (201095 bytes so far)
Downloading... (301399 bytes so far)
Downloading... (402139 bytes so far)
Downloading... (502879 bytes so far)
Downloading... (603771 bytes so far)
Downloading... (704359 bytes so far)
Downloading... (805099 bytes so far)
Downloading... (905839 bytes so far)
Download file length is 927744 and digest ae7b3ab032f6a5be7a8789650c76ea52
Setting boot partition...
OTA flash was successfull
  Flashed 927744 bytes from api.openvehicles.com/firmware/ota/v3/main/ovms3.bin
  Next boot will be from 'ota_0'

> Seems stack gets messed up in that case. I'll try to find out why,
> but the backtrace isn't helping much.

You may have noticed that in 57aab41 I fixed the bug that caused the
crash.  The OvmsHttpClient::m_buf variable was not initialized.  Now
without the wifi connection I get:

OVMS > ota flash http
Current running partition is: factory
Target partition is: ota_0
Download firmware from api.openvehicles.com/firmware/ota/v3/main/ovms3.bin to ota_0
Error: Request failed
W (8297) net: DNS lookup on api.openvehicles.com failed err=202

                                                        -- Steve