08-05-2019 12:30 AM - edited 08-05-2019 01:26 AM
Hello,
while trying to compile a project in SDAccel I get the following error. The makefile was machine-generated. I tried deleting the ip_cache directory both from the makefile and the actual disk, but neither worked(kept reappearing in the makefile and got stuck when deleting from disk) Can someone help me out? I'm using 2018.2 on Ubuntu 16.04.6. I guess emptying the cache might help, but that post was for Vivado, and I can't find the equivalents in SDAccel.
ERROR: [XOCC 60-603] Source file is a directory: /home/myname/workspace/ip_cache
ERROR: [XOCC 60-623] Unsupported input file type specified.
makefile:77: recipe for target 'binary_container_1.xclbin' failed
make: *** [binary_container_1.xclbin] Error 1
This is the makefile of the primary build part
.PHONY: all clean
all: $(BINARY_CONTAINERS) $(HOST_EXE)
.NOTPARALLEL: clean
clean:
-$(RM) $(BINARY_CONTAINERS) $(ALL_KERNEL_OBJS) $(ALL_MESSAGE_FILES) $(HOST_EXE) $(HOST_OBJECTS)
-$(RM) *.xclbin.sh
-$(RMDIR) $(BUILD_SUBDIRS)
-$(RMDIR) _xocc*
-$(RMDIR) .Xil
.PHONY: incremental
incremental: all
nothing:
#
# binary container: binary_container_1.xclbin
#
binary_container_1/krnl_vadd.xo: ../src/krnl_vadd.cl
@mkdir -p $(@D)
-@$(RM) $@
$(XOCC) $(XOCC_OPTS) -c -k krnl_vadd --nk krnl_vadd:1:krnl_vadd_1 --messageDb $(subst .xo,.mdb,$@) -I"$(<D)" --xp misc:solution_name=krnl_vadd --temp_dir binary_container_1 --report_dir binary_container_1/reports --log_dir binary_container_1/logs -o"$@" "$<"
binary_container_1.xclbin: $(BINARY_CONTAINER_1_OBJS)
-@echo $(XOCC) $(XOCC_OPTS) -l --nk krnl_vadd:1:krnl_vadd_1 --messageDb $(subst .xclbin,.mdb,$@) --xp misc:solution_name=link --temp_dir binary_container_1 --report_dir binary_container_1/reports --log_dir binary_container_1/logs --profile_kernel --remote_ip_cache /home/myname/workspace/ip_cache -o"$@" $(+) > binary_container_1.xclbin.sh
$(XOCC) $(XOCC_OPTS) -l --nk krnl_vadd:1:krnl_vadd_1 --messageDb $(subst .xclbin,.mdb,$@) --xp misc:solution_name=link --temp_dir binary_container_1 --report_dir binary_container_1/reports --log_dir binary_container_1/logs --profile_kernel --remote_ip_cache /home/myname/workspace/ip_cache -o"$@" $(+)
08-05-2019 01:26 AM - edited 08-05-2019 01:29 AM
Hi, @jsyoo1117 ,
SDAccel will just call Vivado, so the "set_param" method for clean IP cache will still work.
Using the --xp XOCC compiler switch can help to pass the paramter.
08-05-2019 01:25 AM
Sorry, solved the problem myself. I don't know why, but creating the project directory right under workspace caused the problem. Creating a subdirectory, such as ~/workspace/test/myproject solved the problem beautifully. Not deleting this post for future demand.
08-05-2019 01:26 AM - edited 08-05-2019 01:29 AM
Hi, @jsyoo1117 ,
SDAccel will just call Vivado, so the "set_param" method for clean IP cache will still work.
Using the --xp XOCC compiler switch can help to pass the paramter.
08-05-2019 01:33 AM
@hongh wrote:Hi, @jsyoo1117 ,
SDAccel will just call Vivado, so the "set_param" method for clean IP cache will still work.
Using the --xp XOCC compiler switch can help to pass the paramter.
Well that was obvious... Thx for the comment!