You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Possible minor error on the documentation related with the ROM usage #243
I am not sure, but I think that I have found a minor error on the documentation related with the ROM usage, to be precise under “Command Line Usage”.
In the part where it says:
“
To run macros, it is suggested to use, for example:
cd OpenRAM/macros/rom_configs
make sky130_rom_1kbyte
”
If I blindly follow what it says, I receive a make error. That seems to be caused by the fact that make file is inside “OpenRAM/macros/” while the configuration is inside “OpenRAM/macros/rom_configs”.
Therefore, “make sky130_rom_1kbyte” command works on the “macros” folder but not on the “rom_configs” folder.
I think that it should say:
"
To run macros, it is suggested to use, for example:
cd OpenRAM/macros/
make sky130_rom_1kbyte
"
Again, I am not sure if it is an error on the documentation.
Closing as stale. This has been inactive for 2.4 years and there is no current reproduction against dev, so it is not actionable as it stands.
If the documentation error is still present, the exact file and line in a fresh issue or a one-line PR would be the fastest route.
To be clear, this is being closed for inactivity rather than rejected. If it still affects you, please reopen or file a fresh issue with a reproduction against current dev, including your configuration file, technology, OS and python3 --version, and the contents of the temp directory OpenRAM leaves behind on failure (the FAQ explains which files those are).
If you would like to fix it yourself, a PR would be very welcome and we will review and consider it — see CONTRIBUTING.md. Contributions go to the dev branch.
Activity
mguthaus commentedon Oct 13, 2026
Closing as stale. This has been inactive for 2.4 years and there is no current reproduction against
dev, so it is not actionable as it stands.If the documentation error is still present, the exact file and line in a fresh issue or a one-line PR would be the fastest route.
To be clear, this is being closed for inactivity rather than rejected. If it still affects you, please reopen or file a fresh issue with a reproduction against current
dev, including your configuration file, technology, OS andpython3 --version, and the contents of the temp directory OpenRAM leaves behind on failure (the FAQ explains which files those are).If you would like to fix it yourself, a PR would be very welcome and we will review and consider it — see CONTRIBUTING.md. Contributions go to the
devbranch.