2015.10 U-Boot for Pogoplug V3 (OXNAS OX820)

pulledfromthewater,


> scanning bus 0 for devices... EHCI timed out on TD
> - token=0x80008c80
> unable to get device descriptor (error=-1)
> 1 USB Device(s) found
> scanning usb for storage devices... 0
> Storage Device(s) found

It's a common problem with USB drives. Especially if the drive is HDD. Try these (in this order)

- Increase usb_ready_retry=60
- Plug in the USB port next to the ethernet port.
- Reformat the drive (wipe out partition using fdisk).
- Use a different drive (preferably Sandisk brand for thumb drive).

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

what is the meanings of spl？in this version the u boot partition need 2M？does it use second boot technology？can I use nanddump to backup original uboot? thanks

I've move the posts to its own topic:

Pogo Oxnas V3 with 256MB RAM modding: http://forum.doozan.com/read.php?3,32860

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 1 time(s). Last edit at 03/06/2017 01:34PM by bodhi.

cat /proc/mtd

root@PogoPlug:~# cat /proc/mtd 
dev:    size   erasesize  name
mtd0: 00040000 00020000 "stage1"
mtd1: 00160000 00020000 "u-boot"
mtd2: 00040000 00020000 "u-boot-env"
mtd3: 02000000 00020000 "boot"
mtd4: 00020000 00020000 "factory"
mtd5: 00a00000 00020000 "kernel"
mtd6: 07200000 00020000 "rootfs"
mtd7: 07e00000 00020000 "firmware"
mtd8: 08000000 00020000 "fullflash"

cat /etc/fw_env.config

# MTD device name	Device offset	Env. size	Flash sector size	Number of sectors
/dev/mtd2       0x0        0x2000      0x40000

root@PogoPlug:~# dmesg | grep -i 'bad'
[    8.100000] Scanning device for bad blocks
[    8.230000] Bad eraseblock 928 at 0x000007400000
[    8.800000] UBI warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 8, need 9
[    8.830000] UBI: number of bad PEBs:         1
[    8.870000] UBI: number of PEBs reserved for bad PEB handling: 8

root@PogoPlug:~# /usr/sbin/flash_erase /dev/mtd0 0x0 6
Erasing 128 Kibyte @ 20000 -- 16 % complete libmtd: error!: bad eraseblock number 2, mtd0 has 2 eraseblocks
flash_erase: error!: /dev/mtd0: MTD get bad block failed
             error 22 (Invalid argument)
root@PogoPlug:~# /usr/sbin/nandwrite /dev/mtd0 mtd0
Writing data to block 0 at offset 0x0
Writing data to block 1 at offset 0x20000

The box is still work, Can I flash this u-boot?

ming Wrote:
-------------------------------------------------------
> cat /proc/mtd
>

> root@PogoPlug:~# cat /proc/mtd
> dev:    size   erasesize  name
> mtd0: 00040000 00020000 "stage1"
> mtd1: 00160000 00020000 "u-boot"
> mtd2: 00040000 00020000 "u-boot-env"
> mtd3: 02000000 00020000 "boot"
> mtd4: 00020000 00020000 "factory"
> mtd5: 00a00000 00020000 "kernel"
> mtd6: 07200000 00020000 "rootfs"
> mtd7: 07e00000 00020000 "firmware"
> mtd8: 08000000 00020000 "fullflash"
>

> cat /etc/fw_env.config
>

> # MTD device name	Device offset	Env. size	Flash se
> ctor size	Number of sectors
> /dev/mtd2       0x0        0x2000      0x40000
>

>

> root@PogoPlug:~# dmesg | grep -i 'bad'
> [    8.100000] Scanning device for bad blocks
> [    8.230000] Bad eraseblock 928 at 0x00000740000
> 0
> [    8.800000] UBI warning: print_rsvd_warning: ca
> nnot reserve enough PEBs for bad PEB handling, res
> erved 8, need 9
> [    8.830000] UBI: number of bad PEBs:         1
> [    8.870000] UBI: number of PEBs reserved for ba
> d PEB handling: 8
> 
> root@PogoPlug:~# /usr/sbin/flash_erase /dev/mtd0 0
> x0 6
> Erasing 128 Kibyte @ 20000 -- 16 % complete libmtd
> : error!: bad eraseblock number 2, mtd0 has 2 eras
> eblocks
> flash_erase: error!: /dev/mtd0: MTD get bad block
> failed
> error 22 (Invalid argument)
> root@PogoPlug:~# /usr/sbin/nandwrite /dev/mtd0 mtd
> 0
> Writing data to block 0 at offset 0x0
> Writing data to block 1 at offset 0x20000
>

> The box is still work, Can I flash this u-boot?


Are you flashing it in stock OS? the mtd parts definition is wrong. So no, you should not flash it.

Please post output of dmesg.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

dmesg

