ShoH_Altera
Occasional ContributorJoined 5 years ago
User Profile
Occasional ContributorUser Widgets
Contributions
Re: Preloader/U-Boot Compilation Failure
Hi IOzan , So, the 'sed: cannot rename .../sedXXXXXX: Permission denied' error still occurs after all. Since this error is typically caused by environment‑specific factors within the Cygwin layer on Windows — such as file‑locking behavior, antivirus interference, or permission propagation — it is hard to offer a certain solution, unfortunately. That said, try a few additional tests ? Create a new spl_bsp directory in a location where you have full read/write permissions, preferably in a new folder on C: drive, and run make. Does this attempt generate exactly the same error log? (Try this several times.) ( Alternatively, you might consider abandoning Cygwin on your Windows environment and building it in a Linux environment instead.... ) Thanks, ShoRe: Preloader/U-Boot Compilation Failure
Hi IOzan , Thank you for sending the tool information, your work details, and the error logs. First, I would like to note that the version you are using, 18.1std, has already reached the end of support, and it is recommended to use the latest version, 25.1std. (However, I understand that there may be cases where you need to use this older version for various reasons...) I believe the root cause of the issue you are facing is that an error is occurring in the tar command. tar: Error opening archive: Failed to open '/cygdrive/c/intelFPGA/....' To address this root cause, please try modifying the Makefile as follows: 1. Re‑generate the spl_bsp folder and start from the original Makefile. 2. On the line following line 93, which contains ifeq ($(HOSTOS),cygwin), add the following one line: UNTAR := $(SOCEDS_DEST_ROOT)/host_tools/cygwin/bin/tar zxf Then run make. This modification does not change the value of the TGZ variable; rather, it explicitly forces the build process to use the tar command installed in the SoC EDS Cygwin environment. Please let me know if this Makefile modification resolves the issue. Thanks, ShoRe: Ahsling RiscFree IDE 25.1.1: Unresolved inclusion
Hi Frank, FvM First, As you may already know, RiscFree is based on Eclipse C/C++ Development Toolkit (CDT), and these "unresolved inclusion" messages are from Indexer, which is a component of Eclipse. Indexer parses and analyzes your project files to help your source code exploration in GUI. So these warnings are not related the build process for your binary and the build process can be successfully completed regardless the messages. (Back to the main topic) As you pointed out, fully automatic resolution of Indexer search path settings is not supported yet in RiscFree today, unfortunately. However, We can resolve "unresolved inclusion" issue by manually setting the search path for Indexer. To search files in BSP project: After you have imported both the application and BSP project: Right-click on the application project in Project Explorer Select Properties Navigate to the Project References tab Check the option box for the BSP project, then click Apply and Close To search C/C++ libraries: (This is how I workaround...) Add the default RISC-V gcc include file search paths into project properties. To do this, import the xml explained in my next post with the following steps. The xml file is an example for 25.1.1 RiscFree running on Windows PC, so named as include_search_path_25.1.1_win.xml. Right-click on the application project in Project Explorer Select Import... Select C/C++ -> C/C++ Project Settings, then click Next Click Browse..., then select the attached xml file: include_search_path_25.1.1_win.xml Click Finish After these setup, there is no "unresolved inclusion" in my RiscFree. Hope this helps, Sho
