Default config target

I’m new to the AI64 and I’m trying to build the default configuration target for the AI64 according to the instructions in the docs. For some reason make cannot find the target specified in the docs, i.e. tisdk_j7-evm_defconfig.

This is the command I’m running and the output:

$ make ARCH=arm64 CROSS_COMPILE=aarch64-none-linux-gnu- tisdk_j7-evm_defconfig
make: *** No rule to make target ‘tisdk_j7-evm_defconfig’. Stop.

I’m using the default Makefile, Rules.make etc without any modifications. I’ve looked all over the forum for a solution. What am I missing?

At this point, it is hard to guess. Please post a link to the sdk you are using.

@foxsquirrel - Thank you for your response. I’m using this SDK:

I only downloaded and accepted the defaults during the installation.

Just checking to make sure we are on the same one:

 Processor SDK Linux for J721e
08_06_01 

That uses yocto for the SDK generation. I did not see any make file, so is it safe to assume you have already ran yocto and have the sdk.

Other issue is this is for an old version on ubuntu and they mention java. Pretty sure I have gone down this path a couple years back and what happens is it needs an old java 8 version that is no longer supported. This is from memory and might very well be wrong information.

Thanks for being patient with a newbie! I’m really stuck.

I’m using “latest” which apparently is 09_02_00. I’m on Ubuntu 22.04. I --think-- I have all the prerequisites installed. In my ${SDK_INSTALL_DIR} directory I see the following:

bin board-support example-applications filesystem k3r5-devkit licenses linux-devkit Makefile makerules manifest Rules.make setup.sh targetNFS yocto-build

Not sure what to do next…

I will look at that version tomorrow. Did the yocto build finish without any errors?

Yes, as far as I can tell. Thanks in advance for any suggestions!

You must run the installer script that yocto generated before building with it, its been a while with Ti but it seems like it has a long name ending with .sh. Might look for that, at the top of the tree $find -name *.sh, this is just a quick thought.

No luck as of yet. Maybe something went wrong during installation after all? I’ll try reinstalling the SDK and see if that makes a difference.