root@PogoPlug:~# dmesg
[    0.000000] Initializing cgroup subsys cpuset
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.1.10 (xbmc@xbmc-MCP7A) (gcc version 4.6.3 20120201 (prerelease) (Linaro GCC 4.6-2012.02) ) #11 SMP Wed Sep 25 19:11:24 CST 2013
[    0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5387d
[    0.000000] CPU: VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: PogoPlug Pro
[    0.000000] 1 memory region
[    0.000000] Ignoring unrecognised tag 0x00000000
[    0.000000] Memory policy: ECC disabled, Data cache writealloc
[    0.000000] On node 0 totalpages: 32768
[    0.000000] free_area_init_node: node 0, pgdat c034fee0, node_mem_map c03b5000
[    0.000000]   Normal zone: 256 pages used for memmap
[    0.000000]   Normal zone: 0 pages reserved
[    0.000000]   Normal zone: 32512 pages, LIFO batch:7
[    0.000000] PERCPU: Embedded 7 pages/cpu @c04b8000 s4768 r8192 d15712 u32768
[    0.000000] pcpu-alloc: s4768 r8192 d15712 u32768 alloc=8*4096
[    0.000000] pcpu-alloc: [0] 0 [0] 1 
[    0.000000] Built 1 zonelists in Zone order, mobility grouping on.  Total pages: 32512
[    0.000000] Kernel command line: root=ubi0:rootfs ubi.mtd=6,512 rootfstype=ubifs rootwait console=ttyS0,115200 mac_adr=0x00,0x30,0xe0,0x00,0x00,0x01 mem=128M poweroutage=yes
[    0.000000] PID hash table entries: 512 (order: -1, 2048 bytes)
[    0.000000] Dentry cache hash table entries: 16384 (order: 4, 65536 bytes)
[    0.000000] Inode-cache hash table entries: 8192 (order: 3, 32768 bytes)
[    0.000000] allocated 524288 bytes of page_cgroup
[    0.000000] please try 'cgroup_disable=memory' option if you don't want memory cgroups
[    0.000000] Memory: 128MB = 128MB total
[    0.000000] Memory: 125548k/125548k available, 5524k reserved, 0K highmem
[    0.000000] Virtual kernel memory layout:
[    0.000000]     vector  : 0xffff0000 - 0xffff1000   (   4 kB)
[    0.000000]     fixmap  : 0xfff00000 - 0xfffe0000   ( 896 kB)
[    0.000000]     DMA     : 0xffc00000 - 0xffe00000   (   2 MB)
[    0.000000]     vmalloc : 0xc8800000 - 0xed000000   ( 584 MB)
[    0.000000]     lowmem  : 0xc0000000 - 0xc8000000   ( 128 MB)
[    0.000000]     modules : 0xbf000000 - 0xc0000000   (  16 MB)
[    0.000000]       .text : 0xc0008000 - 0xc030b000   (3084 kB)
[    0.000000]       .init : 0xc030b000 - 0xc03352a0   ( 169 kB)
[    0.000000]       .data : 0xc0336000 - 0xc0351700   ( 110 kB)
[    0.000000]        .bss : 0xc0351724 - 0xc03b42dc   ( 395 kB)
[    0.000000] SLUB: Genslabs=13, HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[    0.000000] Hierarchical RCU implementation.
[    0.000000] NR_IRQS:146 nr_irqs:146 146
[    0.000000] OX820_RPS_init_irq: interrupts 64 to 96
[    0.000000] console [ttyS0] enabled
[    0.030000] Calibrating delay loop... 278.93 BogoMIPS (lpj=1394688)
[    0.100000] pid_max: default: 32768 minimum: 301
[    0.100000] Mount-cache hash table entries: 512
[    0.110000] Initializing cgroup subsys cpuacct
[    0.110000] Initializing cgroup subsys memory
[    0.120000] Initializing cgroup subsys devices
[    0.120000] Initializing cgroup subsys freezer
[    0.130000] CPU: Testing write buffer coherency: ok
[    0.130000] Calibrating local timer... 349.84MHz.
[    0.190000] platform_smp_prepare_cpus 33
[    0.190000] CPU1: Booted secondary processor
[    0.190000] CPU1:Got wake up!
[    0.270000] Brought up 2 CPUs
[    0.270000] SMP: Total of 2 processors activated (557.87 BogoMIPS).
[    0.280000] devtmpfs: initialized
[    0.280000] NET: Registered protocol family 16
[    0.790000] PCIeA version/deviceID 082510b5
[    0.790000] PCIeB version/deviceID 082510b5
[    3.810000] ox820_pci_preinit() PCIEA link up timeout (00001014)
[    6.820000] ox820_pci_preinit() PCIEB link up timeout (00001014)
[    6.820000] ox820_pcie_setup_resources() Enabling PCIe Pre-Emphasis
[    6.830000] ox820_pciea_setup_resources() resource c781bc60
[    6.830000] ox820_pciea_setup_resources()    io:      0x4be00000 - 0x4befffff
[    6.840000] ox820_pciea_setup_resources()    non-pre: 0x48000000 - 0x49ffffff
[    6.850000] ox820_pciea_setup_resources()    pre:     0x4a000000 - 0x4bdfffff
[    6.850000] PCI: bus0: Fast back to back transfers enabled
[    6.860000] PCI: bus1: Fast back to back transfers enabled
[    6.890000] bio: create slab <bio-0> at 0
[    6.890000] SCSI subsystem initialized
[    6.900000] libata version 3.00 loaded.
[    6.900000] Switching to clocksource rps-timer2
[    6.910000] NET: Registered protocol family 2
[    6.910000] IP route cache hash table entries: 1024 (order: 0, 4096 bytes)
[    6.920000] TCP established hash table entries: 4096 (order: 3, 32768 bytes)
[    6.930000] TCP bind hash table entries: 4096 (order: 3, 32768 bytes)
[    6.940000] TCP: Hash tables configured (established 4096 bind 4096)
[    6.940000] TCP reno registered
[    6.950000] UDP hash table entries: 128 (order: 0, 4096 bytes)
[    6.950000] UDP-Lite hash table entries: 128 (order: 0, 4096 bytes)
[    6.960000] NET: Registered protocol family 1
[    6.960000] PCI: CLS 0 bytes, default 32
[    6.990000] squashfs: version 4.0 (2009/01/31) Phillip Lougher
[    7.000000] JFFS2 version 2.2 (NAND) (SUMMARY) (LZMA) (RTIME) (CMODE_PRIORITY) (c) 2001-2006 Red Hat, Inc.
[    7.010000] msgmni has been set to 245
[    7.010000] io scheduler noop registered
[    7.020000] io scheduler deadline registered (default)
[    7.020000] io scheduler cfq registered
[    7.030000] ox820_gpio: initialized
[    7.030000] Serial: 8250/16550 driver, 32 ports, IRQ sharing enabled
[    7.050000] serial8250: ttyS0 at MMIO 0x44200000 (irq = 55) is a 16550A
[    8.040000] brd: module loaded
[    8.050000] loop: module loaded
[    8.050000] ox820sata: OX820 sata core.
[    8.060000] scsi0 : oxnassata
[    8.070000] scsi1 : oxnassata
[    8.070000] ata1: SATA max UDMA/133 irq 50
[    8.070000] ata2: SATA max UDMA/133 irq 50
[    8.080000] sata_ox820: Initialized
[    8.080000] ONFI flash detected
[    8.090000] NAND device: Manufacturer ID: 0xad, Chip ID: 0xf1 (Hynix NAND 128MiB 3,3V 8-bit)
[    8.100000] Scanning device for bad blocks
[    8.230000] Bad eraseblock 928 at 0x000007400000
[    8.250000] Creating 9 MTD partitions on "NAND 128MiB 3,3V 8-bit":
[    8.260000] 0x000000000000-0x000000040000 : "stage1"
[    8.260000] 0x000000040000-0x0000001a0000 : "u-boot"
[    8.270000] 0x0000001a0000-0x0000001e0000 : "u-boot-env"
[    8.280000] 0x000000000000-0x000002000000 : "boot"
[    8.290000] 0x0000001e0000-0x000000200000 : "factory"
[    8.300000] 0x000000200000-0x000000c00000 : "kernel"
[    8.300000] 0x000000e00000-0x000008000000 : "rootfs"
[    8.310000] split_squashfs: no squashfs found in "NAND 128MiB 3,3V 8-bit"
[    8.320000] 0x000000200000-0x000008000000 : "firmware"
[    8.330000] 0x000000000000-0x000008000000 : "fullflash"
[    8.330000] UBI: attaching mtd6 to ubi0
[    8.340000] UBI: physical eraseblock size:   131072 bytes (128 KiB)
[    8.350000] UBI: logical eraseblock size:    129024 bytes
[    8.350000] UBI: smallest flash I/O unit:    2048
[    8.360000] UBI: sub-page size:              512
[    8.360000] UBI: VID header offset:          512 (aligned 512)
[    8.370000] UBI: data offset:                2048
[    8.770000] UBI: max. sequence number:       393
[    8.800000] UBI warning: print_rsvd_warning: cannot reserve enough PEBs for bad PEB handling, reserved 8, need 9
[    8.810000] UBI: attached mtd6 to ubi0
[    8.810000] UBI: MTD device name:            "rootfs"
[    8.820000] UBI: MTD device size:            114 MiB
[    8.820000] UBI: number of good PEBs:        911
[    8.830000] UBI: number of bad PEBs:         1
[    8.830000] UBI: number of corrupted PEBs:   0
[    8.840000] UBI: max. allowed volumes:       128
[    8.840000] UBI: wear-leveling threshold:    4096
[    8.850000] UBI: number of internal volumes: 1
[    8.850000] UBI: number of user volumes:     1
[    8.850000] UBI: available PEBs:             0
[    8.860000] UBI: total number of reserved PEBs: 911
[    8.860000] UBI: number of PEBs reserved for bad PEB handling: 8
[    8.870000] UBI: max/mean erase counter: 2/0
[    8.870000] UBI: image sequence number:  1970227278
[    8.880000] UBI: background thread "ubi_bgt0d" started, PID 357
[    8.890000] Probing for Synopsis GMAC, unit 0
[    8.890000] eth0: Tuning GMAC 0 RGMII timings
[    8.890000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[    8.900000] eth0: Disable EEE (Energy Efficient Ethernet 802.3az)
[    8.910000] eth0: GMAC ver = 53, vendor ver = 18 at 0xed400000, IRQ 40
[    8.920000] eth0: Found PHY at address 3, type 0x001cc914 -> 10/100/1000
[    8.920000] eth0: Ethernet addr: 00:30:e0:00:00:00
[    8.930000] Registered led device: status:misc:blue
[    8.930000] Registered led device: status:health:green
[    8.930000] Registered led device: status:fault:orange
[    8.930000] ox820_led_gpio: initialized
[    8.940000] TCP cubic registered
[    8.940000] NET: Registered protocol family 17
[    8.940000] 8021q: 802.1Q VLAN Support v1.8
[    8.950000] VFP support v0.3: not present
[    9.020000] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
[    9.020000] ata1.00: ATA-8: HGST HTS721010A9E630, JB0OA3U0, max UDMA/133
[    9.030000] ata1.00: 1953525168 sectors, multi 16: LBA48 NCQ (depth 0/32)
[    9.040000] ata1.00: configured for UDMA/133
[    9.040000] scsi 0:0:0:0: Direct-Access     ATA      HGST HTS721010A9 JB0O PQ: 0 ANSI: 5
[    9.400000] ata2: SATA link down (SStatus 0 SControl 300)
[    9.530000] UBIFS: recovery needed
[    9.680000] UBIFS: recovery completed
[    9.680000] UBIFS: mounted UBI device 0, volume 0, name "rootfs"
[    9.690000] UBIFS: file system size:   114573312 bytes (111888 KiB, 109 MiB, 888 LEBs)
[    9.700000] UBIFS: journal size:       9033728 bytes (8822 KiB, 8 MiB, 71 LEBs)
[    9.700000] UBIFS: media format:       w4/r0 (latest is w4/r0)
[    9.710000] UBIFS: default compressor: lzo
[    9.710000] UBIFS: reserved for root:  0 bytes (0 KiB)
[    9.720000] VFS: Mounted root (ubifs filesystem) on device 0:12.
[    9.730000] devtmpfs: mounted
[    9.730000] Freeing init memory: 168K
[   14.640000] Loading modules backported from Linux version master-2013-06-27-0-gdcfa6d5
[   14.650000] Backport generated by backports.git backports-20130617-4-ge3220f5
[   14.790000] cfg80211: Calling CRDA to update world regulatory domain
[   14.800000] cfg80211: World regulatory domain updated:
[   14.800000] cfg80211:   (start_freq - end_freq @ bandwidth), (max_antenna_gain, max_eirp)
[   14.810000] cfg80211:   (2402000 KHz - 2472000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   14.820000] cfg80211:   (2457000 KHz - 2482000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   14.830000] cfg80211:   (2474000 KHz - 2494000 KHz @ 20000 KHz), (300 mBi, 2000 mBm)
[   14.830000] cfg80211:   (5170000 KHz - 5250000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   14.840000] cfg80211:   (5735000 KHz - 5835000 KHz @ 40000 KHz), (300 mBi, 2000 mBm)
[   15.000000] usbcore: registered new interface driver usbfs
[   15.010000] usbcore: registered new interface driver hub
[   15.020000] usbcore: registered new device driver usb
[   15.830000] usbcore: registered new interface driver rt73usb
[   15.920000] usbcore: registered new interface driver rtl8187
[   16.060000] usbcore: registered new interface driver rt2800usb
[   16.380000] NTFS driver 2.1.30 [Flags: R/O MODULE].
[   16.720000] SGI XFS with security attributes, large block/inode numbers, no debug enabled
[   16.810000] PPP generic driver version 2.4.2
[   17.140000] usbcore: registered new interface driver p54usb
[   17.200000] ip_tables: (C) 2000-2006 Netfilter Core Team
[   17.360000] NET: Registered protocol family 24
[   17.400000] sd 0:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/931 GiB)
[   17.410000] sd 0:0:0:0: [sda] 4096-byte physical blocks
[   17.420000] sd 0:0:0:0: [sda] Write Protect is off
[   17.420000] sd 0:0:0:0: [sda] Mode Sense: 00 3a 00 00
[   17.420000] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[   17.710000]  sda: unknown partition table
[   17.720000] sd 0:0:0:0: [sda] Attached SCSI disk
[   17.760000] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[   17.760000] Initializing Oxnas-SoC USB Host Controller
[   17.770000] oxnas-ehci oxnas-ehci.0: OXNAS EHCI
[   17.770000] oxnas-ehci oxnas-ehci.0: new USB bus registered, assigned bus number 1
[   17.810000] oxnas-ehci oxnas-ehci.0: irq 39, io mem 0x40200100
[   17.830000] oxnas-ehci oxnas-ehci.0: USB 2.0 started, EHCI 1.00
[   17.830000] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[   17.840000] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[   17.850000] usb usb1: Product: OXNAS EHCI
[   17.850000] usb usb1: Manufacturer: Linux 3.1.10 ehci_hcd
[   17.850000] usb usb1: SerialNumber: oxnas-ehci.0
[   17.860000] hub 1-0:1.0: USB hub found
[   17.860000] hub 1-0:1.0: 2 ports detected
[   17.920000] nf_conntrack version 0.5.0 (1964 buckets, 7856 max)
[   18.190000] usb 1-1: new high speed USB device number 2 using oxnas-ehci
[   18.230000] ohci_hcd: USB 1.1 'Open' Host Controller (OHCI) Driver
[   18.280000] i2c /dev entries driver
[   18.340000] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[   18.350000] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[   18.350000] usb 1-1: Product: USB2.0 Hub
[   18.360000] hub 1-1:1.0: USB hub found
[   18.360000] usbcore: registered new interface driver ath9k_htc
[   18.370000] hub 1-1:1.0: 4 ports detected
[   18.380000] usbcore: registered new interface driver usblp
[   18.440000] Initializing USB Mass Storage driver...
[   18.450000] usbcore: registered new interface driver usb-storage
[   18.450000] USB Mass Storage support registered.
[   18.520000] Linux video capture interface: v2.00
[   18.630000] gspca: v2.13.0 registered
[   18.670000] usbcore: registered new interface driver zc3xx
[   18.730000] fuse init (API version 7.17)
[   18.790000] usbcore: registered new interface driver uvcvideo
[   18.800000] USB Video Class driver (1.1.1)
[   21.680000] Offload is not active on eth0
[   21.680000] Alloc'ing ARM descs 10240 bytes
[   21.690000] eth0: Resetting GMAC
[   21.690000] eth0: GMAC reset complete
[   21.700000] eth0: Setting Rx flow control thresholds for LAN port
[   22.210000] eth0: PHY is Realtek RTL8211D, type 0x001cc914
[   22.210000] eth0: Disable EEE (Energy Efficient Ethernet 802.3az)
[   22.720000] eth0: link down
[   24.720000] eth0: link up, 100Mbps, full-duplex, using pause, lpa 0x45E1
[   24.720000] device eth0 entered promiscuous mode
[   24.730000] br-lan: port 1(eth0) entering forwarding state
[   24.740000] br-lan: port 1(eth0) entering forwarding state
[   26.740000] br-lan: port 1(eth0) entering forwarding state
[ 2079.380000] EXT4-fs (sda): mounted filesystem with ordered data mode. Opts: (null)

Now it's running OpenWRT

ming Wrote:
-------------------------------------------------------
> Now it's running OpenWRT
>
You should try LEDE for a better performance. OpenWRT is optimized as a router, AFAICT.

bodhi Wrote:
-------------------------------------------------------
> ming Wrote:
> --------------------------------------------------
> -----
> > cat /proc/mtd
> >

> > root@PogoPlug:~# cat /proc/mtd
> > dev:    size   erasesize  name
> > mtd0: 00040000 00020000 "stage1"
> > mtd1: 00160000 00020000 "u-boot"
> > mtd2: 00040000 00020000 "u-boot-env"
> > mtd3: 02000000 00020000 "boot"
> > mtd4: 00020000 00020000 "factory"
> > mtd5: 00a00000 00020000 "kernel"
> > mtd6: 07200000 00020000 "rootfs"
> > mtd7: 07e00000 00020000 "firmware"
> > mtd8: 08000000 00020000 "fullflash"
> >

> > cat /etc/fw_env.config
> >

> > # MTD device name	Device offset	Env. size	Flash
> se
> > ctor size	Number of sectors
> > /dev/mtd2       0x0        0x2000      0x40000
> >

> >

> > root@PogoPlug:~# dmesg | grep -i 'bad'
> > [    8.100000] Scanning device for bad blocks
> > [    8.230000] Bad eraseblock 928 at 0x000007400
> 00
> > 0
> > [    8.800000] UBI warning: print_rsvd_warning:
> ca
> > nnot reserve enough PEBs for bad PEB handling, r
> es
> > erved 8, need 9
> > [    8.830000] UBI: number of bad PEBs:
> 1
> > [    8.870000] UBI: number of PEBs reserved for
> ba
> > d PEB handling: 8
> >
> > root@PogoPlug:~# /usr/sbin/flash_erase /dev/mtd0
> 0
> > x0 6
> > Erasing 128 Kibyte @ 20000 -- 16 % complete libm
> td
> > : error!: bad eraseblock number 2, mtd0 has 2 er
> as
> > eblocks
> > flash_erase: error!: /dev/mtd0: MTD get bad bloc
> k
> > failed
> > error 22 (Invalid argument)
> > root@PogoPlug:~# /usr/sbin/nandwrite /dev/mtd0 m
> td
> > 0
> > Writing data to block 0 at offset 0x0
> > Writing data to block 1 at offset 0x20000
> >

> > The box is still work, Can I flash this u-boot?
>
>
> Are you flashing it in stock OS? the mtd parts def
> inition is wrong. So no, you should not flash it.
>
> Please post output of dmesg.


all reboot TTL output

ming,

You're running an entirely different version of u-boot and kernel for this box. So I would recommend to flash u-boot only if you intend to run the new rootfs from here:
http://forum.doozan.com/read.php?2,16044

And your mtd definitions are very different from what we use here

Your current system:

root@PogoPlug:~# cat /proc/mtd 
dev:    size   erasesize  name
mtd0: 00040000 00020000 "stage1"
mtd1: 00160000 00020000 "u-boot"
mtd2: 00040000 00020000 "u-boot-env"
mtd3: 02000000 00020000 "boot"
mtd4: 00020000 00020000 "factory"
mtd5: 00a00000 00020000 "kernel"
mtd6: 07200000 00020000 "rootfs"
mtd7: 07e00000 00020000 "firmware"
mtd8: 08000000 00020000 "fullflash"

My u-boot mtdparts:

root@PogoPro:~# cat /proc/mtd
dev:    size   erasesize  name
mtd0: 00e00000 00020000 "boot"
mtd1: 07200000 00020000 "data"

In order to flash new u-boot you also need to redefine it in u-boot first, and use that in the kernel bootargs to pass it in

setenv mtparts 'mtdparts=41000000.nand:14m(boot),-(data)'

However, your u-boot envs are really not set to boot a USB rootfs. So it would need more adjustments than just this mtdparts.

---

So the bottom line is: yes, it is possible to install new u-boot and create new USB rootds to boot with it. If you don't intend to run USB or HDD rootfs, then do not flash this new u-boot.

And you need to do it slowly step by step:

- set up to boot USB rootfs first,
- adjust mtdparts to be same as above
- boot this USB rootfs successfully
- verify that the mtds definition are correct.
- flash new u-boot and its default envs images.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)



