Quantcast
Viewing all articles
Browse latest Browse all 262198

WL18xx Build Utilities Error

I'm currently trying to build the files for the WL18xx and SDK 2.00.00.00 with Linux 4.1.6 using the build utilities as described here:  processors.wiki.ti.com/index.php/WL18xx_System_Build_Scripts for running Arago on a BeagleBone Black

I'm running into an issue when executing ./sudo_build_wl18xx.sh update R8.5

The output from the script ends with this:

Modify Kconfig tree ...
Rewrite Makefiles and Kconfig files ...
Done!
Generating local configuration database from kernel ...Kernel version parse failed!
make: *** [clean] Error 1
Generating local configuration database from kernel ...Kernel version parse failed!
make: *** [defconfig-wl18xx] Error 1
Generating local configuration database from kernel ...Kernel version parse failed!
make[1]: *** [modules] Error 1
make: *** [default] Error 2
****** ERROR 0 *******

Here is my setup-env file:

# if DEFAULT toolchain path is set toolchain will be downloaded to ./toolchain.
export TOOLCHAIN_PATH=DEFAULT

# if DEFAULT path to root filesystem is set ./fs folder will be used.
export ROOTFS=/opt/ti-processor-sdk-linux-am335x-evm-02.00.00.00/targetNFS

#if DEFAULT kernel path is set - kernel will be downloaded (set branch to match kernel version)
export KERNEL_PATH=/opt/ti-processor-sdk-linux-am335x-evm-02.00.00.00/board-support/linux-4.1.6+gitAUTOINC+52c4aa7cdb-g52c4aa7

# if KERNEL_VARIANT below is set the build script will look for kernel specific
# patches under the patches directory:
# - patches under the pathces/driver_patches/$KERNEL_VARIANT directory would be
# applied during "modules" build.
# - patches under the patches/kernel_patches/$/$KERNEL_VARIANT directory would
# be applied to the kernel pointed by KERNEL_PATH in case the "patch_kernel"
# command is used.
# Note: the kernel is not built automatically after the patches are applied
export KERNEL_VARIANT=DEFAULT

export CROSS_COMPILE=arm-linux-gnueabihf-
export ARCH=arm
[ "$TOOLCHAIN_PATH" != "DEFAULT" ] && export PATH=$TOOLCHAIN_PATH:$PATH

I'm not certain, but could the issue be with parsing the Linux version from the kernel path?  The folder names were all automatically generated when I installed SDK 2.00.00.00 off of the TI website.


Viewing all articles
Browse latest Browse all 262198

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>