Watchdog handover: fd=3
- watchdog -
killall: telnetd: no process killed
killall: ash: no process killed
Sending TERM to remaining processes ... dnsmasq ubusd askfirst urngd logd netifd odhcpd ntpd
Sending KILL to remaining processes ... ntpd
Switching to ramdisk...
Performing system upgrade...
Could not open mtd device: firmware
Can't open device for writing!
cat: write error: Broken pipe
sysupgrade abort[ 670.661483] reboot: Restarting system
and the i2cdump script below returns nothing for me:
for i in 0 1 2 3 4 5 6 7; do for j in 0 1 2 3 4 5 6 7 8 9 a b c d e f; do i2cdump -y 0 0x${i}${j} 2>/dev/null|grep -v 0123456789abcdef|grep -v XXXXXXXXXXXXXXXX; done; done;
Wizard @jwmullally, as you already know I use your awesome Image Builder frontend to hack around with some ramips/rt305x HooToo images.
After successfully adding a new device, I'm having problems improving the Makefile futher, my Makefile-fu ended here.
Could you give me a few hint in the following topics?
Adding a new device I had to touch some base-files files in $(TOPDIR)/target/linux/$(BOARD)/base-files.
These files don't make their ways into image, only with the Image Builder's FILES="path" parameter.
Any hint?
handling patch series
I added the new devices as a separate commit on my branch, so I would like to apply all the patch automatically instead of listing them in Makefile.
OpenWrt uses quilt to handle patch series, but in Image Builder only the wrapper is included. It's command list is empty:
$ ./staging_dir/host/bin/quilt
Usage: quilt [--trace[=verbose]] [--quiltrc=XX] command [-h] ...
quilt --version
Commands are:
Global options:
--trace
Runs the command in bash trace mode (-x). For internal debugging.
--quiltrc file
Use the specified configuration file instead of ~/.quiltrc (or
/builder/shared-workdir/build/staging_dir/host/etc/quilt.quiltrc if ~/.quiltrc does not exist). See the pdf
documentation for details about its possible contents. The
special value "-" causes quilt not to read any configuration
file.
--version
Print the version number and exit immediately.
Should I install quilt at OS level instead trying to revive IB's wrapper?
Thankfully there is an answered question at SO related to Makefile and quilt.
multi-profile support
Now I have ht-tm02 and ht-tm01 and I'd like to build them in one make command.
Without hard coding $(PROFILE) and/or duplicating the whole line:
cd $(BUILDER) && make image PROFILE="$(PROFILE)" EXTRA_IMAGE_NAME="$(EXTRA_IMAGE_NAME)" PACKAGES="$(PACKAGES)" FILES="$(FILES)"
could you give me some hint for magical rules to achieve this?
Hi @xabolcs , good to hear the method is useful, it does look like a handy approach to maintaining custom OpenWRT images.
Yes, I found that too a few months ago. Originally I didn't need to modify anything in base-files so I hadn't noticed it. I think the issue is that with Image Builder, those files come from the already built base-files packages (e.g. here). I found the easiest solution was specifying FILES= as you suggest. Because those are applied at the end of the filesystem build, it means anything can be customized easily, which is nice.
You could try something simple like this in your Makefile. It would save you having to install quilt and update a list of patches.
Image Builder seems designed around building one profile at a time (I think?), so I wasn't able to find any alternative that didn't look overly complex. In the end I just went with the simple approach).
@xabolcs does your latest 21.02.3-1 build work in terms of basic router functions? Despite looking up what I2C is I don't know what the implications of it not starting are in terms of the router working. The LEDs not working isn't a concern.
I've been looking into upgrading various small routers including an HT-02 I have, and I find it strange that the current officially supported release of OpenWRT for the HT-02 and the other TripMates is 19.07.10, despite there being 3 other devices -- D-Link DIR-320 b1, Hame MPR-A2, Olimex RT5350F -- which all seemingly have the same specs but are supported by 22.03.04. If anyone can explain why that might be, I'm curious to know.
It doesn't have the ppp and ppp-mod-pppoe packages, so it won't work with PPPoE ISPs.
These devices have only one ethernet port, which is configured as LAN, so they are not really routers!
Of course you could reconfigure the ethernet port to WAN or the other way around: use the devices as a wireless client.
And here is the new 21.02.7 release!
BusyBox v1.33.2 (2023-03-30 12:18:04 UTC) built-in shell (ash)
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
-----------------------------------------------------
OpenWrt 21.02.7, r16847-f8282da11e
-----------------------------------------------------
| Machine: HooToo HT-TM01 |
| Uptime: 0d, 02:40:36 |
| Load: 0.42 0.12 0.04 |
| Flash: total: 3.4MB, free: 96KB, used: 97% |
| Memory: total: 27.2MB, free: 11.1MB, used: 59% |
| WAN: |
| LAN: 192.168.1.1, leases: 1 |
| radio0: mode: sta, ssid: OpenWrt, channel: 1, conn: 1 |
-----------------------------------------------------
=== WARNING! =====================================
There is no root password defined on this device!
Use the "passwd" command to set up a new password
in order to prevent unauthorized SSH logins.
--------------------------------------------------
root@HT-TM01-E58 ~ # ping -c 4 forum.openwrt.org
PING forum.openwrt.org (139.59.210.197): 56 data bytes
64 bytes from 139.59.210.197: seq=0 ttl=49 time=23.248 ms
64 bytes from 139.59.210.197: seq=1 ttl=49 time=22.967 ms
64 bytes from 139.59.210.197: seq=2 ttl=49 time=22.608 ms
64 bytes from 139.59.210.197: seq=3 ttl=49 time=23.143 ms
--- forum.openwrt.org ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max = 22.608/22.991/23.248 ms
It's work in progress. The most that can happen, it will able to show the battery levels!
But I'm clueless know.
Nobody cares about them ... the 22.03 kernel are greater than 1536 KB, so I'm unsure if they are able to boot it.
For the HooToo HT-TM02 I intentionally disabled it. See below commit for details!
Back in the 21.02 day, the SNAPSHOT wasn't able to boot because of size problems. Fortunately the release version (of 21.02) is a little bit thinner and below 1536K and now I'm able to provide those new 21.02 releases!
@xabolcs thanks for your continued work on this. I'm not a developer so some of what you discuss is over my head. On the networking side of things though I'm familiar with PPP and PPPoE so I know that I won't miss these on a router intended for travel use.
Further, for I2C, since the HT-TM02 doesn't have a battery it sounds it not working shouldn't be an issue.
Do these builds have WireGuard support in the kernel? I see above that one of the previous releases used Linux kernel 5.4.188, and I know that WireGuard was backported to the 5.4 kernel, but beyond that I don't know how to tell if WireGuard is supported in this specific kernel. I'm aware the 360 MHz processor on these devices would be a huge bottleneck to WireGuard speeds, but for my purposes, even if it can hit 10 Mbps, that would prove useful for a travel router.
Also, if you feel like explaining that limit of 1536 kb for the kernel: is that due to the factory partition sizes, or is something else the reason for that limit?
Will the ht tm-02 image work on the ravpower wd-02. Its not entirely clear as the tile of this would indicate yes while the github page doesnt mention this device at all.
(as already commented)
),
)