Edited 3 time(s). Last edit at 04/21/2017 08:07PM by bodhi.

I read this: http://forum.doozan.com/read.php?2,16044 ,to make a USB rootfs.but i do not understand

set_bootargs_usb=setenv bootargs console=$console root=$usb_root rootdelay=$rootdelay rootfstype=$rootfstype $mtdparts
rootfstype=ext2

I format the U disk using the 'mkfs.ext3 ' command. and extract

tar -xjf Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2

then i get

[root@alarm sdb1]# mv /home/alarm/Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
[root@alarm sdb1]# ls
Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
[root@alarm sdb1]# ls /home/alarm/
kcptnu	kcptnu2  sqlite  ssr
[root@alarm sdb1]# tar -xjf Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 
[root@alarm sdb1]# ls
Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2	bin  boot  dev	etc  home  lib	lost+found  media  mnt	opt  proc  root  run  sbin  selinux  srv  sys  tmp  usr  var
[root@alarm sdb1]# ls -l
total 84872
-rw-r--r--  1 alarm alarm 86736625 Apr 22 06:16 Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
drwxr-xr-x  2 root  root      4096 Nov  1  2014 bin
drwxr-xr-x  3 root  root      4096 Nov  1  2014 boot
drwxr-xr-x  5 root  root      4096 Feb 24  2012 dev
drwxr-xr-x 51 root  root      4096 Jan  1  1970 etc
drwxr-xr-x  2 root  root      4096 Jan 22  2012 home
drwxr-xr-x 11 root  root      4096 May  9  2014 lib
drwx------  2 root  root      4096 Feb 24  2012 lost+found
drwxr-xr-x  2 root  root      4096 Feb 24  2012 media
drwxr-xr-x  2 root  root      4096 Jan 22  2012 mnt
drwxr-xr-x  2 root  root      4096 Feb 24  2012 opt
drwxr-xr-x  2 root  root      4096 Jan 22  2012 proc
drwx------  4 root  root      4096 Nov  1  2014 root
drwxr-xr-x  2 root  root      4096 Feb  8  2013 run
drwxr-xr-x  2 root  root      4096 May  9  2014 sbin
drwxr-xr-x  2 root  root      4096 Jul 21  2010 selinux
drwxr-xr-x  2 root  root      4096 Feb 24  2012 srv
drwxr-xr-x  2 root  root      4096 Jan  1  2011 sys
drwxrwxrwt  2 root  root      4096 Jan  1  1970 tmp
drwxr-xr-x 10 root  root      4096 Feb 24  2012 usr
drwxr-xr-x 11 root  root      4096 Jan  1  1970 var
[root@alarm sdb1]# rm -rf Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2

