Xiangfu Liu wrote:
> map -ol high -t 20 -w system.ngd -o system1.ncd Great.
Whee !
> map -ol high -t 80 -w system.ngd -o system4.ncd Great
Another one ! Whee ! :-)
> map -ol high -t 99 -w system.ngd -o system5.ncd False. but kind of cool.
Pictures ? ;-)
> The -t 20 and -t 80 both works fine. which one do you think is better?
As I understand this, there's no "better" here. It's just a random
number. Some will work, some not. Change one line anywhere in the
SoC and the number that worked before may no longer work but one
that didn't work before will be okay.
> -all: $(BUILDDIR)/system.bit $(BUILDDIR)/system.fpg
> +all: $(BUILDDIR)/system.bit $(BUILDDIR)/system.fpg \
> + $(BUILDDIR)/system0.bit $(BUILDDIR)/system0.fpg \
> + $(BUILDDIR)/system1.bit $(BUILDDIR)/system1.fpg \
> + $(BUILDDIR)/system2.bit $(BUILDDIR)/system2.fpg \
> + $(BUILDDIR)/system3.bit $(BUILDDIR)/system3.fpg \
> + $(BUILDDIR)/system4.bit $(BUILDDIR)/system4.fpg \
> + $(BUILDDIR)/system5.bit $(BUILDDIR)/system5.fpg \
Will this run a total of six builds for "make soc.fg" ? If yes,
that wouldn't be so nice.
> +$(BUILDDIR)/system0.bit: $(BUILDDIR)/system-routed0.ncd
> + cd $(BUILDDIR) && bitgen -g LCK_cycle:6 -g Binary:Yes -g INIT_9K:Yes -w
> system-routed0.ncd system0.bit
Couldn't you do this with something like this ?
$(BUILDDIR)/system%.bit: $(BUILDDIR)/system-routed%.ncd
cd $(BUILDDIR) && bitgen -g LCK_cycle:6 -g Binary:Yes \
-g INIT_9K:Yes -w `basename $<` `basename $@`
I suppose you couldn't get rid of the directory change because of
temp files left by the tools ? Because if you can control/avoid
temp files, then this could even become as simple as
$(BUILDDIR)/system%.bit: $(BUILDDIR)/system-routed%.ncd
bitgen -g LCK_cycle:6 -g Binary:Yes -g INIT_9K:Yes -w $< $@
There's a lot of redundancy in common.mak even without -t.
$< and $@ are your friends :-)
- Werner
_______________________________________________
http://lists.milkymist.org/listinfo.cgi/devel-milkymist.org
IRC: #milkymist@Freenode
