Re: A small status update..
Posted by
Roadrunnere42 on
Jul 08, 2020; 1:06pm
URL: https://itus.accessinnov.com/FIRMWARE-Itus-Shield-v2-tp2014p2080.html
Anything that makes life easier for the emmc must be better, but as you say recovery would be a pain. How would you go about recovering an image?
On Wed, 8 Jul 2020 at 13:33, Grommish [via Itus Networks Owners Forum] <
[hidden email]> wrote:
Ok..
Well, this is getting more and more interesting..
First: I've made definitions for both the Router and Bridge modes. I've decided to scrap the Gateway mode and turn it into an emergency de-brick boot (everything will be kept in RAM like a LiveCD. I hate TFTP as much as anyone).
I'm working on trying to build out different formats for each, but keep it combined in OpenWrt. At the end of this, I'm going to really try and get it set as an official device so it'll get regular builds. The first step is figuring out the build system and how the target directories are laid out. I've got to re-arrange the Edgerouter/Edgeroute Lite stuff and create a generic octeon device build, in addition to the Itus builds.
I've got it set to build both Router and Bridge images at the same time (yay).. and build out all the packages as well.. Then, I can push them to the Github repo so everyone can use luCi and/or opkg to install files..
I'm trying to figure out the sysupgrade system, as well.. Currently, I'm building out sysupgrade images that contain the kernel image and a root image. Currently, the rootfs is creates is only 104MB in size, and calling the dd write only writes 104MB, which limits the available space from 850Mb to 104Mb This is.. sub-optimal.. Granted, it's WAY more than routers usually get, but..
When I increase the rootfs size, I need to be able to fit it expanded into RAM before dd'ing it to the device. I also need to be careful not to stall the device while it does the dd, because then the watchdog kicks in and kills the system. I'm ALSO generating a rootfs.tar.gz file that contains the files that I can roll out, but it doesn't put the rootfs.tar.gz and the kernel in the same file ;/ If I can get it to this, then the upgrade system will be complete (for real.. you can even send it thru luCi! :) ) And, it will preserve existing configurations... Or should.. testing has to be done.
After that, it's a matter of trying to get the separate configurations for each mode, if I can..
If I cannot, or can't easily, then both images will be set to act as a router by default.. Since you have to add packages yourself, you can set the network however you need it.. This will at least prevent any chance of IP conflicts on a given network though it'll create a higher barrier to get it setup..
I am seriously looking at using f2fs over ext4 for the filesystem.. f2fs is FAR better and gentler on the eMMC, but it makes recovery a pain if the image doesn't know f2fs (see above about the gateway slot).
Does anyone have any objections regarding f2fs?
Running Itus Shield v2 Firmware