Edited 2 time(s). Last edit at 04/22/2017 01:44AM by ming.

ming,

> I read this: http://forum.doozan.com/read.php?2,16
> 044 ,to make a USB rootfs.but i do not understand

All of what you did below was correct. But there is 1 missing step. And 1 step is not needed.

> set_bootargs_usb=setenv bootargs console=$console
> root=$usb_root rootdelay=$rootdelay rootfstype=$ro
> otfstype $mtdparts
> rootfstype=ext2

The setenv above is not needed if you run with new uboot.


> I format the U disk using the 'mkfs.ext3 ' command
> . and extract

> tar -xjf Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.ta
> r.bz2

> then i get

> [root@alarm sdb1]# mv /home/alarm/Debian-3.17.0-ox
> nas-tld-1-rootfs-bodhi.tar.bz2 Debian-3.17.0-oxnas
> -tld-1-rootfs-bodhi.tar.bz2
> [root@alarm sdb1]# ls
> Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
> [root@alarm sdb1]# ls /home/alarm/
> kcptnu kcptnu2 sqlite ssr
> [root@alarm sdb1]# tar -xjf Debian-3.17.0-oxnas-tl
> d-1-rootfs-bodhi.tar.bz2
> [root@alarm sdb1]# ls
> Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 bin
> boot dev etc home lib lost+found media mnt op
> t proc root run sbin selinux srv sys tmp
> usr var
> [root@alarm sdb1]# ls -l
> total 84872
> -rw-r--r-- 1 alarm alarm 86736625 Apr 22 06:16 De
> bian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
> drwxr-xr-x 2 root root 4096 Nov 1 2014 bi
> n
> drwxr-xr-x 3 root root 4096 Nov 1 2014 bo
> ot
> drwxr-xr-x 5 root root 4096 Feb 24 2012 de
> v
> drwxr-xr-x 51 root root 4096 Jan 1 1970 et
> c
> drwxr-xr-x 2 root root 4096 Jan 22 2012 ho
> me
> drwxr-xr-x 11 root root 4096 May 9 2014 li
> b
> drwx------ 2 root root 4096 Feb 24 2012 lo
> st+found
> drwxr-xr-x 2 root root 4096 Feb 24 2012 me
> dia
> drwxr-xr-x 2 root root 4096 Jan 22 2012 mn
> t
> drwxr-xr-x 2 root root 4096 Feb 24 2012 op
> t
> drwxr-xr-x 2 root root 4096 Jan 22 2012 pr
> oc
> drwx------ 4 root root 4096 Nov 1 2014 ro
> ot
> drwxr-xr-x 2 root root 4096 Feb 8 2013 ru
> n
> drwxr-xr-x 2 root root 4096 May 9 2014 sb
> in
> drwxr-xr-x 2 root root 4096 Jul 21 2010 seo
> linux
> drwxr-xr-x 2 root root 4096 Feb 24 2012 sr
> v
> drwxr-xr-x 2 root root 4096 Jan 1 2011 sy
> s
> drwxrwxrwt 2 root root 4096 Jan 1 1970 tm
> p
> drwxr-xr-x 10 root root 4096 Feb 24 2012 us
> r
> drwxr-xr-x 11 root root 4096 Jan 1 1970 va
> r
> [root@alarm sdb1]# rm -rf Debian-3.17.0-oxnas-tld-
> 1-rootfs-bodhi.tar.bz2

