2018-07-13 07:52:25 -05:00
|
|
|
|
2020-07-02 17:23:03 -05:00
|
|
|
OBJS += techlibs/ecp5/synth_ecp5.o techlibs/ecp5/ecp5_gsr.o
|
2018-07-13 07:52:25 -05:00
|
|
|
|
2019-08-30 05:05:09 -05:00
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/cells_ff.vh))
|
|
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/cells_io.vh))
|
2018-07-13 07:52:25 -05:00
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/cells_map.v))
|
|
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/cells_sim.v))
|
2018-10-21 13:27:02 -05:00
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/cells_bb.v))
|
2019-07-16 15:44:55 -05:00
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/lutrams_map.v))
|
Harmonize BRAM/LUTRAM descriptions across all of Yosys.
This commit:
* renames all remaining instances of "DRAM" (which is ambiguous)
to "LUTRAM" (which is not), finishing the work started in
the commit 698ab9be;
* renames memory rule files to brams.txt/lutrams.txt;
* adds/renames script labels map_bram/map_lutram;
* extracts where necessary script labels map_ffram and map_gates;
* adds where necessary options -nobram/-nolutram.
The end result is that BRAM/LUTRAM/FFRAM aspects of every target
are now consistent with each other.
Per architecture:
* anlogic: rename drams.txt→lutrams.txt, add -nolutram, add
:map_lutram, :map_ffram, :map_gates
* ecp5: rename bram.txt→brams.txt, lutram.txt→lutrams.txt
* efinix: rename bram.txt→brams.txt, add -nobram, add :map_ffram,
:map_gates
* gowin: rename bram.txt→brams.txt, dram.txt→lutrams.txt,
rename -nodram→-nolutram (-nodram still recognized), rename
:bram→:map_bram, :dram→:map_lutram, add :map_ffram, :map_gates
2020-01-01 06:30:00 -06:00
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/lutrams.txt))
|
2018-10-10 10:35:19 -05:00
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/brams_map.v))
|
Harmonize BRAM/LUTRAM descriptions across all of Yosys.
This commit:
* renames all remaining instances of "DRAM" (which is ambiguous)
to "LUTRAM" (which is not), finishing the work started in
the commit 698ab9be;
* renames memory rule files to brams.txt/lutrams.txt;
* adds/renames script labels map_bram/map_lutram;
* extracts where necessary script labels map_ffram and map_gates;
* adds where necessary options -nobram/-nolutram.
The end result is that BRAM/LUTRAM/FFRAM aspects of every target
are now consistent with each other.
Per architecture:
* anlogic: rename drams.txt→lutrams.txt, add -nolutram, add
:map_lutram, :map_ffram, :map_gates
* ecp5: rename bram.txt→brams.txt, lutram.txt→lutrams.txt
* efinix: rename bram.txt→brams.txt, add -nobram, add :map_ffram,
:map_gates
* gowin: rename bram.txt→brams.txt, dram.txt→lutrams.txt,
rename -nodram→-nolutram (-nodram still recognized), rename
:bram→:map_bram, :dram→:map_lutram, add :map_ffram, :map_gates
2020-01-01 06:30:00 -06:00
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/brams.txt))
|
2018-07-13 08:46:12 -05:00
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/arith_map.v))
|
2018-10-18 13:39:48 -05:00
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/latches_map.v))
|
2019-07-08 09:40:12 -05:00
|
|
|
$(eval $(call add_share_file,share/ecp5,techlibs/ecp5/dsp_map.v))
|
