building the sdk fails at cloning arago-project repository

Maxime Guillemette

Hi,

I'm following along this video: https://www.ti.com/video/5768885091001 on building the SDK for my k2g-evm.

When running the following command:

./oe-layertool-setup.sh -f configs/processor-sdk/processor-sdk-06.03.00.106-config.txt

The part when it needs to clone meta-processor-sdk from arago-project.org hangs forever, since the domain was switched to some other place:

cloning repo meta-processor-sdk

Cloning into '/home/mgui/yocto/tisdk/sources/meta-processor-sdk'...
fatal: unable to access 'http://arago-project.org/git/projects/meta-processor-sdk.git/': Failed to connect to arago-project.org port 80: Connection refused
git failed... remaining attempts: 4    sleeping 15 seconds

The problem is that from https://www.ti.com/tool/download/PROCESSOR-SDK-LINUX-K2G 06.03.00.106 is the latest version for my evm.

I tried using a more recent configuration file, but then no recipes are provided for k2g-evm.

I'm using an ubuntu 18.04 host machine.

Is the k2g-evm still actively supported for building the SDK? I tried the demo SDK but for our needs we would need something closer to the yocto framework.

What is the most up-to-date way to build a linux image for this board?

Thanks

over 2 years ago

0 Andreas Dannenberg over 2 years ago

TI__Guru 69847 points

Hi Maxime,

the arago-project.org server has been decommissioned a while ago so you need to replace/update related URLs accordingly. There's a few posts here on the E2E regarding this. For example see this post here for more info and how to get going: https://e2e.ti.com/support/processors-group/processors/f/processors-forum/1125319/processor-sdk-am437x-am437x-hs-tisdk-rootfs-image-target-build-issue/4185134#4185134

Regards, Andreas

0 Maxime Guillemette over 2 years ago in reply to Andreas Dannenberg

Prodigy 10 points

As I mentioned, when using a more recent configuration file (e.g. SDK version > 08.0), the repo url changes to a valid one and "fixes" the problem, but then the MACHINE=k2g-evm is not valid for new SDK versions.

Does this mean the k2g-evm is not supported in more recent SDK versions?

If so, what is the recommended software stack for new designs using the chip.

0 Andreas Dannenberg over 2 years ago in reply to Maxime Guillemette

TI__Guru 69847 points

Maxime Guillemette said:
Does this mean the k2g-evm is not supported in more recent SDK versions?

Support for those devices has been dropped from newer SDKs.

Maxime Guillemette said:
If so, what is the recommended software stack for new designs using the chip.

You should be using the latest official SDK released for those devices, which is SDK v6.3 as per https://www.ti.com/tool/PROCESSOR-SDK-K2G In order to get it to Yocto-build you'll need to update various upstream URLs to accommodate any upstream changes that happened over time to server locations and also branch names ('master' -> 'main' !!!), so this will take a bit of effort to sort but it's not too difficult to do. Once you have that up and running you can then always upgrade individual SW components to newer versions as needed on your own. But I think it is important to have a working known-good baseline first.

Regards, Andreas

0 Maxime Guillemette over 2 years ago in reply to Andreas Dannenberg

Prodigy 10 points

Ok we'll use the 6.3 version and modify the scripts to evaluate the module.

Regarding the SDK, can you confirm if the k2g-evm support is permanently dropped and will not be supported in future releases? And if so, is there a particular reason?

Regards,

+1 Andreas Dannenberg over 2 years ago in reply to Maxime Guillemette

TI__Guru 69847 points

Maxime Guillemette said:
Regarding the SDK, can you confirm if the k2g-evm support is permanently dropped and will not be supported in future releases?

That is correct from a TI SDK POV. However I just checked there is support for those platform in upstream U-Boot as well as Kernel maintained by the community. I'm not sure how complete the support is but it may well be possible to migrate/use those trees. Should additional features/fixes be needed they could also be contributed back directly to those projects.

Maxime Guillemette said:
And if so, is there a particular reason?

I think those are considered "legacy platforms'; most customers/business is on the newer 64-bit ARM platforms such as AM6x which is where most our investment goes. Generally speaking from a TI POV we'll keep making any device as long as somebody is buying those however for software updates/investments those are are done in a more targeted fashion and not always for all platforms we ever made.

Regards, Andreas

Processors

Processors forum

building the sdk fails at cloning arago-project repository