Right here, you need to label the partition

tune2fs -L rootfs /dev/sdb1

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

ming Wrote:
-------------------------------------------------------
> Now it's running OpenWRT
>
I assume you device boots off OpenWRT from the internal storage, right?

ming,

hahibie has a good point, if the uboot envs are currently set up to boot Openwrt, you need to modify them to boot USB. Please post the current uboot envs if you have installed new uboot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

habibie Wrote:
-------------------------------------------------------
> ming Wrote:
> --------------------------------------------------
> -----
> > Now it's running OpenWRT
> >
> I assume you device boots off OpenWRT from the int
> ernal storage, right?


Yes.My English is not very good.Has been using google translation

I moved this to a different tpoic:

http://forum.doozan.com/read.php?3,33930

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello,

I want to use your builds of U-Boot to boot Iomega Home Media Network Hard Drive Cloud Edition, but that device does not have flash (ie. mtd0), it boots directly from HDD. Stock U-Boot is written directly in first 32MB (raw, ie using 'dd'), stock filesystem config, including first 32MB of RAW data is here: http://iomega.nas-central.org/wiki/Stock_Configuration_(Home_Media_CE)#Partitioning_.26_File_Systems
Can you give me some tips to make it work ? Do I need to fork your U-Boot or it's a simpler way to make it work ?

