Issues setting up Development environment
Posted: Sat Apr 03, 2021 3:21 pm
I have encountered a number of problems (some admittedly self-inflicted) trying to set up the development environment for a QuickFeather development kit, using the video at https://www.quicklogic.com/products/eos ... pment-kit/
I am working on Win10 Pro, and I am able to successfully connect to the QuickFeather and run the diagnostic demo.
I am now at the point where the example project from the video builds (32 warnings, vs 12 in the video, but I am using a later version of Eclipse and tools).
However, when I attempt to debug after a successful build, the second build fails immediately, with:
A pop-up message appears, with a choice to proceed or cancel. If I choose to proceed, J-Link fails to connect.
The first problem (build failure) I have no clue how to resolve. I see the source file in the folder, and a Makefile_Startup, but the hierarchy of dependencies to build the example are a rat's nest, to put it mildly.
EDIT-1: After reviewing some other related posts, there is a discrepancy between posts here and instructions in the video when dragging and dropping the example project files.
In the video, the instructions are very specific - when dragging/dropping, select Link to files and folders.
In other posts here, the instruction is to Link to files and recreate folder structure with virtual folders.
While the arcane structure of makefiles is a mystery, it seems to me that both options cannot magically be correct. So which is correct?
EDIT-2: On the face of it, the \ between c and : in the make Target, which appears in the xxxx.d files produced during the first build, is causing the problem. But I have been unable to find where the \ is coming from. It appears something in the ARM tool chain generates the *.d files and must be inserting the extraneous \. I would appreciate a makefile guru chiming in here.
Regarding the debugger, a major, IMHO, problem with the video is that it does not mention HOW to install the SEGGER debugger – it only references confirming that wherever it is installed correctly appears in the Eclipse settings. I have worked with other boards that use it (e.g. STMicro, Maxim) and have never had to install any J-Link debugger software separately, so that was an aggravating side jaunt. Development for those boards also relies on the (byzantine) Eclipse framework, and examples work 'out-of-the-box' without needing to separately install SEGGER.
My questions:
1 Any suggestions on resolving the build issue? Why does the first build succeed but the following build (ostensibly the same) fail?
2 Is it necessary to insert jumpers on one or both of J1 and J7? If so, which? This was also not addressed in the video – which by its name I expected to cover all details of getting the development environment set up.
Thanks,
Jack Copper
I am working on Win10 Pro, and I am able to successfully connect to the QuickFeather and run the diagnostic demo.
I am now at the point where the example project from the video builds (32 warnings, vs 12 in the video, but I am using a later version of Eclipse and tools).
However, when I attempt to debug after a successful build, the second build fails immediately, with:
Code: Select all
make: Entering directory `C:/qorc-sdk/qf_apps/qf_ssi_ai_app/GCC_Project'
A subdirectory or file output\depend already exists.
make: [_makedirs_] Error 1 (ignored)
A subdirectory or file output already exists.
make: [_makedirs_] Error 1 (ignored)
make -f makefiles/Makefile_Startup
make[1]: Entering directory `C:/qorc-sdk/qf_apps/qf_ssi_ai_app/GCC_Project'
make[1]: *** No rule to make target `c\:\qorc-sdk\hal\startup\startup_eoss3b_gcc.c', needed by `output/startup_EOSS3B_GCC.o'. Stop.
make[1]: Leaving directory `C:/qorc-sdk/qf_apps/qf_ssi_ai_app/GCC_Project'
make: *** [Startup] Error 2
make: Leaving directory `C:/qorc-sdk/qf_apps/qf_ssi_ai_app/GCC_Project'
"make -C C:\qorc-sdk\qf_apps\qf_ssi_ai_app\GCC_Project\Eclipse_Make_Project/../ all" terminated with exit code 2. Build might be incomplete.
The first problem (build failure) I have no clue how to resolve. I see the source file in the folder, and a Makefile_Startup, but the hierarchy of dependencies to build the example are a rat's nest, to put it mildly.
EDIT-1: After reviewing some other related posts, there is a discrepancy between posts here and instructions in the video when dragging and dropping the example project files.
In the video, the instructions are very specific - when dragging/dropping, select Link to files and folders.
In other posts here, the instruction is to Link to files and recreate folder structure with virtual folders.
While the arcane structure of makefiles is a mystery, it seems to me that both options cannot magically be correct. So which is correct?
EDIT-2: On the face of it, the \ between c and : in the make Target, which appears in the xxxx.d files produced during the first build, is causing the problem. But I have been unable to find where the \ is coming from. It appears something in the ARM tool chain generates the *.d files and must be inserting the extraneous \. I would appreciate a makefile guru chiming in here.
Regarding the debugger, a major, IMHO, problem with the video is that it does not mention HOW to install the SEGGER debugger – it only references confirming that wherever it is installed correctly appears in the Eclipse settings. I have worked with other boards that use it (e.g. STMicro, Maxim) and have never had to install any J-Link debugger software separately, so that was an aggravating side jaunt. Development for those boards also relies on the (byzantine) Eclipse framework, and examples work 'out-of-the-box' without needing to separately install SEGGER.
My questions:
1 Any suggestions on resolving the build issue? Why does the first build succeed but the following build (ostensibly the same) fail?
2 Is it necessary to insert jumpers on one or both of J1 and J7? If so, which? This was also not addressed in the video – which by its name I expected to cover all details of getting the development environment set up.
Thanks,
Jack Copper