OpenWRT Package Updates

BotBlox Software
1

I purchased a rugged-som board preloaded with OpenWRT and am having issues downloading/updating packages. I also cannot upgrade the firmware using built-in sysupgrade tools. I suspect this is because the firmware version that is loaded on the board is no longer supported.

Are there plans to update the github release to a newer version? Release v24.10.0-botblox_v1.0.0 · botblox/openwrt · GitHub

Steps to reproduce:

From CLI

opkg update

Downloading https://downloads.openwrt.org/snapshots/targets/imx/imx6ull/packages/Packages.gz
*** Failed to download the package list from

Collected errors:

  • opkg_download: Failed to download, wget returned 8.

Sysupgrade failure

image
image1949×247 28.6 KB

System Information

Hostname OpenWrt
Model Freescale i.MX6 ULL BotBlox SwitchBlox Rugged Board
Architecture ARMv7 Processor rev 5 (v7l)
Target Platform imx/imx6ull
Firmware Version OpenWrt 24.10-SNAPSHOT r28578-fc1d7db6d61 / LuCI Master 25.070.50769~dea8d79
Kernel Version 6.6.83
2

Sysupgrade updates, either through the GUI or CLI, will not work. Part of the next update is to fix this.

Regarding opkg update failing: you can try using the packages created for the imx/cortexa7 target instead.

cp /etc/opkg/distfeeds.conf /etc/opkg/distfeeds.conf.backup # optional
vi /etc/opkg/distfeeds.conf

Edit /etc/opkg/distfeeds.conf

- src/gz openwrt_core https://downloads.openwrt.org/snapshots/targets/imx/imx6ull/packages
+ src/gz openwrt_core https://..archive.openwrt.org/releases/24.10.0/targets/imx/cortexa7/packages
+ src/gz openwrt_base      https://..archive.openwrt.org/releases/24.10.0/packages/arm_cortex-a7_neon-vfpv4/base
+ src/gz openwrt_luci      https://..archive.openwrt.org/releases/24.10.0/packages/arm_cortex-a7_neon-vfpv4/luci
+ src/gz openwrt_packages  https://..archive.openwrt.org/releases/24.10.0/packages/arm_cortex-a7_neon-vfpv4/packages
+ src/gz openwrt_routing   https://..archive.openwrt.org/releases/24.10.0/packages/arm_cortex-a7_neon-vfpv4/routing
+ src/gz openwrt_telephony https://..archive.openwrt.org/releases/24.10.0/packages/arm_cortex-a7_neon-vfpv4/telephony

>Run opkg update again

>You may need to comment out the core package feed if you get errors

- src/gz openwrt_core https://downloads.openwrt.org/snapshots/targets/imx/cortexa7/packages
+ # src/gz openwrt_core https://..archive.openwrt.org/releases/24.10.0/targets/imx/cortexa7/packages

Let me know how you get on.

The long-term solution is either to publish our own package feed for the imx/imx6ull target or to fix the package feeds used by opkg in build time rather than implement this fix. I will add this to the next release.

3

Thanks for your quick response! The package sources you listed did not work as they rely on the apk package manager. The version I am on only supports opkg. I was able to get what I needed by changing my sources to an archived source. I only needed to install one package and that worked for me, I will refrain from updating any packages as I am not sure about dependencies etc. I will keep an eye out for your next firmware release!

/etc/opkg/distfeeds.conf (remove the “..” at the beginning of the link)

src/gz openwrt_core https://..archive.openwrt.org/releases/24.10.0/targets/imx/cortexa7/packages
src/gz openwrt_base https://..archive.openwrt.org/releases/24.10.0/packages/arm_cortex-a7_neon-vfpv4/base
src/gz openwrt_luci https://..archive.openwrt.org/releases/24.10.0/packages/arm_cortex-a7_neon-vfpv4/luci
src/gz openwrt_packages https://..archive.openwrt.org/releases/24.10.0/packages/arm_cortex-a7_neon-vfpv4/packages
src/gz openwrt_routing https://..archive.openwrt.org/releases/24.10.0/packages/arm_cortex-a7_neon-vfpv4/routing
src/gz openwrt_telephony https://..archive.openwrt.org/releases/24.10.0/packages/arm_cortex-a7_neon-vfpv4/telephony

1 Like
4

Thanks for pointing that out @nbrown .

Yes, my apologies I missed that. In which case, you can try the archive packages sources or use https://downloads.openwrt.org/releases/24.10.3/packages/arm_cortex-a7/{subdirectory}
(Changing subdirectory for the specific package feeds you want)

Yes, I will be pushing this as part of the next Rugged SOM software update.