Thanks !

Nucleorptoein,

It is best that you start with shv SATA boot setup:
http://forum.doozan.com/read.php?3,16017,17297#msg-17297

And then we'll go from there.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Hello again,

Can you send me .config file for your latest U-Boot mtd0 version ie. ?
I'm currently rebuilding U-Boot, I think I will update it to 2017 branch but first I need to build a working one.

Do you know how to change RAM size ? My device have 256MB and U-Boot detects only 128MB.

Thanks

Please see developer section in Wki thread:
http://forum.doozan.com/read.php?2,23630

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I given up on new u-boot SPL and used stock U-Boot 'go' command to chainload your latest u-boot.bin which I build with SATA & EXT4 support and it works fine with your linux-4.4.54-oxnas-tld-1 and stg-212 fdt. I will share my findings here but I need to write nice guide :p

Thanks

Nucleoprotein,

> chainload your latest u-boot.bin w
> hich I build with SATA & EXT4 support and it works
> fine with your linux-4.4.54-oxnas-tld-1 and stg-21
> 2 fdt. I will share my findings here but I need to
> write nice guide :p

Cool :) That would be really helpful to a lot of users. Please create a new OX820 u-boot thread for your guide so I can add it to the Wiki thread.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

hi, bodhi

I try to rebuild uboot with your code on Pogo V3. I find there is an error when make target 'checkarmreloc'

