Do I have to flash "entire chip" with esptool if I already have the code on my OVMS box?
Hi Mark et-al, I've installed the esp32 and the esp-idf environments on my Mac and successfully build the OVMS firmware. In the developer guide it then covers how to flash the box with esptool. But: do I need to do that? - my OVMS box is up and running already - I'm guessing I can use OTA update to update with steve@maximus OVMS.V3 % ls -l build/ovms3.bin -rw-r--r-- 1 steve staff 2986336 Dec 5 12:24 build/ovms3.bin ? Since the "flash from web" and and "flash from file" are looking for an ovms.bin. Nervous to brick my box since it was expensive to get it to Cape Town. By the way, my build prints 'App "ovms3" version: 3.2.015-162-g10232c58-dirty' I recognise the git commit hash, but what is the "-dirty"? (I build a "bmwi3" branch of a fork of the original project - maybe that answers my own question?) My OVMS box currently says it's running "3.2.015/ota_0/main (build idf v3.3.2-881-g22d636b7b Sep 2 2020 08:32:35)" Thanks, Steve
Steve, I know of no case of bricking by flashing the firmware. Using the developing environment, a simple "make app-flash" will do the esptool call for you. Of course you can also flash OTA. I usually flash my desk/development module by USB and the one in my car via Wifi from my local server. It's up to you. Flashing OTA can only update the firmware, but that's normally sufficient. The "-dirty" tag is appended when building from a "dirty" working tree, i.e. one with uncommitted changes. Regards, Michael Am 05.12.20 um 11:40 schrieb Steve Davies:
Hi Mark et-al,
I've installed the esp32 and the esp-idf environments on my Mac and successfully build the OVMS firmware.
In the developer guide it then covers how to flash the box with esptool.
But: do I need to do that? - my OVMS box is up and running already -
I'm guessing I can use OTA update to update with
steve@maximus OVMS.V3 % ls -l build/ovms3.bin -rw-r--r-- 1 steve staff 2986336 Dec 5 12:24 build/ovms3.bin
?
Since the "flash from web" and and "flash from file" are looking for an ovms.bin.
Nervous to brick my box since it was expensive to get it to Cape Town.
By the way, my build prints 'App "ovms3" version: 3.2.015-162-g10232c58-dirty'
I recognise the git commit hash, but what is the "-dirty"?
(I build a "bmwi3" branch of a fork of the original project - maybe that answers my own question?)
My OVMS box currently says it's running "3.2.015/ota_0/main (build idf v3.3.2-881-g22d636b7b Sep 2 2020 08:32:35)"
Thanks, Steve
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Links: - https://docs.openvehicles.com/en/latest/userguide/ota.html - https://docs.openvehicles.com/en/latest/userguide/factory.html#flash-factory... Am 05.12.20 um 12:51 schrieb Michael Balzer:
Steve,
I know of no case of bricking by flashing the firmware.
Using the developing environment, a simple "make app-flash" will do the esptool call for you.
Of course you can also flash OTA. I usually flash my desk/development module by USB and the one in my car via Wifi from my local server. It's up to you. Flashing OTA can only update the firmware, but that's normally sufficient.
The "-dirty" tag is appended when building from a "dirty" working tree, i.e. one with uncommitted changes.
Regards, Michael
Am 05.12.20 um 11:40 schrieb Steve Davies:
Hi Mark et-al,
I've installed the esp32 and the esp-idf environments on my Mac and successfully build the OVMS firmware.
In the developer guide it then covers how to flash the box with esptool.
But: do I need to do that? - my OVMS box is up and running already -
I'm guessing I can use OTA update to update with
steve@maximus OVMS.V3 % ls -l build/ovms3.bin -rw-r--r-- 1 steve staff 2986336 Dec 5 12:24 build/ovms3.bin
?
Since the "flash from web" and and "flash from file" are looking for an ovms.bin.
Nervous to brick my box since it was expensive to get it to Cape Town.
By the way, my build prints 'App "ovms3" version: 3.2.015-162-g10232c58-dirty'
I recognise the git commit hash, but what is the "-dirty"?
(I build a "bmwi3" branch of a fork of the original project - maybe that answers my own question?)
My OVMS box currently says it's running "3.2.015/ota_0/main (build idf v3.3.2-881-g22d636b7b Sep 2 2020 08:32:35)"
Thanks, Steve
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
Hi Michael, Thanks for the reply. I was able to flash my build OTA using the web server on my laptop and it's running with no trouble. So far I have added a "stub" for the i3 as per the docs. It is selectable on the OVMS but of course doesn't produce any data. On the i3 you have to send in obd2 requests in order to get data - I think other cars just chatter away unprompted. Is there another vehicle type that works similarly so I can look at the code to see how it should be done? I'm hoping that I can poll the rapidly changing stuff frequently and then the more static pids maybe once a minute or something. Steve On Sat, 5 Dec 2020 at 13:52, Michael Balzer <dexter@expeedo.de> wrote:
Steve,
I know of no case of bricking by flashing the firmware.
Using the developing environment, a simple "make app-flash" will do the esptool call for you.
Of course you can also flash OTA. I usually flash my desk/development module by USB and the one in my car via Wifi from my local server. It's up to you. Flashing OTA can only update the firmware, but that's normally sufficient.
The "-dirty" tag is appended when building from a "dirty" working tree, i.e. one with uncommitted changes.
Regards, Michael
Am 05.12.20 um 11:40 schrieb Steve Davies:
Hi Mark et-al,
I've installed the esp32 and the esp-idf environments on my Mac and successfully build the OVMS firmware.
In the developer guide it then covers how to flash the box with esptool.
But: do I need to do that? - my OVMS box is up and running already -
I'm guessing I can use OTA update to update with
steve@maximus OVMS.V3 % ls -l build/ovms3.bin -rw-r--r-- 1 steve staff 2986336 Dec 5 12:24 build/ovms3.bin
?
Since the "flash from web" and and "flash from file" are looking for an ovms.bin.
Nervous to brick my box since it was expensive to get it to Cape Town.
By the way, my build prints 'App "ovms3" version: 3.2.015-162-g10232c58-dirty'
I recognise the git commit hash, but what is the "-dirty"?
(I build a "bmwi3" branch of a fork of the original project - maybe that answers my own question?)
My OVMS box currently says it's running "3.2.015/ota_0/main (build idf v3.3.2-881-g22d636b7b Sep 2 2020 08:32:35)"
Thanks, Steve
_______________________________________________ OvmsDev mailing listOvmsDev@lists.openvehicles.comhttp://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
Steve, side note: according to the "received" headers it seems you're sending all messages twice, please check your mail client/setup. Most cars have some live status frames (called "process data objects" in CANopen), some need polling. Nearly all car adaptions use OBD polling to retreive extended info. Polling is necessary on the OBD2 variant of the VW e-Up, and IIRC also on the newer Nissan Leaf models. I suggest looking at the e-Up OBD for reference first, as it uses only polling and is simple & clean. Having no status frames means you may also need to poll to detect the vehicle power status, but that may keep the car alive and drain the 12V battery. The e-Up OBD variant uses the 12V level as a hint, maybe that's an option for you as well. Regards, Michael Am 05.12.20 um 14:07 schrieb Steve Davies:
Hi Michael,
Thanks for the reply. I was able to flash my build OTA using the web server on my laptop and it's running with no trouble.
So far I have added a "stub" for the i3 as per the docs. It is selectable on the OVMS but of course doesn't produce any data.
On the i3 you have to send in obd2 requests in order to get data - I think other cars just chatter away unprompted.
Is there another vehicle type that works similarly so I can look at the code to see how it should be done?
I'm hoping that I can poll the rapidly changing stuff frequently and then the more static pids maybe once a minute or something.
Steve
On Sat, 5 Dec 2020 at 13:52, Michael Balzer <dexter@expeedo.de <mailto:dexter@expeedo.de>> wrote:
Steve,
I know of no case of bricking by flashing the firmware.
Using the developing environment, a simple "make app-flash" will do the esptool call for you.
Of course you can also flash OTA. I usually flash my desk/development module by USB and the one in my car via Wifi from my local server. It's up to you. Flashing OTA can only update the firmware, but that's normally sufficient.
The "-dirty" tag is appended when building from a "dirty" working tree, i.e. one with uncommitted changes.
Regards, Michael
Am 05.12.20 um 11:40 schrieb Steve Davies:
Hi Mark et-al,
I've installed the esp32 and the esp-idf environments on my Mac and successfully build the OVMS firmware.
In the developer guide it then covers how to flash the box with esptool.
But: do I need to do that? - my OVMS box is up and running already -
I'm guessing I can use OTA update to update with
steve@maximus OVMS.V3 % ls -l build/ovms3.bin -rw-r--r-- 1 steve staff 2986336 Dec 5 12:24 build/ovms3.bin
?
Since the "flash from web" and and "flash from file" are looking for an ovms.bin.
Nervous to brick my box since it was expensive to get it to Cape Town.
By the way, my build prints 'App "ovms3" version: 3.2.015-162-g10232c58-dirty'
I recognise the git commit hash, but what is the "-dirty"?
(I build a "bmwi3" branch of a fork of the original project - maybe that answers my own question?)
My OVMS box currently says it's running "3.2.015/ota_0/main (build idf v3.3.2-881-g22d636b7b Sep 2 2020 08:32:35)"
Thanks, Steve
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com <mailto:OvmsDev@lists.openvehicles.com> http://lists.openvehicles.com/mailman/listinfo/ovmsdev <http://lists.openvehicles.com/mailman/listinfo/ovmsdev>
_______________________________________________ OvmsDev mailing list OvmsDev@lists.openvehicles.com http://lists.openvehicles.com/mailman/listinfo/ovmsdev
-- Michael Balzer * Helkenberger Weg 9 * D-58256 Ennepetal Fon 02333 / 833 5735 * Handy 0176 / 206 989 26
participants (2)
-
Michael Balzer -
Steve Davies