This is regarding pin_order.cfg file for user_proj_example. I got the following error with my exampl...
l
This is regarding pin_order.cfg file for user_proj_example. I got the following error with my example project. _*Valid directives are #N, #E, #S, or #W. Append R for reversing the default order. Use #BUS_SORT to group 'bus bits' by index. Please make sure you have set a valid side first before listing pins*_ child process exited abnormally Is there a document where I can refer to know more about the #N/E/S/W/R and $BUS_SORT. How to write pin_order.cfg file? wb_.* etc. mean what?
v
can you post your pin_order.cfg here?
l
Here is the pin order #BUS_SORT #S wb_.* wbs_.* la_.* irq.* #N io_.* #USER DEFINED user_.* data_.* addr_.* soc_.* en_.* rw_.*
v
@Lab Lecture #USER DEFINED is wrong location to place. Remove that from the file
l
Ok. But what are the allowed #s? What are there significance?
v
"#E", "#S", "#W", "#NR", "#ER", "#SR", "#WR", "#BUS_SORT", "#N",
l
Thanks. What do they mean? If I have a new pin which # should I use?
v
Place your pins only above directions.
l
With the new tag "mpw-7a" all the pins must be listed in pin_order.cfg. Otherwise, the flow fails. Earlier, it was ok not to list all the pins.
v
Yes its was made mandatory to define all pins. After #N just define pin names. flow will pass
Else remove the following variable from
config.tcl
, so openlane by default place all pins.
set ::env(FP_PIN_ORDER_CFG) $script_dir/pin_order.cfg
103 Views