Thanks! The trick with the esptool.py is what i was looking for. Looking at partitions.csv, the offset for OTA_0 is 0x10000 + 4MByte?


# OVMS 16MB flash ESP32 Partition Table
# Name,   Type, SubType, Offset,   Size
nvs,      data, nvs,     0x9000,  0x4000
otadata,  data, ota,     0xd000,  0x2000
phy_init, data, phy,     0xf000,  0x1000
factory,  app,  factory, 0x10000,  4M
ota_0,    app,  ota_0,   ,         4M
ota_1,    app,  ota_1,   ,         4M
store,    data, fat,     ,         1M

Thanks,
Eddy
From: OvmsDev <ovmsdev-bounces@lists.openvehicles.com> on behalf of Mark Webb-Johnson <mark@webb-johnson.net>
Sent: Wednesday, April 22, 2020 2:28 PM
To: OVMS Developers <ovmsdev@lists.openvehicles.com>
Subject: Re: [Ovmsdev] make apt-flash destination location?
 

The app-flash always flashes the ‘factory’ partition. If you ‘make flash’ it will also overwrite the bootloader, partition table, and switch back to factory for you.

You can also tell the module to boot from factory with ‘ota boot factory’ (and ota_0, ota_1 for the ota partitions).

Regards, Mark.

P.S. You can manually flash (using the esptool.py script) to a specific partition, using partitions.csv to tell you the offsets.

On 22 Apr 2020, at 2:23 PM, Eddy Vromen <eddy_vromen@hotmail.com> wrote:




Hi All,

Quick question:  I am experimenting with some code changes and i am using the sdcard method to get a new  .bin file on the device. It will automatically alternate between the 2 OTA image loactions which is great.
I would like to make this process a little less labor intensive:
When i use "make apt-flash", where does the code get flashed? With this method, how can i pick between the 2 OTA image locations?

Thanks,
Eddy




_______________________________________________
OvmsDev mailing list
OvmsDev@lists.openvehicles.com
http://lists.openvehicles.com/mailman/listinfo/ovmsdev