Self checks
ECC version
v0.1.0.alpha.9
Affected area
Flow/runtime
How did you get ECC?
Release PyInstaller bundle
Where are you running ECC?
Native Linux
Environment
ubuntu 22.04
Toolchain, PDK, and dependency context
ecc v0.1.0-alpha.9 (binary reports 0.1.0a6; dist-info confirms 0.1.0a9)
Steps to reproduce
When fp_default_config.json specifies macro_location_path as a relative path (e.g. "macro_locations.txt"), the run bootstrap
copies a 0-byte placeholder to runs//config/macro_locations.txt instead of resolving the path against the project root and
copying the actual file. The MacroPlacer then reads the empty file, places nothing, and completes instantly. Macros end up
collapsed at the die origin, overlapping each other.
Steps to reproduce:
- ecc init a project, create macro_locations.txt with valid coordinates in the project root
- In fp_default_config.json, leave "macro_location_path": "macro_locations.txt" (relative)
- Run ecc run --project .
Expected behavior
Expected: ECC resolves macro_locations.txt relative to the project directory and copies the actual file (145 bytes, 2 macro
entries) into the run config.
Actual behavior
Actual: ECC creates a 0-byte empty file:
$ wc -c macro_locations.txt # project root
145 macro_locations.txt
$ wc -c runs/u07_d08/config/macro_locations.txt # run config
0 macro_locations.txt
Logs or command output
Floorplan log:
MacroPlacer.cpp:56 place] Starting...
MacroPlacer.cpp:65 place] Completed (elapsed = 00:00:00)
Result: macros stacked at lower-left corner, overlapping.
Workaround: Use an absolute path in fp_default_config.json:
"macro_location_path": "/absolute/path/to/project/macro_locations.txt"
Additional context
No response
Self checks
ECC version
v0.1.0.alpha.9
Affected area
Flow/runtime
How did you get ECC?
Release PyInstaller bundle
Where are you running ECC?
Native Linux
Environment
ubuntu 22.04
Toolchain, PDK, and dependency context
ecc v0.1.0-alpha.9 (binary reports 0.1.0a6; dist-info confirms 0.1.0a9)
Steps to reproduce
When fp_default_config.json specifies macro_location_path as a relative path (e.g. "macro_locations.txt"), the run bootstrap
copies a 0-byte placeholder to runs//config/macro_locations.txt instead of resolving the path against the project root and
copying the actual file. The MacroPlacer then reads the empty file, places nothing, and completes instantly. Macros end up
collapsed at the die origin, overlapping each other.
Steps to reproduce:
Expected behavior
Expected: ECC resolves macro_locations.txt relative to the project directory and copies the actual file (145 bytes, 2 macro
entries) into the run config.
Actual behavior
Actual: ECC creates a 0-byte empty file:
$ wc -c macro_locations.txt # project root
145 macro_locations.txt
$ wc -c runs/u07_d08/config/macro_locations.txt # run config
0 macro_locations.txt
Logs or command output
Floorplan log:
MacroPlacer.cpp:56 place] Starting...
MacroPlacer.cpp:65 place] Completed (elapsed = 00:00:00)
Result: macros stacked at lower-left corner, overlapping.
Workaround: Use an absolute path in fp_default_config.json:
"macro_location_path": "/absolute/path/to/project/macro_locations.txt"
Additional context
No response