Remove esp_binary_optimize tool
No real esptool operation backs "optimize firmware binary". Size optimization happens at compile-time via ESP-IDF menuconfig, not as a post-processing step on a .bin file. The analysis use case is already covered by esp_firmware_analyze.
This commit is contained in:
parent
f2f2dbd5eb
commit
9810d35637
@ -38,13 +38,6 @@ class FirmwareBuilder:
|
|||||||
"""Analyze firmware binary structure"""
|
"""Analyze firmware binary structure"""
|
||||||
return {"success": True, "note": "Implementation coming soon"}
|
return {"success": True, "note": "Implementation coming soon"}
|
||||||
|
|
||||||
@self.app.tool("esp_binary_optimize")
|
|
||||||
async def optimize_binary(
|
|
||||||
context: Context, input_path: str, output_path: str
|
|
||||||
) -> dict[str, Any]:
|
|
||||||
"""Optimize firmware binary for size/performance"""
|
|
||||||
return {"success": True, "note": "Implementation coming soon"}
|
|
||||||
|
|
||||||
async def health_check(self) -> dict[str, Any]:
|
async def health_check(self) -> dict[str, Any]:
|
||||||
"""Component health check"""
|
"""Component health check"""
|
||||||
return {"status": "healthy", "note": "Firmware builder ready"}
|
return {"status": "healthy", "note": "Firmware builder ready"}
|
||||||
|
|||||||
@ -169,7 +169,7 @@ class ESPToolServer:
|
|||||||
"esp_efuse_read",
|
"esp_efuse_read",
|
||||||
"esp_efuse_burn",
|
"esp_efuse_burn",
|
||||||
],
|
],
|
||||||
"firmware": ["esp_elf_to_binary", "esp_firmware_analyze", "esp_binary_optimize"],
|
"firmware": ["esp_elf_to_binary", "esp_firmware_analyze"],
|
||||||
"ota": ["esp_ota_package_create", "esp_ota_deploy", "esp_ota_rollback"],
|
"ota": ["esp_ota_package_create", "esp_ota_deploy", "esp_ota_rollback"],
|
||||||
"production": ["esp_factory_program", "esp_batch_program", "esp_quality_control"],
|
"production": ["esp_factory_program", "esp_batch_program", "esp_quality_control"],
|
||||||
"diagnostics": [
|
"diagnostics": [
|
||||||
|
|||||||
Loading…
x
Reference in New Issue
Block a user