Checksum for file could not be found (scarthgap)

33 views
Skip to first unread message

Moritz Krautwald

unread,
Jul 24, 2025, 6:52:29 AM7/24/25
to swup...@googlegroups.com
Hello,

I was following the tutorial [1] which basically resembles the raspberry
pi setup in meta-swupdate-boards.
Building results in this error:

ERROR:
/home/mo/projects/daccu-coprocessor/meta-daccu-coprocessor/build/../meta-swupdate/recipes-support/swupdate/swupdate_20
23.12.1.bb: Unable to get checksum for swupdate SRC_URI entry
0001-BUG-regression-checking-IVT.patchfile: file could not be found

Then it lists all paths, also the one containing the patch. The weird
thing is, that swupdate_2023.12.1.bb contains:

> require swupdate.inc
>
> SRC_URI += "file://0001-BUG-regression-checking-IVT.patch"
>
> SRCREV = "66952eff1a30701686723ff2fab0576b389620db"

So openembedded appends file resulting in the .patchfile suffix, which
does not exist on the filesystem. I am unable to explain this and could
not find any hints online. Does someone has any idea what might be
causing this?

Best regards
Moritz Krautwald

[1] https://www.winterstein.biz/blog/yocto-swupdate-local/

--
https://www.aicorn.de

Östliche Rheinbrückenstr. 50 | BK 148, 76187 Karlsruhe (Postanschrift)

aicorn GmbH: Geschäftsführer: Dr.-Ing. Thilo Oliver Richter, Samuel
Wenz, Christian Grund; Sitz der Gesellschaft: Siemensallee 75, 76187
Karlsruhe, Deutschland; Registergericht: Mannheim, HRB 74312

Stefano Babic

unread,
Jul 24, 2025, 7:01:38 AM7/24/25
to Moritz Krautwald, swup...@googlegroups.com
Hallo Moritz,

On 7/24/25 12:44, Moritz Krautwald wrote:
> Hello,
>
> I was following the tutorial [1] which basically resembles the raspberry
> pi setup in meta-swupdate-boards.
> Building results in this error:
>
> ERROR:
> /home/mo/projects/daccu-coprocessor/meta-daccu-coprocessor/build/../meta-swupdate/recipes-support/swupdate/swupdate_20
> 23.12.1.bb: Unable to get checksum for swupdate SRC_URI entry
> 0001-BUG-regression-checking-IVT.patchfile: file could not be found
>
> Then it lists all paths, also the one containing the patch. The weird
> thing is, that swupdate_2023.12.1.bb contains:
>
>> require swupdate.inc
>>
>> SRC_URI += "file://0001-BUG-regression-checking-IVT.patch"
>>
>> SRCREV = "66952eff1a30701686723ff2fab0576b389620db"
>
> So openembedded appends file resulting in the .patchfile suffix, which
> does not exist on the filesystem. I am unable to explain this and could
> not find any hints online. Does someone has any idea what might be
> causing this?

Do you have another .bbappend with SRC_URI:append = "file..", that means
without the required space for the append ?

Nevertheless, why are you forcing 2023.12.1 when I released 2025.05 for
scarthgap, too ?

Best regards,
Stefano Babic

Moritz Krautwald

unread,
Jul 25, 2025, 4:43:48 AM7/25/25
to Stefano Babic, swup...@googlegroups.com
Hello Stefano,

thank you for your answer. Indeed I had a SRC_URI:append without the
space. Adding it resolved the issue.

> Nevertheless, why are you forcing 2023.12.1 when I released 2025.05 for scarthgap, too ?

I did not force 2023.12.1. I even tried forcing 2025.05, but even then
the error occured, probably because it already happened while loading
all the metadata.

Best regards
Moritz Krautwald

Moritz Krautwald

unread,
Jul 25, 2025, 8:59:09 AM7/25/25
to Stefano Babic, swup...@googlegroups.com
Hello Stefano,

thank you for your answer. Indeed I had a SRC_URI:append without the
space. Adding it resolved the issue.

> Nevertheless, why are you forcing 2023.12.1 when I released 2025.05 for scarthgap, too ?

I did not force 2023.12.1. I even tried forcing 2025.05, but even then
the error occured, probably because it already happened while loading
all the metadata.

Best regards
Moritz Krautwald

Reply all
Reply to author
Forward
0 new messages