Link path correction
This commit is contained in:
parent
fe218fc207
commit
509c1d2c80
|
@ -18,7 +18,7 @@ dir_keyword="GENERATED_DIR_KEYWORD"
|
|||
rm -rf ${pwd_path}/results_OpenPithon
|
||||
|
||||
cd ${pwd_path}/arch
|
||||
mkdir generated # create folder to save rewritten architecture
|
||||
mkdir -p generated # create folder to save rewritten architecture
|
||||
cd ${pwd_path}/scripts
|
||||
|
||||
# Replace keyword in config and architecture files
|
||||
|
|
|
@ -93,4 +93,4 @@ Once dependancies are understood, we can modify the flow by changing the archite
|
|||
|
||||
### Explanation
|
||||
|
||||
With this last experiment we replace the [**K6 architecture**](https://github.com/LNIS-Projects/OpenFPGA/blob/master/tutorials/image/architectures_schematics/frac_lut6.pdf) with a [**K8 architecture**](https://github.com/LNIS-Projects/OpenFPGA/blob/master/tutorials/image/architectures_schematics/frac_lut8.pdf), which means a 8-inputs fracturable LUT (implemented by LUT6 and LUT4 with 2 shared inputs). This architecture provides more modes for the CLB and the crossbar changed from a half-connected to a fully connected, implying bigger multiplexor between the CLB and LUT inputs. These requirement in term of interconnection will lead to the increase in routing channel width. Indeed, if the routing channel is to low, it could be impossible to route a benchmark or the FPGA output can be delayed.
|
||||
With this last experiment we replace the [**K6 architecture**](https://github.com/LNIS-Projects/OpenFPGA/blob/master/tutorials/images/architectures_schematics/frac_lut6.pdf) with a [**K8 architecture**](https://github.com/LNIS-Projects/OpenFPGA/blob/master/tutorials/images/architectures_schematics/frac_lut8.pdf), which means a 8-inputs fracturable LUT (implemented by LUT6 and LUT4 with 2 shared inputs). This architecture provides more modes for the CLB and the crossbar changed from a half-connected to a fully connected, implying bigger multiplexor between the CLB and LUT inputs. These requirement in term of interconnection will lead to the increase in routing channel width. Indeed, if the routing channel is to low, it could be impossible to route a benchmark or the FPGA output can be delayed.
|
||||
|
|
Loading…
Reference in New Issue