Repository navigation
(Developers Only) Base Images
Pre-release
Pre-release
Some vendors remove previously uploaded images for their boards. To ensure that these scripts continue to be usable and produce consistent ArPiRobot images, base images for these vendors boards have been uploaded here.
End users should NOT use these images. They do not contain any ArPiRobot modifications. These simply exist so that I don't have to dig up OS images for some boards up from the depths of the internet.
Notes on these images:
-
Orange Pi Zero 2W
- Images with both Linux 5.4 and 6.1 kernel are provided for this board. Using 6.1 kernel images
- Linux 6.1 images used to have three variants: 1GB/2GB, 1.5GB, and 4GB board variants (however, looking at the orange pi build scripts, 4GB should be the same as 1GB/2GB). 1.5GB seems to be different because dram controller is undocumented for SOC (something about not being able to tell the difference between 1.5GB and 2GB ram).
- As of 1.0.2 (at least - unsure if 1.0.1 images ever existed) there are no longer three variants. From looking at build scripts, it seems this will work on all variants including 1.5GB variant)
Orangepizero2w_1.0.0_debian_bookworm_server_linux6.1.31.7z: This is image for 1GB/2GB boards (also should work on 4GB - see above)Orangepizero2w_1.0.2_debian_bookworm_server_linux6.1.31.7z: Should work on all board variants
-
Orange Pi 3B
- There are several revisions of this board. Two we care about are v1.1.1 and v2.1. I think these both use same pinout, but I only have v1.1.1. hardware to test on. I think v1.0 (and maybe v1.1 if ever sold) used an older pinout and images may not be compatible.
- v2.1 seems to have changed Ethernet voltage, so old images may brick v2.1 boards.
Orangepi3b_1.0.4_debian_bookworm_server_linux5.10.160.7zwas downloaded when v1.1.1 of the board was sold. DO NOT USE see comments in 1.0.6 image below.Orangepi3b_1.0.6_debian_bookworm_server_linux5.10.160.7zwas uploaded later with support for v2.1. The changelog also indicates that a u-boot power domain issue causing network port damage was fixed. All old images were also removed at this time. It is unknown if this power domain issue impacted v2.1 only or also v1.1.1 boards. It may have only applied to a 1.0.5 image. But there's really no way to be sure. As such, assume v1.0.4 image could damage v.1.1.1 hardware (and since it is also incompatible with v2.1 boards, just don't use it).