make obj=spl -f ./scripts/Makefile.spl all
make[1]: *** No rule to make target `checkarmreloc', needed by `all'.  Stop.
make: *** [spl/u-boot-spl] Error 2

Have you met this error before?

I find there is a u-boot.bin already. I compare this bin with yours. There is 64 bytes header in your uboot(uboot.2015.10-tld-1.ox820.mtd0.img). And my u-boot.bin is smaller than yours.
Should I add this 64 bytes header to my bin if I want to use your spl?

My build command is

make CROSS_COMPILE=arm-openwrt-linux- ox820_defconfig
make CROSS_COMPILE=arm-openwrt-linux-

Use u-boot.img as target for make in 2015 branch to build main image ie.

make CROSS_COMPILE=arm-uknown-linux- u-boot.img

You need to use different branch from github to build SPL.

lpwsxy,

Please make a new uboot thread for this.

>
> I try to rebuild uboot with your code on Pogo V3.
> I find there is an error when make target 'checkar
> mreloc'
>

> make obj=spl -f ./scripts/Makefile.spl all
> make[1]: *** No rule to make target `checkarmreloc
> ', needed by `all'.  Stop.
> make: *** [spl/u-boot-spl] Error 2
>

> Have you met this error before?
>
> I find there is a u-boot.bin already. I compare th
> is bin with yours. There is 64 bytes header in you
> r uboot(uboot.2015.10-tld-1.ox820.mtd0.img). And m
> y u-boot.bin is smaller than yours.
> Should I add this 64 bytes header to my bin if I w
> ant to use your spl?
>
> My build command is
>

