cancel
Showing results for 
Search instead for 
Did you mean: 

Yocto Kirkstone SDK Build Issue - nativesdk-cmsis-svd error

MToum.1
Associate II

Hello,

I am building the SDK toolchain out of the ST Yocto Layer so I can use in on a local machine. I am having the following issue:

WARNING: nativesdk-cmsis-svd-0.4+gitAUTOINC+f487b5ca7c-r0 do_fetch: Failed to fetch URL git://github.com/posborne/cmsis-svd.git;protocol=https;branch=master, attempting MIRRORS if available
ERROR: nativesdk-cmsis-svd-0.4+gitAUTOINC+f487b5ca7c-r0 do_fetch: Fetcher failure: Unable to find revision f487b5ca7c132b8f09d11514c509372f83a6cb75 in branch master even from upstream
ERROR: nativesdk-cmsis-svd-0.4+gitAUTOINC+f487b5ca7c-r0 do_fetch: Bitbake Fetcher Error: FetchError('Unable to fetch URL from any source.', 'git://github.com/posborne/cmsis-svd.git;protocol=https;branch=master')
ERROR: Logfile of failure stored in: /home/xxxx/dev/xxx-os/build-xxxx-yyyy/tmp-glibc/work/x86_64-nativesdk-ostl_sdk-linux/nativesdk-cmsis-svd/0.4+gitAUTOINC+f487b5ca7c-r0/temp/log.do_fetch.1538562
ERROR: Task (virtual:nativesdk:/home/xxxx/dev/xxx-os/layers/meta-st/meta-st-stm32mp/recipes-devtools/cmsis-svd/cmsis-svd_git.bb:do_fetch) failed with exit code '1'
NOTE: Tasks Summary: Attempted 3412 tasks of which 3353 didn't need to be rerun and 1 failed.
NOTE: Writing buildhistory
NOTE: Writing buildhistory took: 2 seconds

I have tried to manually clone the repository: cmsis-svd with the commit number and it worked.

Any clue on what could go wrong?

 

 

6 REPLIES 6
MToum.1
Associate II

Looking at the recipe under: /layers/meta-st/meta-st-stm32mp/recipes-devtools/cmsis-svd/cmsis-svd_git.bb, the SRC_URI with branch "master" is not available. I changed it for "main" to reflect the github repository and the fetch command started to work:

 

SRC_URI = "git://github.com/posborne/cmsis-svd.git;protocol=https;branch=main"
SRCREV = "f487b5ca7c132b8f09d11514c509372f83a6cb75"

 


Please comment!

 

Erwan SZYMANSKI
ST Employee

Hello @MToum.1 ,
Thank your for reporting this, our internal integration team observed this issue too and is working on it to solve.

Kind regards,
Erwan.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

Dear @Erwan SZYMANSKI thank you for confirmation. How is this issue happening? It would be good to know the root cause of it. 

Hello @MToum.1 ,
As you saw, the "master" branch of the repo we target here has been changed to "main" branch. We did not detect it earlier and we apologize for this. Your change is the good one, this is a miss from our side.

Kind regards,
Erwan.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.
Erwan SZYMANSKI
ST Employee

Hello @MToum.1 ,
As information, the correction has been released in OSTL 5.0.2 : https://wiki.st.com/stm32mpu/wiki/STM32_MPU_OpenSTLinux_release_note_-_v5.0.0#Minor_release_updates

 

Kind regards,
Erwan.

In order to give better visibility on the answered topics, please click on 'Accept as Solution' on the reply which solved your issue or answered your question.

I just had the same issue. Thanks a lot! That save me a lot of trouble shooting.
Hope ST will release it in an official release soon.