make in boot folder fails with error#8

[SteveSpencer]

I have just cloned master (49th step) into a new folder. Did the usual configuration, and ran ./makeall, and all is well.
This is on a pi64 running aarch64 Debian bookworm, kernel 6.12.
Went into the boot folder and tried make, but got an error 8 from make. I noticed that many of the files were zero length (which isn't right). So I removed the -q from the wget command lines, and I now see that many of the wget commands are getting "429 Too Many Requests" responses.
This didn't used to happen, so I suspect a change in rate limiting or similar on github.
Two questions, then. 1. Is there a way to fix it and 2. When did it change (although that's not strictly a circle issue...)
As a workaround, I can generate the command lines and execute them interspersed with calls to sleep, which is clunky but seems to work.

[rsta2]

Oops, this is a new problem. I can confirm it on my normal Linux development host. I think it still worked about one week ago. Perhaps it's temporary? Please send a PR, if you have a solution. Thanks.

[rsta2]

With this small patch, it should work:

diff --git a/boot/Makefile b/boot/Makefile
index 236f32e1..3a21bac9 100644
--- a/boot/Makefile
+++ b/boot/Makefile
@@ -14,7 +14,7 @@
 # Use firmware revision built/committed on: Nov 26 2024
 FIRMWARE ?= 4bb9d889a9d48c7335ebe53c0b8be83285ea54b1
 
-BASEURL = https://github.com/raspberrypi/firmware/blob/$(FIRMWARE)/boot
+BASEURL = https://github.com/raspberrypi/firmware/raw/$(FIRMWARE)/boot
 
 FILES = LICENCE.broadcom COPYING.linux \
        bootcode.bin start.elf fixup.dat start4.elf fixup4.dat \
@@ -32,12 +32,12 @@ firmware: clean
        @for file in $(FILES) ; \
        do \
                echo Downloading $$file ... ; \
-               wget -q -O $$file $(BASEURL)/$$file?raw=true ; \
+               wget -q -O $$file $(BASEURL)/$$file ; \
        done
        @for file in $(OVERLAYS) ; \
        do \
                echo Downloading $$file ... ; \
-               wget -q -O $$file $(BASEURL)/overlays/$$file?raw=true ; \
+               wget -q -O $$file $(BASEURL)/overlays/$$file ; \
        done
 
 all: firmware armstub bootloader

[rsta2]

The given patch is on the develop branch now. So to download the firmware files one should checkout develop now and proceed in boot/ as known.

[Andy2No]

What exactly should I be doing to checkout develop? I'm not all that familiar with git bash. I tried:

git checkout develop
git fetch --all
cd ~/Documents/circle/boot
make all

but got the same error and set of empty downloads, ending with:

Downloading bcm2712-rpi-cm5-cm5io.dtb ...
Downloading bcm2712-rpi-cm5l-cm5io.dtb ...
make: *** [makefile:32: firmware] Error 1

Edit: I then tried downloading the new makefile, from develop, overwriting the one I had, i.e. I downloaded

https://github.com/rsta2/circle/blob/develop/boot/Makefile

to

C:\Users\andy\Documents\circle\boot

make all failed again, with the same error.

From following the https://github.com/rsta2/circle/blob/master/doc/windows-build.txt, I have GNU Make 4.2 (checked with $ make --version). Is that the version I'm meant to have?

Edit2: I then tried:

"go to the build root of Circle and do:"

./makeall clean
./makeall

but got the same results when I tried again.

[rsta2]

After "git checkout develop" you should give the following command to get the latest version of the develop branch: git pull

[Andy2No]

Thanks, but when I try that it just says "Already up to date.". I then get the same problem when I try make all again, in boot.

[hpingel]

Do you use the environment variable FIRMWARE on your system with a value that then overrides the default value of FIRMWARE within the make file? Remove -q from wget in the makefile to get more insight in what happens and which exact error message comes up.

[Andy2No]

Do you use the environment variable FIRMWARE on your system with a value that then overrides the default value of FIRMWARE within the make file?

Apparently not, no.

Remove -q from wget in the makefile to get more insight in what happens and which exact error message comes up.

Yes, I tried:

$ wget -O bcm2712-rpi-cm5l-cm5io.dtb https://github.com/raspberrypi/firmware/blob/4bb9d889a9d48c7335ebe53c0b8be83285ea54b1/boot/bcm2712-rpi-cm5l-cm5io.dtb
https://github.com/raspberrypi/firmware/blob/4bb9d889a9d48c7335ebe53c0b8be83285ea54b1/boot/bcm2712-rpi-cm5l-cm5io.dtb: Unknown/unsupported protocol.

The last part is the error message - it got tacked onto what I typed, instead of being put on a new line: "Unknown/unsupported protocol.".

It seems this is to do with wget in git not supporting https, until recently. For comfort and sanity reasons, I've been trying to do this on my PC with Windows 7, which all seemed to be going well - makeall of the circle project itself works, for example, but it seems this won't, and I already have the last version of git for Windows 7, AFAIK :

$ git --version
git version 2.46.0.rc2.windows.1

So, my problem seems to be only partly related to this issue after all. I've come up with a workaround which allows me to do make all successfully in boot - I downloaded the files from https://github.com/raspberrypi/firmware/tree/4bb9d889a9d48c7335ebe53c0b8be83285ea54b1 then commented out the part of the makefile that tries to download them, then ran make all.

[hpingel]

You seem to have chosen an unsupported build environment that makes your life very hard. Who knows which version of wget you have on Win7. If you solve this issue you will run into the next. Please read the instructions on a proper build environment in the Circle Readme.

You are IMHO wasting your time and the time of helpers without using WSL on Windows.

[hpingel]

Gnu Make for Windows seems to have a really old wget version? I don't remember if git for Windows ships with wget as well.

https://gnuwin32.sourceforge.net/packages/wget.htm

Bottom line is: If your circle project compiles fine and you want to stick to your outdated Win7 environment, replace wget with something newer. Or download the firmware manually as you already did. You don't need to get the firmware files again once you have them.

I am biased as I use Linux or WSL2.

[Andy2No]

I'm not against using Linux to do it, and may switch to that, but I was following the startup guide for Windows that I linked to above, and hoping that applied to Windows 7, since it's what I'm most comfortable using and have in front of me.

FWIW, it seems I had that version of wget installed but not on the path, so wget v1.7 was being picked up from WINAVR (C:\WinAVR-20100110\bin). Sadly, both versions cause similar behaviour and my single file test now shows:

$ wget -O bcm2712-rpi-cm5l-cm5io.dtb https://github.com/raspberrypi/firmware/blob/4bb9d889a9d48c7335ebe53c0b8be83285ea54b1/boot/bcm2712-rpi-cm5l-cm5io.dtb
SYSTEM_WGETRC = c:/progra~1/wget/etc/wgetrc
syswgetrc = C:\Program Files (x86)\GnuWin32/etc/wgetrc
--2025-06-15 16:03:50--  https://github.com/raspberrypi/firmware/blob/4bb9d889a9d48c7335ebe53c0b8be83285ea54b1/boot/bcm2712-rpi-cm5l-cm5io.dtb
Resolving github.com... 20.26.156.215
Connecting to github.com|20.26.156.215|:443... connected.
OpenSSL: error:1407742E:SSL routines:SSL23_GET_SERVER_HELLO:tlsv1 alert protocol version
Unable to establish SSL connection.

Never mind. I'll come back to it when I'm less tired.

[rsta2]

I think the problem is, that you are using a very old OS. wget is using an old out-dated SSL/TLS protocol version on this system, which is not supported by GitHub any more. I think the only possible solution is to update your OS. This problem is different from that, which has been answered above in this topic, and Circle is not responsible for this.

[bcox-sdm]

I am having the same issue, but with Windows 11.

I would really appreciate any help here; I am stuck. I have tried both the Master and Develop branches and get the same result.

[rsta2]

Not sure, but I guess this is caused by an old wget version. Can you install and try a recent version?

[bcox-sdm]

Thank you for responding. I downloaded wget from the link provided by hpingel above. It did appear old (2008), but the gnu.org and SourceForge sites still reference the same page. I downloaded the windows .exe since I am developing on Windows 11. Is there a better source?

[rsta2]

This is definitely an old version. I have 1.25.0 on Linux here. I could also only use a search engine on the Internet for found a newer version for Windows.