Tool/software:
I am trying to do a yocto build using the 6.03 SDK. I am having trouble with the meta-processor-sdk. The line in the configs file to load the repository is:
meta-processor-sdk,git.ti.com/.../meta-processor-sdk,master,56d9d47f18eeec31a1086ca29e54b5956c46de84,layers=
And this fails to clone the repository. The error messages look something like:
[2025-09-22T13:24:58.210Z] Cloning into '/work/sources/meta-processor-sdk'...
[2025-09-22T13:25:00.105Z] warning: redirecting to https://git.ti.com/cgit/processor-sdk/meta-processor-sdk/
[2025-09-22T13:25:14.961Z] error: HTTP request failed (curl_result = 22, http_code = 503, sha1 = 5ee3f2ba2cc80870afa21f1b0dd68bcc1717bacc)
[2025-09-22T13:25:15.218Z] error: Unable to find 5ee3f2ba2cc80870afa21f1b0dd68bcc1717bacc under https://git.ti.com/cgit/processor-sdk/meta-processor-sdk
[2025-09-22T13:25:15.218Z] Cannot obtain needed tree 5ee3f2ba2cc80870afa21f1b0dd68bcc1717bacc
[2025-09-22T13:25:15.218Z] while processing commit b0a7b924b9b518e5790fd5bb0a668d424be0d378.
[2025-09-22T13:25:15.218Z] error: fetch failed.
A manual clone also fails:
$ git clone https://git.ti.com/processor-sdk/meta-processor-sdk
Cloning into 'meta-processor-sdk'...
warning: redirecting to https://git.ti.com/cgit/processor-sdk/meta-processor-sdk/
error: The requested URL returned error: 503 (curl_result = 22, http_code = 503, sha1 = 05eb0dd4ca59646a403e5e732ca638083b8a49d0)
error: Unable to find d145b971078f683faaa98d592afd80196e81645c under https://git.ti.com/cgit/processor-sdk/meta-processor-sdk
Fetching objects: 52, done.
Cannot obtain needed tree d145b971078f683faaa98d592afd80196e81645c
while processing commit 2005e3725272a477332f5d6f0573c19e97e47268.
error: fetch failed.
The details of the error messages are different but the failure is similar.
Doing a manual clone and specifying the branch seems to work:
git clone --single-branch --branch master https://git.ti.com/processor-sdk/meta-processor-sdk
In short, the repository seems like it might be broken. The manual clone specifying the branch might be a work-around.