• State Verified Answer
  • +1 person also asked this people also asked this
  • Replies 20 replies
  • Answers 2 answers
  • Subscribers 7 subscribers
  • Views 1024 views
  • Users 0 members are here
Options
Related

DA16200 SDK 3.2.6 unable to build

Keith_CQ

I've installed the FreeRTOS SDK tool chain package (v1.0) and Eclipse version 2022-12 (4.26.0) on a clean/new Win10 laptop but I'm faced with a build error.:- 

10:59:06 **** Incremental Build of configuration Debug for project da16200 ****
make all
make: unknown option -- no-print-directory
BusyBox v1.36.0.git (2023-01-29 16:36:13 UTC)

Usage: make [--posix] [-C DIR] [-f FILE] [j NUM] [-eiknpqrsSt] [MACRO[::]=VAL]... [TARGET]...

Maintain files based on their dependencies

--posix Enforce POSIX mode
-C DIR Change to DIR
-f FILE Makefile
-j NUM Jobs to run in parallel (not implemented)
-e Environment variables override macros in makefiles
-i Ignore exit status
-k Continue on error
-n Dry run
-p Print macros and targets
-q Query target; exit status 1 if not up to date
-r Don't use built-in rules
-s Make silently
-S Stop on error
-t Touch files instead of making them
make: *** [makefile:121: all] Error 1
"make all" terminated with exit code 2. Build might be incomplete.

10:59:11 Build Failed. 1 errors, 0 warnings. (took 5s.101ms)

I've not found a solution on the web. Can you help?

I notice that during the install the text advised be that the install would require 3GB of HDD space! That's a lot of bloat!

I have another laptop - Win11 with Arm tools already installed but that also fails - in more interesting ways.- builds the DA16200.elf file but then fails with unable to find the file specified. I can grab logs and post here if I'm unable to get this machine building - I'm hoping to be able to find which tool it's looking for from a working buiild.

Thanks.

Keith_CQ.

Parents
  • 0

    Hello! 
    I am facing the exact same issue on a Win 11 machine without tools previously installed. 
    I followed the guide and ended up getting this same error:
    ```

    13:33:12 **** Build of configuration Debug for project da16600 ****
    make all
    make: unknown option -- no-print-directory
    BusyBox v1.36.0.git (2023-01-29 16:36:13 UTC)

    Usage: make [--posix] [-C DIR] [-f FILE] [j NUM] [-eiknpqrsSt] [MACRO[::]=VAL]... [TARGET]...

    Maintain files based on their dependencies

    --posix Enforce POSIX mode
    -C DIR Change to DIR
    -f FILE Makefile
    -j NUM Jobs to run in parallel (not implemented)
    -e Environment variables override macros in makefiles
    -i Ignore exit status
    -k Continue on error
    -n Dry run
    -p Print macros and targets
    -q Query target; exit status 1 if not up to date
    -r Don't use built-in rules
    -s Make silently
    -S Stop on error
    -t Touch files instead of making them
    make: *** [makefile:129: all] Error 1
    "make all" terminated with exit code 2. Build might be incomplete.

    13:33:14 Build Failed. 1 errors, 0 warnings. (took 1s.889ms)
    ```
    I am using this sdk: `DA16200_DA16600_SDK_FreeRTOS_v3.2.6.0`
    I have also extracted to a path with less than 70 chars length. 
    Please let us know for a solution. I am working on this about 2 weeks now.
    Thanks in advance 

  • 0 in reply to Evan

    Hi All,

    Our Team was able to recreate this issue.

    We found a compatibility issue with the compile environment.

    We are working on it to solve the issue.
    I will update you here as soon as I have an update from the Team that the issue is fixed.

    Kind Regards,
    OV_Renesas

  • 0 in reply to OV_Renesas

    I am just getting started with the EVK, and I am experiencing the same build issue. I also look forward to the solution.

  • 0 in reply to Michael

    Update: I found that the SDK builds with Eclipse 2021-03 but breaks with Eclipse 2021-06. So for anyone needing to play with the SDK before the fix is released, try the older version of Eclipse.

Reply Children