Tasmota

Commit Graph

Author	SHA1	Message	Date
Dellucifer	f45b55a18b	Rectified Typos (#19841 ) * Rectified Typos * Update settings.json	2023-10-26 18:04:34 +02:00
Jason2866	30521027ab	Keep FS intact when over flashing with VSC (#403 ) (#19816 )	2023-10-22 17:10:59 +02:00
Jason2866	10821b7e24	fix factory file not removed (#18761 )	2023-05-31 21:54:59 +02:00
Jason2866	ec00f0f7e2	esp8266 iram metrics (#18564 )	2023-05-03 11:04:10 +02:00
Jason2866	112c254d54	refac firmware-metrics (#18466 ) * refac firmware-metrics * rm debugging print * fix esp8266	2023-04-21 16:56:27 +02:00
Jason2866	ca88aa2519	fix c3 map metrics (#18465 )	2023-04-21 14:24:29 +02:00
Jason2866	49d5356ea3	Show Metrics for ESP32x firmware (#18461 )	2023-04-20 20:26:07 +02:00
Jason2866	11645705e3	Flash firmware without `run build` (#18233 ) * Flash without build * Use firmwares from `build_output` * simulate build with firmware from `build_output` * rm debug code	2023-03-21 14:56:24 +01:00
Jason2866	c574e24cad	minor clean up in scripts (#17483 )	2022-12-22 17:50:40 +01:00
Jason2866	12ecfae94d	copy factory firmware to `build_output`	2022-01-05 23:14:49 +01:00
Sillyfrog	7dd7cf71a0	Refactor Python PIO tools	2021-08-16 20:37:38 +10:00
Jason2866	4209f7d1cb	Final? fix for map file with IDF4.4	2021-08-09 18:34:09 +02:00
Jason2866	18442c7e57	next try for IDF 4.4 map file building #12837 @arendst @sillyfrog give it a try. I am a Python noob... The `map_name` generating is problematic. Better would be to use last entry of the string `src_dir`.	2021-08-09 16:27:22 +02:00
Jason2866	0ce68b1b6b	Fixes #12837 With the new toolchain used with IDF 4.4 the MAP file is in a different folder and the name has changed (from firmware.map to Tasmota.map). Now name-firmware.py is searching for both-	2021-08-08 13:35:17 +02:00
Barbudor	1694087a28	Rename pio folder to pio-tools solve linux build errors When vscode is ran from the Tasmota folder in Linux, build fails with message : ```Executing task: pio run < The terminal process failed to launch: Path to shell executable "pio" is not a file of a symlink.``` Renaming pio folder into pio-tools solve the problem. Note: the problem can still occur if the user have a pio folder in his PATH...	2020-11-17 22:01:42 +01:00

15 Commits