> make CROSS_COMPILE=arm-openwrt-linux- ox820_defcon
> fig
> make CROSS_COMPILE=arm-openwrt-linux-
>

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

uboot.2015.10-tld-2 u-Boot image for Pogoplug V3 Oxnas has been uploaded. Please see 1st post for download link.

Quote

Updated in this u-boot version:

- Fixed preboot missing in previous version. As a result, netconsole is now starting automatically if set up.
- A more robust new default envs image.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Last post moved here:
https://forum.doozan.com/read.php?3,41109

It's always good to create a new thread for question. This thread is a release thread, and for questions pertaining to the released u-boot.

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Do I can use this u-boot with Akitio Mycloud Duo?

Last post moved here:

https://forum.doozan.com/read.php?3,47919

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

Last post moved here:

https://forum.doozan.com/read.php?3,49629

-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)

I was trying to upgrade from uboot-tld-1 to uboot-tld-2 but i see this

root@debian:~/installers/uboot-2# /usr/sbin/flash_erase /dev/mtd0 0x0 6
Erasing 128 Kibyte @ 48cf5c00000064 --  6 % complete

Everything else looks ok to me

root@debian:~/installers/uboot-2# more /etc/fw_env.config 
# pogoplug v3
  /dev/mtd0               0x00100000      0x20000         0x20000

root@debian:~/installers/uboot-2# more /proc/mtd 
dev:    size   erasesize  name
mtd0: 00e00000 00020000 "boot"
mtd1: 07200000 00020000 "data"

I still have the system up and running.
Any clues to what i could be doing wrong?

----
mod edit: please use code tags.



Edited 1 time(s). Last edit at 02/23/2018 03:50PM by bodhi.