Forums - Snapdragon Flight Dev. Kit

1 post / 0 new
Snapdragon Flight Dev. Kit
antonl
Join Date: 5 Dec 15
Posts: 42
Posted: Sun, 2015-12-13 13:27

Hello

My questions concern the Qualcomm Flight Controller Board, Eagle. In the flight-controller-hexagon-sdk-add-on (delivered by intrinsyc) is the dspal tester example which one should be able to build and run with the Hexagon SDK 2.0 (delivered by Qualcomm). However, I get the following error when I execute
"C:\Qualcomm\Hexagon_SDK\2.0\flight_controller\examples\dspal_tester>build Debug|Release"


without debugging output:

C:\Qualcomm\Hexagon_SDK\2.0\flight_controller\examples\dspal_tester>build Debug
make  V=hexagon_Debug_dynamic clean
(if exist hexagon_Debug_dynamic rmdir/s/q hexagon_Debug_dynamic) &&  cmd /c exit 0
make tree  V=hexagon_Debug_dynamic
making C:\Qualcomm\Hexagon_SDK\2.0/lib/common/atomic
making C:\Qualcomm\Hexagon_SDK\2.0/lib/common/rpcmem
making C:\Qualcomm\Hexagon_SDK\2.0/test/common/test_util
making C:\Qualcomm\Hexagon_SDK\2.0/test/common/test_main
making .
c:/qualcomm/hexagon_tools/6.4.03/gnu/bin/../lib/gcc/hexagon/4.6.1/../../../../hexagon/bin/ld.exe: warning: -z text ignor
ed.
make V=UbuntuARM_Debug clean
(if exist UbuntuARM_Debug rmdir/s/q UbuntuARM_Debug) &&  cmd /c exit 0
make tree  V=UbuntuARM_Debug
making C:\Qualcomm\Hexagon_SDK\2.0/lib/common/atomic
The system cannot find the path specified.
make[1]: *** [UbuntuARM_Debug/atomic.o] Error 1
ERROR making C:\Qualcomm\Hexagon_SDK\2.0/lib/common/atomic
make[1]: Entering directory `C:/Qualcomm/Hexagon_SDK/2.0/lib/common/atomic'
"../../../tools/make.d.ext/UbuntuARM/../../Linaro/gcc-linaro-arm-linux-gnueabihf-4.8-2013.08_win32/bin/arm-linux-gnueabi
hf-gcc"  -c -fPIC -Wall -Wno-missing-braces -mword-relocations -mthumb-interwork -mfloat-abi=hard -mfpu=neon -mtune=cort
ex-a8 -march=armv7-a -Werror -g -isystem ../../../tools/make.d.ext/UbuntuARM/../../Linaro/gcc-linaro-arm-linux-gnueabihf
-4.8-2013.08_win32/arm-linux-gnueabihf/libc/usr/include -DARM_ARCH_7A -DUSE_SYSLOG -std=gnu99      -D__FILENAME__=\"atom
ic.c\" -D_DEBUG  -I../../../inc/stddef -IUbuntuARM_Debug  -oUbuntuARM_Debug/atomic.o atomic.c
make[1]: Leaving directory `C:/Qualcomm/Hexagon_SDK/2.0/lib/common/atomic'
make: *** [MAKE_D_3_LIBDIR] Error 1
Done


with debugging output:
...
Updating goal targets....
Considering target file `tree'.
 File `tree' does not exist.
  Considering target file `MAKE_D_3_LIBDIR'.
   File `MAKE_D_3_LIBDIR' does not exist.
   Finished prerequisites of target file `MAKE_D_3_LIBDIR'.
  Must remake target `MAKE_D_3_LIBDIR'.
Creating temporary batch file C:\Users\ANTONJ~1\AppData\Local\Temp\make7692-1.bat
CreateProcess(C:\Users\ANTONJ~1\AppData\Local\Temp\make7692-1.bat,C:\Users\ANTONJ~1\AppData\Local\Temp\make7692-1.bat,...)
Putting child 0x01db54e0 (MAKE_D_3_LIBDIR) PID 31094576 on the chain.
Live child 0x01db54e0 (MAKE_D_3_LIBDIR) PID 31094576
making C:\Qualcomm\Hexagon_SDK\2.0/lib/common/atomic
The system cannot find the path specified.
make[1]: *** [UbuntuARM_Release/atomic.o] Error 1
ERROR making C:\Qualcomm\Hexagon_SDK\2.0/lib/common/atomic
GNU Make 3.81
Copyright (C) 2006  Free Software Foundation, Inc.
This is free software; see the source for copying conditions.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
...


Additionallly, also the android calculator example fails to run on the board, even though it compiles. Probably because there is not a common android os installed on the snapdragon flight board (e.g. no \system folder etc.)

Do you have any idea of how to approach these issues? Any kind of help is very welcome!

 

Tony

  • Up0
  • Down0

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.