Whether compiling the main branch or the 2.11 branch, there are multiple similar errors indicating duplicate definitions as shown below:
Building compilation database build_sf32-oed-epd_v11_hcpu\bootloader\compile_commands.json
C:/Users/sunwo/.sifli/tools/arm-none-eabi-gcc/14.2.1/bin/../lib/gcc/arm-none-eabi/14.2.1/../../../../arm-none-eabi/bin/ld.exe: build_sf32-oed-epd_v11_hcpu\bootloader\sifli_sdk\customer\boards\sf32-oed-epd_v11\base\bsp_init.o: in function BSP_GetFlash1DIV': F:\\github\\EPD_Reader\\SiFli-SDK\\customer\\boards\\sf32-oed-epd_base/bsp_init.c:26: **multiple definition** of BSP_GetFlash1DIV`;
build_sf32-oed-epd_v11_hcpu\bootloader\sifli_sdk\customer\boards\sf32-oed-epd_base\bsp_init.o:F:\github\EPD_Reader\SiFli-SDK\customer\boards\sf32-oed-epd_base/bsp_init.c:26: first defined here
Previously, .\install.ps1 and .\export.ps1 were executed successfully.
Are you compiling using the SDK pulled from the e-ink screen project? If not, please re-fetch it, then run the command below to set up the environment and proceed with compilation.
Yes, I’m using the SDK from the engineering-specified submodule. I’ll try again with the provided command. Thanks.
Currently, on various platforms, there are almost no successful application examples of this e-ink display kit. I’ve asked several other developers, and they’re also stuck on environment setup and project compilation.
I’m directly pulling the GitHub code (command as below), then running install.ps1 under sdk, followed by export.ps1 to launch the environment. After that, I go into the project directory and compile using scons --board=sf32-oed-epd_v11 --board_search_path=.. -j8, and I haven’t encountered the error you mentioned. You could try deleting the build files first and recompiling. If it still doesn’t work, please let me know which version branch you’re using so I can try to reproduce it. By the way, I’m currently using the main branch.
Also, did you make any modifications? Normally, the sf32-oed-epd_base file shouldn’t exist in the path below—did you add it yourself? If so, you could try deleting it first and then testing again.
