How do I see my device tree? Just ls -l /dev/mtd0, or something else?by rsantag - Debian
I think I found what I need - nand-utils package. I installed it, but I'm getting permission denied error: Quoteroot@OpenWrt:/tmp# flash_erase /dev/mtd0 0 4 flash_erase: error!: /dev/mtd0 error 13 (Permission denied) root@OpenWrt:/tmp# ls -l /dev/mtd0 crw------- 1 root root 90, 0 Jan 1 1970 /dev/mtd0 root@OpenWrt:/tmp# This is what current mtd partitiby rsantag - Debian
Hello. I have another Pogoplug V4 that I bought used and that doesn't boot, so I was going to install your uboot & openwrt. I was able to get to the CE boot loader from a serial console, then loaded openwrt via tftp and booted it. I'm now logged in to openwrt, but I'm trying to figure out how to do flash_erase, nandwrite and nanddump. Not finding those utilities on openwrby rsantag - Debian
And to wrap things up... I decided to install the 2017.07 uboot on my other Pogoplug, which was running 2014.07 uboot. It has /uboot.mtd0.dockstar.original.kwb on /dev/mtd4 (root), so was still able to boot to the original OS using boot chaining. After that was successfully install, I added bootcmd_pogo and modified bootcmd_exec as follows: Quotefw_setenv bootcmd_exec 'if run lby rsantag - Debian
Well, that was really easy. And OpenWrt is very cool! Thanks very much for your help, Bodhi! Ralphby rsantag - Debian
OK, reading through that openwrt thread, it looks like everything after the u-boot partition gets combined into a single partition for the new openwrt install. So, since I've already got uboot set up, I think this is what I would do: From debian: Quotefw_setenv mtdparts 'mtdparts=orion_nand:0x200000@0x0(u-boot),-@0x200000(ubi)' fw_setenv partition 'nand0,0' fw_seteby rsantag - Debian
Which partition does openwrt get installed on? Is this what's documented in part 3 of https://forum.doozan.com/read.php?4,100764,101409#msg-101409 Ralphby rsantag - Debian
First mtdparts, root parition shows active QuotePogov4> setenv partition nand0,4 setenv partition nand0,4 Pogov4> mtdparts mtdparts device nand0 <orion_nand>, # parts = 5 #: name size offset mask_flags 0: u-boot 0x00200000 0x00000000 0 1: uImage 0x00300000 0x00200000 0 2: uImage2by rsantag - Debian
I enabled netconsole and tried booting with "bootcmd_exec=run bootcmd_pogo" in /boot/uEnv.txt again. This is what I see in the console log (I stripped out 900+ of the "ubi0: fixable bit-flip detected at PEB ###" errors to keep this post a little smaller QuoteU-Boot 2017.07-tld-1 (Sep 05 2017 - 00:34:01 -0700) Pogoplug V4 gcc (Debian 6.3.0-18) 6.3.0 20170516 GNU ld (GNUby rsantag - Debian
OK, "flash_erase /dev/mtd4 0 0" worked, thanks. I don't currently have a serial console on this device. But here's what I was thinking re: /boot/uEnv.txt: The first thing bootcmd runs is bootcmd_uenv, so after that completes, bootcmd_exec should be set to what is in uEnv.txt. If so, then if the pogo successfully boots (it does), then at a minimum that bootcmd_exec willby rsantag - Debian
Yep, -n is same as --noecc, and it appears that --omitoob is default. The only oob options it gives are -oob and -onlyoob Quoteroot@debian:~# nandwrite -h Usage: nandwrite MTD_DEVICE Writes to the specified MTD device. -a, --autoplace Use auto OOB layout -k, --skip-all-ffs Skip pages that contain only 0xff bytes -m, --markbad Mark blocks bad if write faby rsantag - Debian
I was able to do ubiattach for mtd3 Quoteroot@debian:~# ubiattach /dev/ubi_ctrl -m 3 UBI device number 0, total 64 LEBs (8257536 bytes, 7.9 MiB), available 40 LEBs (5160960 bytes, 4.9 MiB), LEB size 129024 bytes (126.0 KiB) But I still get the "unknown filesystem type 'ubifs' error. (I just reused /mnt/ubi4 directory I'd created before) Quoteroot@debian:~# mount -t uby rsantag - Debian
No ubiattach command, so had to install mtd-utils. Then tried the ubiattach, but get an error 22 root@debian:~# ubiattach /dev/ubi_ctrl -m 4 ubiattach: error!: cannot attach mtd4 error 22 (Invalid argument) Tried doing the modprobe first, but same error root@debian:~# modprobe ubi mtd=4 root@debian:~# ubiattach /dev/ubi_ctrl -m 4 ubiattach: error!: cannot attach mtd4by rsantag - Debian
Here is my dmesg [ 0.000000] Booting Linux on physical CPU 0x0 [ 0.000000] Linux version 5.8.3-kirkwood-tld-1 (root@tldDebian) (gcc (Debian 8.3.0-6) 8.3.0, GNU ld (GNU Binutils for Debian) 2.31.1) #1.0 PREEMPT Sat Aug 22 16:10:01 PDT 2020 [ 0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f [ 0.000000] CPU: VIVT data cache, VIVT instruction cache [by rsantag - Debian
OK, I'm definitely unfamiliar with mtd, ubi and ubifs, so please take pity on me, but this is what I tried: root@debian:~# grep ubi /proc/filesystems nodev ubifs root@debian:~# modprobe ubi mtd=4 root@debian:~# mkdir /mnt/ubi4 root@debian:~# mount -t ubifs ubi4 /mnt/ubi4 mount: unknown filesystem type 'ubifs' root@debian:~# The only ubi I see in /dev is /dev/ubi_ctrlby rsantag - Debian
OK, so digging into this a little more, my other Pogos have /uboot.mtd0.dockstar.original.kwb on the mtd4 root partition, which seems to be what bootcmd_pogo loads with ubifsload. I'm guessing this is the original, unmodified /dev/mtd0 uboot partition? So, the uboot.2014.07 uboot loads and runs this as a last resort, which in turn boots the original OS. So, problem is that I'm notby rsantag - Debian
Thanks. Yeah, that was my thought - as a rescue OS. My other Pogos are running the 2014 Uboot, which does boot to the stock OS if no SD or USB boot device. I know the older U-Boot that I'm running on my other Pogos tries to boot off MMC, then USB, then Sata, then internal flash. root@pogoplug:~# fw_printenv bootcmd bootcmd=run bootcmd_mmc; run bootcmd_usb; run bootcmd_sata; run boby rsantag - Debian
OK, thanks again. That helped. Hopefully the last question: Step e.2 says to restore mtdparts, but this wasn't set in the original env variables. # grep mtdparts current_envs.txt # wc -l current_envs.txt 50 current_envs.txt # However, I have another Pogo same model that it IS set: root@pogoplug:~# fw_printenv mtdparts mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImby rsantag - Debian
OK, downloaded the U-Boot and tools from dropbox. Extracted tools and moved to /usr/local/bin, and moved fw_env.config to /etc. When I run fw_printenv I get Bad CRC error and only a handful of env variables are listed # fw_printenv Warning: Bad CRC, using default environment bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:by rsantag - Debian
Thanks for the quick reply. I've give it a go later today and post my results. rsantagby rsantag - Debian
Hello. I'm new to this forum, and fairly new with the Pogoplug, but experienced with Unix/Linux. I bought a Pogoplug V4-A3-01 that was configured by the previous owner to boot Arch Linux from USB drive. I'm booting debian from SD on my other Pogoplugs, which is what I'd like to do on this one. I'm not able to see it on my network when I boot to the original Cloud Engby rsantag - Debian