add informations and a production env example

This commit is contained in:
1technophile committed 2019-08-25 20:35:30 +02:00
1 parent 9fc2609bba
commit 1ce1fe30dd
2 files changed
+48

No files matched your search

+5
View File
@@ -20,6 +20,11 @@ extra_configs =
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;Uncomment the env line corresponding to your board and modules required, ;
;you can also adapt the modules by removing the corresponding lines in the env detail ;
; if you go to the build flag section of your env you will see that some user_config.h ;
; parameters can be overwritten here, for example the gateway name. ;
; If you want to avoid the lost of your environments at each update you can put them ;
; into a separate file called prod_env.ini, it will be automatically read by pio ;
; an example (prod_env.ini.example) is available into the same folder as this file. ;
;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;
;default_envs = sonoff-basic-rfr3
+43
View File
@@ -0,0 +1,43 @@
[platformio]
default_envs =
esp32dev-ble-1
esp32dev-ble-2
;esp32 1
[env:esp32dev-ble-1]
platform = ${com.esp32_platform}
board = esp32dev
board_build.partitions = min_spiffs.csv
lib_deps =
${com-esp.lib_deps}
${libraries.ble}
build_flags =
${com-esp.build_flags}
'-DZgatewayBT="BT"'
'-DGateway_Name="OpenMQTTGateway_ESP32_1"'
upload_protocol = espota
upload_port = 192.168.1.82
upload_flags =
--auth=OTAPASSWORD
upload_speed = 512000
monitor_speed = 115200
;esp32 2
[env:esp32dev-ble-2]
platform = ${com.esp32_platform}
board = esp32dev
board_build.partitions = min_spiffs.csv
lib_deps =
${com-esp.lib_deps}
${libraries.ble}
build_flags =
${com-esp.build_flags}
'-DZgatewayBT="BT"'
'-DGateway_Name="OpenMQTTGateway_ESP32_2"'
;-DCORE_DEBUG_LEVEL=4
upload_protocol = espota
upload_port = 192.168.1.111
upload_flags =
--auth=OTAPASSWORD
upload_speed = 512000
monitor_speed = 115200