This commit adds missing nmbm parameters to device dts. Before: ``` [ 13.065277] ubi0 warning: ubi_eba_init: cannot reserve enough PEBs for bad PEB handling, reserved 36, need 40 [ 13.184624] ubi0: attached mtd4 (name "ubi", size 226 MiB) [ 13.250170] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes [ 13.332343] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 [ 13.413459] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096 [ 13.496659] ubi0: good PEBs: 1812, bad PEBs: 0, corrupted PEBs: 0 [ 13.569460] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128 [ 13.655780] ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 1717500926 [ 13.764971] ubi0: available PEBs: 0, total reserved PEBs: 1812, PEBs reserved for bad PEB handling: 36 ``` After: ``` [ 0.939053] spi-nand spi0.0: Winbond SPI NAND was found. [ 0.944422] spi-nand spi0.0: 256 MiB, block size: 128 KiB, page size: 2048, OOB size: 128 [ 0.953256] Signature found at block 2047 [0x0ffe0000] [ 0.958389] NMBM management region starts at block 1920 [0x0f000000] [ 0.966032] First info table with writecount 0 found in block 1920 [ 0.975792] Second info table with writecount 0 found in block 1923 [ 0.982076] NMBM has been successfully attached [ 0.986815] 5 fixed-partitions partitions found on MTD device spi0.0 [ 0.993245] Creating 5 MTD partitions on "spi0.0": [ 0.998028] 0x000000000000-0x000000100000 : "BL2" [ 1.003825] 0x000000100000-0x000000180000 : "u-boot-env" [ 1.009867] 0x000000180000-0x000000380000 : "Factory" [ 1.016776] 0x000000380000-0x000000580000 : "FIP" [ 1.023109] 0x000000580000-0x00000e780000 : "ubi" [ 1.724925] ubi0: default fastmap pool size: 90 [ 1.729444] ubi0: default fastmap WL pool size: 45 [ 1.734256] ubi0: attaching mtd4 [ 2.441513] ubi0: scanning is finished [ 2.451382] ubi0: attached mtd4 (name "ubi", size 226 MiB) [ 2.456876] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes [ 2.463753] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048 [ 2.470528] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096 [ 2.477481] ubi0: good PEBs: 1808, bad PEBs: 0, corrupted PEBs: 0 [ 2.483567] ubi0: user volume: 3, internal volumes: 1, max. volumes count: 128 [ 2.490775] ubi0: max/mean erase counter: 2/1, WL threshold: 4096, image sequence number: 0 [ 2.499114] ubi0: available PEBs: 0, total reserved PEBs: 1808, PEBs reserved for bad PEB handling: 38 ``` Signed-off-by: Fil Dunsky <filipp.dunsky@gmail.com> Link: https://github.com/openwrt/openwrt/pull/23153 Signed-off-by: Hauke Mehrtens <hauke@hauke-m.de>
OpenWrt Project is a Linux operating system targeting embedded devices. Instead of trying to create a single, static firmware, OpenWrt provides a fully writable filesystem with package management. This frees you from the application selection and configuration provided by the vendor and allows you to customize the device through the use of packages to suit any application. For developers, OpenWrt is the framework to build an application without having to build a complete firmware around it; for users this means the ability for full customization, to use the device in ways never envisioned.
Sunshine!
Download
Built firmware images are available for many architectures and come with a package selection to be used as WiFi home router. To quickly find a factory image usable to migrate from a vendor stock firmware to OpenWrt, try the Firmware Selector.
If your device is supported, please follow the Info link to see install instructions or consult the support resources listed below.
An advanced user may require additional or specific package. (Toolchain, SDK, ...) For everything else than simple firmware download, try the wiki download page:
Development
To build your own firmware you need a GNU/Linux, BSD or macOS system (case sensitive filesystem required). Cygwin is unsupported because of the lack of a case sensitive file system.
Requirements
You need the following tools to compile OpenWrt, the package names vary between distributions. A complete list with distribution specific packages is found in the Build System Setup documentation.
binutils bzip2 diff find flex gawk gcc-6+ getopt grep install libc-dev libz-dev
make4.1+ perl python3.7+ rsync subversion unzip which
Quickstart
-
Run
./scripts/feeds update -ato obtain all the latest package definitions defined in feeds.conf / feeds.conf.default -
Run
./scripts/feeds install -ato install symlinks for all obtained packages into package/feeds/ -
Run
make menuconfigto select your preferred configuration for the toolchain, target system & firmware packages. -
Run
maketo build your firmware. This will download all sources, build the cross-compile toolchain and then cross-compile the GNU/Linux kernel & all chosen applications for your target system.
Related Repositories
The main repository uses multiple sub-repositories to manage packages of
different categories. All packages are installed via the OpenWrt package
manager called opkg. If you're looking to develop the web interface or port
packages to OpenWrt, please find the fitting repository below.
-
LuCI Web Interface: Modern and modular interface to control the device via a web browser.
-
OpenWrt Packages: Community repository of ported packages.
-
OpenWrt Routing: Packages specifically focused on (mesh) routing.
-
OpenWrt Video: Packages specifically focused on display servers and clients (Xorg and Wayland).
Support Information
For a list of supported devices see the OpenWrt Hardware Database
Documentation
Support Community
- Forum: For usage, projects, discussions and hardware advise.
- Support Chat: Channel
#openwrton oftc.net.
Developer Community
- Bug Reports: Report bugs in OpenWrt
- Dev Mailing List: Send patches
- Dev Chat: Channel
#openwrt-develon oftc.net.
License
OpenWrt is licensed under GPL-2.0
