I could not create a custom image 24.10.0-rc2 because all the packages had not been built and made available to users.
I created the custom image, it is installed and operational.
Now, with LuCi, I have access to Update lists..
It's as if a file was missing in the basic firmware allowing access to the Internet for a 4G/5G box purchased personally, the SIM card has a mobile number and not a landline number.
I know that there is no connection problem, with a 4G box, SIM card provided by an ISP.
I will be able to configure my router.
Finally, I know why an image cannot be built.
The only solution, with a personal box, is to do tests in "OpenWrt Firmware selector" and wait for all the packages to be built. Phew! what a pain! heh! heh!
Manual installation of IPK packages remains pending. A solution would be welcome, my knowledge is limited, even if I browse the forum.
I used this (well the previous release that was euphoric blue, couldn't get the euphoric blue charge cable so settled for pastel blue). OfficeWorks - Otto 30W usb-c pastel blue
Would you mind providing some further detail on exactly how you successfully upgraded the firmware? The OpenWrt One Howto document says "The easiest way to do is is via USB." Did you prepare a USB drive with the openwrt-mediatek-filogic-openwrt_one-squashfs-sysupgrade.itb file? Did you then boot with that USB drive inserted in the USB 2.0 host port? If you did not do this USB drive method then what other method did you use to upgrade the firmware? Thanks!
in case you wonder...
then copied that via SSH to the /tmp directory on the One and
logged into the One (via the USB console)
called cd /tmp ; sysupgrade -v ./openwrt-24.10.0-rc4-79659d805e8c-mediatek-filogic-openwrt_one-squashfs-sysupgrade.itb
and watched this succeed...
(I had done this after the first boot and basic configuration to switch to rc02, snapshots are nice, but for an AP I prefer luci, and it turned out quickly that instead of getting a nice new toy, my One will become a dumb AP pretty soon...)
Indeed I did successfully update the firmware using the USB method. I figured out a few things to do so though which may be worth mentioning to others.
Although the current OpenWrt One Howto document doesn't specify this the TOH page https://openwrt.org/toh/openwrt/one provides additional detail to format the USB drive as FAT32.
The bootloader looks for a file named exactly openwrt-mediatek-filogic-openwrt_one-squashfs-sysupgrade.itb. So if you download, for example, openwrt-24.10.0-rc4-mediatek-filogic-openwrt_one-squashfs-sysupgrade.itb from firmware selector then you would have to rename the file on the USB drive to delete '24.10.0-rc4-' characters out of it.
The youtube video that vanst pointed to illustrated that the front side LED did not turn green by itself because of an LED light loop error. I experienced the same thing -- the bootloader hung on this error after it actually did already sysupgrade the firmware, and it continued to just flash the amber light closest to the USB 2.0 host port. But I was able to see what had happened in the USB serial console, which was very helpful. This hang on this error after the sysupgrade indeed in this case prevented completion of the firmware update process that the OpenWrt One Howto document presumes. But because the sysupgrade actually did complete I just power-cycled the device after ensuring that the DIP switch was still on NAND, and it booted with the sysupgraded firmware.
Thanks all for the work and support for this device! Now to just figure out how to persist settings through the next sysupgrade.
Always taking a backup prior to an upgrade is highly suggested for reference if needed. For the most part, most settings will migrate properly from prior release to current release under sysupgrade. Just go over the Release Announcement to verify prior to flashing.
USB Flashing NAND recovery method would not work for me at all as it would not invoke ubiformat ?
would get output below and just reboot without flashing
(ouput was reduced as it was long)
Jump to BL
NOTICE: BL2: v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7981-spim-nand-ubi-ddr4)
NOTICE: BL2: Built : 22:11:55, Oct 22 2024
NOTICE: WDT: Cold boot
NOTICE: WDT: disabled
NOTICE: EMI: Using DDR4 settings
NOTICE: EMI: Detected DRAM size: 1024MB
NOTICE: EMI: complex R/W mem test passed
NOTICE: CPU: MT7981 (1300MHz)
NOTICE: SPI_NAND parses attributes from parameter page.
NOTICE: SPI_NAND Detected ID 0xef
NOTICE: Page size 2048, Block size 131072, size 268435456
NOTICE: UBI: scanning [0x100000 - 0x10000000] ...
NOTICE: UBI: Bad EC magic in block 1060 ffffffff
NOTICE: UBI: Bad EC magic in block 1061 ffffffff
NOTICE: UBI: Bad EC magic in block 1062 ffffffff
NOTICE: UBI: Bad EC magic in block 1063 ffffffff
..
NOTICE: UBI: Bad EC magic in block 2026 ffffffff
NOTICE: UBI: Bad EC magic in block 2027 ffffffff
NOTICE: UBI: Bad EC magic in block 2028 ffffffff
NOTICE: UBI: Bad EC magic in block 2029 ffffffff
NOTICE: UBI: Bad EC magic in block 2030 ffffffff
NOTICE: UBI: Bad EC magic in block 2031 ffffffff
NOTICE: UBI: Bad EC magic in block 2032 ffffffff
NOTICE: UBI: Bad EC magic in block 2033 ffffffff
NOTICE: UBI: Bad EC magic in block 2034 ffffffff
NOTICE: UBI: Bad EC magic in block 2035 ffffffff
NOTICE: UBI: Bad EC magic in block 2036 ffffffff
NOTICE: UBI: Bad EC magic in block 2037 ffffffff
NOTICE: UBI: Bad EC magic in block 2038 ffffffff
NOTICE: UBI: Bad VID magic in block 2039 4e4d4d30
NOTICE: UBI: scanning is finished
NOTICE: UBI: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
NOTICE: UBI: VID header offset: 2048 (aligned 2048), data offset: 4096
NOTICE: UBI: Volume fip (Id #2) size is 960689 bytes
NOTICE: BL2: Booting BL31
NOTICE: BL31: v2.10.0 (release):OpenWrt v2024.01.17~bacca82a-3 (mt7981-spim-nand-ubi-ddr4)
NOTICE: BL31: Built : 22:11:55, Oct 22 2024
U-Boot 2024.10-OpenWrt-r27893-b6bbc76c0b (Oct 22 2024 - 22:11:55 +0000)
CPU: MediaTek MT7981
Model: OpenWrt One
DRAM: 1 GiB
Core: 44 devices, 20 uclasses, devicetree: separate
spi-nand: spi_nand spi_nand@0: Winbond SPI NAND was found.
spi-nand: spi_nand spi_nand@0: 256 MiB, block size: 128 KiB, page size: 2048, OOB size: 128
Loading Environment from UBI... SF: Detected w25q128 with page size 256 Bytes, erase size 4 KiB, total 16 MiB
ubi0 error: scan_peb: bad image sequence number 1705631169 in PEB 1016, expected 1716284138
Erase counter header dump:
magic 0x55424923
version 1
ec 1
vid_hdr_offset 2048
data_offset 4096
image_seq 1705631169
hdr_crc 0xe39430d5
erase counter header hexdump:
00000000: 55 42 49 23 01 00 00 00 00 00 00 00 00 00 00 01 00 00 08 00 00 00 10 00 65 a9 dd c1 00 00 00 00 UBI#....................e.......
00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e3 94 30 d5 ..............................0.
ubi0 error: ubi_attach_mtd_dev: failed to attach mtd3, error -22
UBI error: cannot attach mtd3
UBI error: cannot initialize UBI, error -22
UBI init error 22
Please check, if the correct MTD partition is used (size big enough?)
** Cannot find mtd partition "ubi"
In: serial@11002000
Out: serial@11002000
Err: serial@11002000
reset button found
Loading Environment from UBI... ubi0 error: scan_peb: bad image sequence number 1705631169 in PEB 1016, expected 1716284138
Erase counter header dump:
magic 0x55424923
version 1
ec 1
vid_hdr_offset 2048
data_offset 4096
image_seq 1705631169
hdr_crc 0xe39430d5
erase counter header hexdump:
00000000: 55 42 49 23 01 00 00 00 00 00 00 00 00 00 00 01 00 00 08 00 00 00 10 00 65 a9 dd c1 00 00 00 00 UBI#....................e.......
00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e3 94 30 d5 ..............................0.
ubi0 error: ubi_attach_mtd_dev: failed to attach mtd3, error -22
UBI error: cannot attach mtd3
UBI error: cannot initialize UBI, error -22
UBI init error 22
Please check, if the correct MTD partition is used (size big enough?)
** Cannot find mtd partition "ubi"
Net:
Warning: ethernet@15100000 (eth0) using random MAC address - d2:88:be:ff:4f:35
eth0: ethernet@15100000
Reading 131072 byte(s) at offset 0x00000000
Error, no UBI device selected!
Error, no UBI device selected!
Error, no UBI device selected!
Error, no UBI device selected!
Saving Environment to UBI... ubi0 error: scan_peb: bad image sequence number 1705631169 in PEB 1016, expected 1716284138
Erase counter header dump:
magic 0x55424923
version 1
ec 1
vid_hdr_offset 2048
data_offset 4096
image_seq 1705631169
hdr_crc 0xe39430d5
erase counter header hexdump:
00000000: 55 42 49 23 01 00 00 00 00 00 00 00 00 00 00 01 00 00 08 00 00 00 10 00 65 a9 dd c1 00 00 00 00 UBI#....................e.......
00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e3 94 30 d5 ..............................0.
ubi0 error: ubi_attach_mtd_dev: failed to attach mtd3, error -22
UBI error: cannot attach mtd3
UBI error: cannot initialize UBI, error -22
UBI init error 22
Please check, if the correct MTD partition is used (size big enough?)
** Cannot find mtd partition "ubi"
Failed (1)
Saving Environment to UBI... ubi0 error: scan_peb: bad image sequence number 1705631169 in PEB 1016, expected 1716284138
Erase counter header dump:
magic 0x55424923
version 1
ec 1
vid_hdr_offset 2048
data_offset 4096
image_seq 1705631169
hdr_crc 0xe39430d5
erase counter header hexdump:
00000000: 55 42 49 23 01 00 00 00 00 00 00 00 00 00 00 01 00 00 08 00 00 00 10 00 65 a9 dd c1 00 00 00 00 UBI#....................e.......
00000020: 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 e3 94 30 d5 ..............................0.
ubi0 error: ubi_attach_mtd_dev: failed to attach mtd3, error -22
UBI error: cannot attach mtd3
UBI error: cannot initialize UBI, error -22
UBI init error 22
Please check, if the correct MTD partition is used (size big enough?)```
only tftp-boot with sysupgrae method work successfully. (as it actually invoked ubiformat)
initramfs boot
e[?25le[2Je[1;1He[1;1He[2Ke[2;3H e[0;34m( ( ( e[1;39mOpenWrte[0;34m ) ) ) e[0;36m[SPI-NAND]e[0m e[33mU-Boot 2024.10-OpenWrt-r27893-b6bbc76c0b (Oct 22 2024 - 22:11:55 +0000)e[0me[0Ke[3;1He[2Ke[16;1He[2Ke[17;3HPress UP/DOWN to move, ENTER to select, ESC to quite[0Ke[18;1He[2Ke[4;7He[7m1. Run default boot command.e[0me[5;7H2. Boot system via TFTP.e[6;7H3. Boot production system from NAND.e[7;7H4. Boot recovery system from NAND.e[8;7H5. Load production system via TFTP then write to NAND.e[9;7H6. Load recovery system via TFTP then write to NAND.e[10;7H7. e[31mLoad BL31+U-Boot FIP via TFTP then write to NAND.e[0me[11;7H8. e[31mLoad BL2 preloader via TFTP then write to NAND.e[0me[12;7H9. Reboot.e[13;7Ha. Reset all settings to factory defaults.e[14;7H0. Exite[16;3HHit any key to stop autoboot: 3 e[16;1He[2Ke[1;1He[2Ke[2;3H e[0;34m( ( ( e[1;39mOpenWrte[0;34m ) ) ) e[0;36m[SPI-NAND]e[0m e[33mU-Boot 2024.10-OpenWrt-r27893-b6bbc76c0b (Oct 22 2024 - 22:11:55 +0000)e[0me[0Ke[3;1He[2Ke[16;1He[2Ke[17;3HPress UP/DOWN to move, ENTER to select, ESC to quite[0Ke[18;1He[2Ke[4;7H1. Run default boot command.e[5;7He[7m2. Boot system via TFTP.e[0me[6;7H3. Boot production system from NAND.e[7;7H4. Boot recovery system from NAND.e[8;7H5. Load production system via TFTP then write to NAND.e[9;7H6. Load recovery system via TFTP then write to NAND.e[10;7H7. e[31mLoad BL31+U-Boot FIP via TFTP then write to NAND.e[0me[11;7H8. e[31mLoad BL2 preloader via TFTP then write to NAND.e[0me[12;7H9. Reboot.e[13;7Ha. Reset all settings to factory defaults.e[14;7H0. Exite[1;1He[2Ke[2;3H e[0;34m( ( ( e[1;39mOpenWrte[0;34m ) ) ) e[0;36m[SPI-NAND]e[0m e[33mU-Boot 2024.10-OpenWrt-r27893-b6bbc76c0b (Oct 22 2024 - 22:11:55 +0000)e[0me[0Ke[3;1He[2Ke[16;1He[2Ke[17;3HPress UP/DOWN to move, ENTER to select, ESC to quite[0Ke[18;1He[2Ke[4;7H1. Run default boot command.e[5;7H2. Boot system via TFTP.e[6;7He[7m3. Boot production system from NAND.e[0me[7;7H4. Boot recovery system from NAND.e[8;7H5. Load production system via TFTP then write to NAND.e[9;7H6. Load recovery system via TFTP then write to NAND.e[10;7H7. e[31mLoad BL31+U-Boot FIP via TFTP then write to NAND.e[0me[11;7H8. e[31mLoad BL2 preloader via TFTP then write to NAND.e[0me[12;7H9. Reboot.e[13;7Ha. Reset all settings to factory defaults.e[14;7H0. Exite[1;1He[2Ke[2;3H e[0;34m( ( ( e[1;39mOpenWrte[0;34m ) ) ) e[0;36m[SPI-NAND]e[0m e[33mU-Boot 2024.10-OpenWrt-r27893-b6bbc76c0b (Oct 22 2024 - 22:11:55 +0000)e[0me[0Ke[3;1He[2Ke[16;1He[2Ke[17;3HPress UP/DOWN to move, ENTER to select, ESC to quite[0Ke[18;1He[2Ke[4;7H1. Run default boot command.e[5;7He[7m2. Boot system via TFTP.e[0me[6;7H3. Boot production system from NAND.e[7;7H4. Boot recovery system from NAND.e[8;7H5. Load production system via TFTP then write to NAND.e[9;7H6. Load recovery system via TFTP then write to NAND.e[10;7H7. e[31mLoad BL31+U-Boot FIP via TFTP then write to NAND.e[0me[11;7H8. e[31mLoad BL2 preloader via TFTP then write to NAND.e[0me[12;7H9. Reboot.e[13;7Ha. Reset all settings to factory defaults.e[14;7H0. Exite[1;1He[2Ke[2;3H e[0;34m( ( ( e[1;39mOpenWrte[0;34m ) ) ) e[0;36m[SPI-NAND]e[0m e[33mU-Boot 2024.10-OpenWrt-r27893-b6bbc76c0b (Oct 22 2024 - 22:11:55 +0000)e[0me[0Ke[3;1He[2Ke[16;1He[2Ke[17;3HPress UP/DOWN to move, ENTER to select, ESC to quite[0Ke[18;1He[2Ke[4;7He[7m1. Run default boot command.e[0me[5;7H2. Boot system via TFTP.e[6;7H3. Boot production system from NAND.e[7;7H4. Boot recovery system from NAND.e[8;7H5. Load production system via TFTP then write to NAND.e[9;7H6. Load recovery system via TFTP then write to NAND.e[10;7H7. e[31mLoad BL31+U-Boot FIP via TFTP then write to NAND.e[0me[11;7H8. e[31mLoad BL2 preloader via TFTP then write to NAND.e[0me[12;7H9. Reboot.e[13;7Ha. Reset all settings to factory defaults.e[14;7H0. Exite[1;1He[2Ke[2;3H e[0;34m( ( ( e[1;39mOpenWrte[0;34m ) ) ) e[0;36m[SPI-NAND]e[0m e[33mU-Boot 2024.10-OpenWrt-r27893-b6bbc76c0b (Oct 22 2024 - 22:11:55 +0000)e[0me[0Ke[3;1He[2Ke[16;1He[2Ke[17;3HPress UP/DOWN to move, ENTER to select, ESC to quite[0Ke[18;1He[2Ke[4;7H1. Run default boot command.e[5;7He[7m2. Boot system via TFTP.e[0me[6;7H3. Boot production system from NAND.e[7;7H4. Boot recovery system from NAND.e[8;7H5. Load production system via TFTP then write to NAND.e[9;7H6. Load recovery system via TFTP then write to NAND.e[10;7H7. e[31mLoad BL31+U-Boot FIP via TFTP then write to NAND.e[0me[11;7H8. e[31mLoad BL2 preloader via TFTP then write to NAND.e[0me[12;7H9. Reboot.e[13;7Ha. Reset all settings to factory defaults.e[14;7H0. Exite[?25he[2Je[1;1HUsing ethernet@15100000 device
TFTP from server 192.168.11.23; our IP address is 192.168.11.11
Filename 'openwrt-mediatek-filogic-openwrt_one-initramfs.itb'.
Load address: 0x46000000
Loading: *#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#################################################################
#####
7.7 MiB/s
done
..
root@OpenWrt:/tmp# wget -c https://downloads.openwrt.org/snapshots//targets/medi
atek/filogic/openwrt-mediatek-filogic-openwrt_one-factory.ubi
Downloading 'https://downloads.openwrt.org/snapshots//targets/mediatek/filogic/openwrt-mediatek-filogic-openwrt_one-factory.ubi'
Connecting to 151.101.66.132:443
Writing to 'openwrt-mediatek-filogic-openwrt_one-factory.ubi'
openwrt-mediatek-fil 5% |* | 1155k 0:00:17 ETA
openwrt-mediatek-fil 11% |*** | 2384k 0:00:16 ETA
openwrt-mediatek-fil 15% |**** | 3392k 0:00:16 ETA
openwrt-mediatek-fil 21% |****** | 4561k 0:00:14 ETA
openwrt-mediatek-fil 25% |******* | 5484k 0:00:14 ETA
openwrt-mediatek-fil 29% |********* | 6348k 0:00:14 ETA
openwrt-mediatek-fil 36% |*********** | 7842k 0:00:12 ETA
openwrt-mediatek-fil 42% |************* | 9170k 0:00:10 ETA
openwrt-mediatek-fil 47% |************** | 10130k 0:00:10 ETA
openwrt-mediatek-fil 50% |*************** | 10880k 0:00:09 ETA
openwrt-mediatek-fil 54% |***************** | 11808k 0:00:09 ETA
openwrt-mediatek-fil 60% |****************** | 13062k 0:00:07 ETA
openwrt-mediatek-fil 64% |******************** | 13966k 0:00:07 ETA
openwrt-mediatek-fil 69% |********************* | 14992k 0:00:06 ETA
openwrt-mediatek-fil 73% |********************** | 15856k 0:00:05 ETA
openwrt-mediatek-fil 78% |************************ | 16864k 0:00:04 ETA
openwrt-mediatek-fil 83% |************************* | 17856k 0:00:03 ETA
openwrt-mediatek-fil 88% |*************************** | 19035k 0:00:02 ETA
openwrt-mediatek-fil 92% |**************************** | 19915k 0:00:01 ETA
openwrt-mediatek-fil 95% |***************************** | 20563k 0:00:00 ETA
openwrt-mediatek-fil 100% |*******************************| 21504k 0:00:00 ETA
Download completed (22020096 bytes)
root@OpenWrt:/tmp# ls
e[0;0mTZe[m
e[0;0mdhcp.leasese[m
e[1;34mdnsmasq.cfg01411c.de[m
e[1;34metce[m
e[1;34mhostse[m
e[1;34mlibe[m
e[1;34mlocke[m
e[1;34mloge[m
e[0;0mopenwrt-mediatek-filogic-openwrt_one-factory.ubie[m
e[0;0mresolv.confe[m
e[1;34mresolv.conf.de[m
e[1;34mrune[m
e[1;34mshme[m
e[1;34mstatee[m
e[1;34msysinfoe[m
e[1;34mtmpe[m
root@OpenWrt:/tmp# sysup
root@OpenWrt:/tmp# sysupgrade e[J-n -v ./ope
root@OpenWrt:/tmp# sysupgrade -n -v ./openwrt-mediatek-filogic-openwrt_one-facto
ry.ubi e[J
Thu Oct 24 20:49:05 UTC 2024 upgrade: Image metadata not present
Thu Oct 24 20:49:05 UTC 2024 upgrade: Use sysupgrade -F to override this check when downgrading or flashing to vendor firmware
Image check failed.
root@OpenWrt:/tmp#
root@OpenWrt:/tmp# sysupgrade -n -v ./openwrt-mediatek-filogic-openwrt_one-facto
ry.ubi e[J
e[1Ae[79Cv -./openwrt-mediatek-filogic-openwrt_one-fact
ory.ubi
e[1Ae[37CF./openwrt-mediatek-filogic-openwrt_one-fac
tory.ubi
e[1Ae[38C ./openwrt-mediatek-filogic-openwrt_one-fa
ctory.ubi
e[1Ae[39C./openwrt-mediatek-filogic-openwrt_one-fa
ctory.ubi
Thu Oct 24 20:49:29 UTC 2024 upgrade: Image metadata not present
Image check failed but --force given - will update anyway!
Thu Oct 24 20:49:29 UTC 2024 upgrade: Commencing upgrade. Closing all shell sessions.
Command failed: Connection failed
-ash: can't set tty process group: Not a tty
[1]+ Done(10) sysupgrade -n -v -F ./openwrt-mediatek-filogic-openwrt_one-factory.ubi
root@OpenWrt:/tmp# Watchdog handover: fd=3
- watchdog -
Watchdog does not have CARDRESET support
Thu Oct 24 20:49:29 UTC 2024 upgrade: Sending TERM to remaining processes ...
Thu Oct 24 20:49:33 UTC 2024 upgrade: Sending KILL to remaining processes ...
[ 216.901428] stage2 (3534): drop_caches: 3
Thu Oct 24 20:49:40 UTC 2024 upgrade: Switching to ramdisk...
Thu Oct 24 20:49:41 UTC 2024 upgrade: Performing system upgrade...
ubiformat: mtd5 (nand), size 267386880 bytes (255.0 MiB), 2040 eraseblocks of 131072 bytes (128.0 KiB), min. I/O size 2048 bytes
libscan: scanning eraseblock 0 -- 0 % complete
..
ubiformat: flashing eraseblock 167 -- 100 % complete
ubiformat: formatting eraseblock 168 -- 0 % complete
..
ubiformat: formatting eraseblock 217 -- 2 % complete
ubiformat: formatting eraseblock 1986 -- 97 % complete
u[ 244.695120] ubi0: default fastmap pool size: 100
biformat: format[ 244.701113] ubi0: default fastmap WL pool size: 50
ting eraseblock [ 244.707258] ubi0: attaching mtd5
1987 -- 97 % complete
..
ubiformat: formatting eraseblock 2014 -- 98 % complete
ubifo[ 244.846816] UBI: EOF marker found, PEBs from 163 will be erased
rmat: formatting[ 244.854519] ubi0: scanning is finished
eraseblock 2015 -- 98 % complete
ubiformat: formatting eraseblock 2016 -- 98 % complete
ubiformat: formatting eraseblock 2017 -- 98 % compl[ 244.870697] ubi0: attached mtd5 (name "ubi", size 255 MiB)
ete
ubiformat:[ 244.876857] ubi0: PEB size: 131072 bytes (128 KiB), LEB size: 126976 bytes
formatting eras[ 244.885082] ubi0: min./max. I/O unit sizes: 2048/2048, sub-page size 2048
eblock 2018 -- 9[ 244.893246] ubi0: VID header offset: 2048 (aligned 2048), data offset: 4096
8 % complete
u[ 244.901573] ubi0: good PEBs: 2040, bad PEBs: 0, corrupted PEBs: 0
biformat: format[ 244.909033] ubi0: user volume: 5, internal volumes: 1, max. volumes count: 128
ting eraseblock [ 244.917621] ubi0: max/mean erase counter: 1/1, WL threshold: 4096, image sequence number: 630094542
2019 -- 98 % com[ 244.928031] ubi0: available PEBs: 1815, total reserved PEBs: 225, PEBs reserved for bad PEB handling: 40
plete
ubiforma[ 244.938885] ubi0: background thread "ubi_bgt0d" started, PID 4242
t: formatting er[ 244.947258] block ubiblock0_4: created from ubi0:4(fit)
aseblock 2020 -- 98 % complete
ubiformat: formatting eraseblock 2021 -- 99 % complete
ubiformat: formatting eraseblock 2022 -- 99 % complete
ubiformat: fo[ 244.965668] reboot: Restarting system
Now running Meshtastic (LoRa Mesh Communication) on OpenWRT with a LR1110 SPI LoRa miktroBUS module
Well, a little background on why you are using the SPI-NAND U-Boot and the numeric menu option used would probably be helpful. FWIW, I’ve yet to need SPI-NOR or SPI-NAND U-Boot in day to day use of OO.
