hecatae
September 18, 2024, 3:06pm
1
So with this commit , support for the following devices may now be possible:
GL-iNet SFT1200 128NAND/128DDR3
GL-iNet SF1200 16NOR/128DDR3
BPI-WiFi5 16NOR/64DDR2
HLK-RM50 16NOR/256DDR3
HSGQ-R1200 16NOR/128DDR3
CPE-RG200U 16NOR/128DDR3
Of course, the commit is for the Siflower Evaluation Board, and is reference only, so you will not find any downloads available or an imagebuilder.
Just getting my head around adding the SFT1200 as a new device.
7 Likes
hecatae
September 19, 2024, 10:13am
2
Ok, I've got GL-iNet's attention, so I'm going to sit on my hands regarding the SFT1200, as they are going to see if they can get this working with their proprietary overlay stuff.
1 Like
Amadeus
September 20, 2024, 2:00pm
3
It seems that the switch driver is missing (for GL-iNet's devices).
1 Like
hecatae
September 20, 2024, 2:21pm
4
Which is weird as GL-iNet are the biggest vendor using this chipset, and have been asking for this commit for years.
1 Like
hecatae
October 11, 2024, 11:33am
5
GL are awaiting for SiFlower to submit the relevant WiFi driver patches to Openwrt.
3 Likes
Fyi: I've put a few sft1200s aside in storage pending future testing possibilities.
2 Likes
BPI-WiFi5 is now available around $16 from AliExpress.
Ordered the BPI, one of these devices should be able to build with the chipset now being in mainline Openwrt.
2 Likes
64MB RAM isn't great though, considering the 8/64 warning.
1 Like
Be fine as an access point though
1 Like
bluewavenet:
sft1200s
@hecatae @frollic @Amadeus
I still have access to a bunch of second hand gl-sft1200 devices. (128/128)....
hecatae
December 3, 2024, 10:36am
11
GL's cofounder have advised they are working hard on the new kernel stuff from Siflower, I'm happy to wait for them to release an op24 version of their stock firmware for the sft1200.
3 Likes
hecatae
December 10, 2024, 4:04pm
12
BPI-WiFi5 arrived, just hunting down a suitable power supply as it came with US.
2 Likes
hecatae
January 23, 2025, 3:50pm
13
SINOVOIP have released sources:
Contribute to BPI-SINOVOIP/BPI-WiFi5-Siflower development by creating an account on GitHub.
Apparently you need Ubuntu 18.04 to build, anyone got a VM to see if it builds?
uboot builds fine on Debian 11, just trying the SDK
4 Likes
h1771t
January 29, 2025, 1:01pm
14
I can attempt a build if needed? The github link you pasted shows their build is for openwrt 18.06, this is ancient and deprecated right? Are you investigating if the build can be done against the latest stable openwrt?
I bought a cheap bpi-wifi5 for access point use, but would like stable openwrt on it. I'm interested in openwrt having official support for bpi-wifi5.
Any way I can assist? I see your first post here says the chipset should be supported already?
Thanks.
hecatae
January 29, 2025, 1:40pm
15
Anyone got a GL SF1200 to hand, apparently the EVB board that the Openwrt commit references was used in SF1200.
h1771t
January 29, 2025, 2:50pm
16
I installed ubuntu 18.04.6 server and ran the instructions at:
Contribute to BPI-SINOVOIP/BPI-WiFi5-Siflower development by creating an account on GitHub.
Both uboot and openwrt-18.06 build successfully. They produce files:
uboot_main_sfa28_ac28_fullmask__3cc0edbe4.bin 232KB
openwrt1806_main_a28_bpi_sf19a28_fullmask_rel_v1.0.0.bin 6.3MB
hecatae
January 29, 2025, 3:00pm
17
What about
a28_bpi_luci2 and a28_bpi_luci2_neutral ?
a month ago, the source was released, and the latest images are bpi_luci2 and bpi_luci2_neutral so you build those with ./make.sh bpi_luci2 etc.
reason being if you look at Sinovoip's wiki, the images are openwrt1806_main_a28_bpi_luci2 and 6,913kb in size.
Bottom of this page:
h1771t
January 29, 2025, 4:15pm
18
a28_bpi_luci2 fails to build:
collect2: error: ld returned 1 exit status
/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0/gcc/c/Make-lang.in:85: recipe for target 'cc1' failed
make[5]: *** [cc1] Error 1
make[5]: *** Waiting for unfinished jobs....
collect2: error: ld returned 1 exit status
/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0/gcc/lto/Make-lang.in:81: recipe for target 'lto1' failed
make[5]: *** [lto1] Error 1
make[5]: Leaving directory '/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0-initial/gcc'
Makefile:4210: recipe for target 'all-gcc' failed
make[4]: *** [all-gcc] Error 2
make[4]: Leaving directory '/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0-initial'
Makefile:36: recipe for target '/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0-initial/.built' failed
make[3]: *** [/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0-initial/.built] Error 2
make[3]: Leaving directory '/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/toolchain/gcc/initial'
a28_bpi_luci2_neutral also fails to build:
collect2: error: ld returned 1 exit status
/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0/gcc/c/Make-lang.in:85: recipe for target 'cc1' failed
make[5]: *** [cc1] Error 1
make[5]: *** Waiting for unfinished jobs....
collect2: error: ld returned 1 exit status
/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0/gcc/lto/Make-lang.in:81: recipe for target 'lto1' failed
make[5]: *** [lto1] Error 1
make[5]: Leaving directory '/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0-initial/gcc'
Makefile:4210: recipe for target 'all-gcc' failed
make[4]: *** [all-gcc] Error 2
make[4]: Leaving directory '/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0-initial'
Makefile:36: recipe for target '/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0-initial/.built' failed
make[3]: *** [/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/build_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/gcc-7.4.0-initial/.built] Error 2
make[3]: Leaving directory '/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/toolchain/gcc/initial'
time: toolchain/gcc/initial/compile#2.52#0.48#1.83
toolchain/Makefile:104: recipe for target 'toolchain/gcc/initial/compile' failed
make[2]: *** [toolchain/gcc/initial/compile] Error 2
make[2]: Leaving directory '/home/user1/BPI-WiFi5-Siflower/openwrt-18.06'
toolchain/Makefile:102: recipe for target '/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/staging_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/stamp/.toolchain_compile' failed
make[1]: *** [/home/user1/BPI-WiFi5-Siflower/openwrt-18.06/staging_dir/toolchain-mipsel_mips-interAptiv_gcc-7.4.0_musl/stamp/.toolchain_compile] Error 2
make[1]: Leaving directory '/home/user1/BPI-WiFi5-Siflower/openwrt-18.06'
Trying to see if I can figure out why.
Hostle
January 29, 2025, 5:40pm
19
maybe try with just a single core so you can get a better idea of whats happening.
you can see in the error what is failing ..
Makefile:4210: recipe for target 'all-gcc' failed
maybe try again with the good old fashion
make V=s
this may produce a more useful error log
2 Likes
h1771t
January 29, 2025, 5:53pm
20
I tried again after editing make.sh to run make -j1 at the end.
I can't see anything yet, but will keep digging.
Here is the full output at the moment: