|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 11, 2015 02:29AM |
Registered: 10 years ago Posts: 64 |
Dear Bodhi, Shv, Morph027
Sata uboot oxnas and me is a non working love affair. I tried very much, but failed... :)
In this stage I have command prompt, able to modify env variable.
Is there any way to boot via usb or tftp? Is it possible theoretically?
There is two option:
I have tftp server on my server side.
I have working usb pen drive too. (It works before I screw up boot.)
Sata uboot oxnas and me is a non working love affair. I tried very much, but failed... :)
In this stage I have command prompt, able to modify env variable.
Is there any way to boot via usb or tftp? Is it possible theoretically?
There is two option:
I have tftp server on my server side.
I have working usb pen drive too. (It works before I screw up boot.)
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 11, 2015 07:16AM |
Admin Registered: 13 years ago Posts: 18,997 |
@robert,
You have unbricked it! You can reflash u-boot in serial console now :)
Yes. Since you have booted into u-boot console with SATA u-boot. However, there is no need to do this. If you like, just reflash NAND u-boot/SPL. Then your pboblem is solved.
To continue with SATA booting:
You've booted SATA far into to the point where the kernel is loaded. So now the problem is to make it boot successfully. I would try different kernel and/ rootfs (unless shv has some idea why the current one does not).
So try switching the uImage and uInitrd to to one from 3.16.0-oxnas-tld-1. Which rootfs are you using?
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 02/11/2015 07:28AM by bodhi.
You have unbricked it! You can reflash u-boot in serial console now :)
Quote
> Is there any way to boot via usb or tftp? Is it
> possible theoretically?
Yes. Since you have booted into u-boot console with SATA u-boot. However, there is no need to do this. If you like, just reflash NAND u-boot/SPL. Then your pboblem is solved.
To continue with SATA booting:
You've booted SATA far into to the point where the kernel is loaded. So now the problem is to make it boot successfully. I would try different kernel and/ rootfs (unless shv has some idea why the current one does not).
So try switching the uImage and uInitrd to to one from 3.16.0-oxnas-tld-1. Which rootfs are you using?
Quote
ls -la /media/b/rootfs/boot/ -----------This is the HDD mounted on PC
összesen 12316
drwxr-xr-x 3 root root 4096 febr 10 19:36 .
drwxr-xr-x 22 root root 4096 febr 10 15:22 ..
drwxr-xr-x 2 root root 4096 aug 3 2014 dts
-rw-r--r-- 1 root root 7033 máj 11 2014 ox820-pogoplug-pro.dtb
-rwxr-xr-x 1 root root 16384 jan 1 1970 u-boot.env
-rw-r--r-- 1 root root 525880 aug 3 2014 u-boot.img
-rwxr-xr-x 1 root root 32120 aug 3 2014 u-boot-spl.bin
-rw-r--r-- 1 root root 3676848 aug 3 2014 uImage
-rw-r--r-- 1 root root 2212156 aug 3 2014 uImage_2.6.31.14_OX820_1.2_shv.Pro
-rw-r--r-- 1 root root 2103272 aug 3 2014 uInitrd
-rwxr-xr-x 1 root root 4010416 aug 23 03:22 zImage-3.16.0-oxnas-tld-1
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 2 time(s). Last edit at 02/11/2015 07:28AM by bodhi.
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 11, 2015 10:25AM |
Registered: 10 years ago Posts: 64 |
Hi Bodhi,
Thank you so much!
>If you like, just reflash NAND u-boot/SPL. Then your pboblem is solved.
But how can I reflash NAND if I only have prompt but not a linux console? I dont have nandwrite or erase command.
I have this command line 2 days ago, but you didnt mention it is enough.
I thought I need any kernel loaded and normal linux load and then will be available the nand flash.
> Which rootfs are you using?
I exactly follow the instructions, tried both the latest Archlinux and also tried with Your 3.17 Debian. But none of them works.
>So try switching the uImage and uInitrd to to one from 3.16.0-oxnas-tld-1.
How?
But never mind I had another solution :)
A few hours ago I was able to tftpboot from commandline (based on your note: TFTP boot
And now I have booted debian.
I will now try reflash Uboot and forget this nighmare of no right SATA UBOOT.
But this works.:
1. Sata uboot.
2. Stopped at counter. (or else kernel loading freezed!!)
3. tftpboot from your uboot.2013.10-tld-2.ox820.bin
4. USB pendrive attached with 3.17 debian.
5. login to debian.
Without TFTP boot and USB debian rootfs on pendrive, all previous kernel loading freezed!
Thank you very much Bodhi for efforts to help!
:))
Robert
Thank you so much!
>If you like, just reflash NAND u-boot/SPL. Then your pboblem is solved.
But how can I reflash NAND if I only have prompt but not a linux console? I dont have nandwrite or erase command.
I have this command line 2 days ago, but you didnt mention it is enough.
I thought I need any kernel loaded and normal linux load and then will be available the nand flash.
> Which rootfs are you using?
I exactly follow the instructions, tried both the latest Archlinux and also tried with Your 3.17 Debian. But none of them works.
>So try switching the uImage and uInitrd to to one from 3.16.0-oxnas-tld-1.
How?
But never mind I had another solution :)
A few hours ago I was able to tftpboot from commandline (based on your note: TFTP boot
And now I have booted debian.
I will now try reflash Uboot and forget this nighmare of no right SATA UBOOT.
But this works.:
1. Sata uboot.
2. Stopped at counter. (or else kernel loading freezed!!)
3. tftpboot from your uboot.2013.10-tld-2.ox820.bin
4. USB pendrive attached with 3.17 debian.
5. login to debian.
Without TFTP boot and USB debian rootfs on pendrive, all previous kernel loading freezed!
U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - 14:31:34)
Boot device: SATA
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1
PLLA Set
Bus 0: OK
Device 0:
** File not found /boot/bootargs.bin **
U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - 10:18:57) for OXNAS
DRAM: 128 MiB
IDE: Bus 0: OK
Device 0: Model: ST940210AS Firm: 3.ALC Ser#: 5QX21TEE
Type: Hard Disk
Supports 48-bit addressing
Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
OX820 # tftpboot 0x64000000 uboot.2013.10-tld-2.ox820.bin
Waiting for PHY auto negotiation to complete.. done
ENET Speed is 1000 Mbps - FULL duplex connection
Using mii0 device
TFTP from server 192.168.178.33; our IP address is 192.168.178.40
Filename 'uboot.2013.10-tld-2.ox820.bin'.
Load address: 0x64000000
Loading: T #################################################################
####################################
79.1 KiB/s
done
Bytes transferred = 514568 (7da08 hex)
OX820 # go 0x64000000
## Starting application at 0x64000000 ...
U-Boot 2013.10-tld-2-ga72eb8f-dirty (May 04 2014 - 14:20:05) for OXNAS
DRAM: 128 MiB
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
(Re)start USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 3 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found
4102704 bytes read in 498 ms (7.9 MiB/s)
1953812 bytes read in 351 ms (5.3 MiB/s)
7033 bytes read in 226 ms (30.3 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-3.17.0-oxnas-tld-1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4102640 Bytes = 3.9 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.17.0-oxnas-tld-1
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1953748 Bytes = 1.9 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 67c4d000, end 67e29fd4 ... OK
Loading Device Tree to 67c48000, end 67c4cb78 ... OK
Led: GREEN
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
[ 0.000000] Booting Linux on physical CPU 0x0
[ 0.000000] Linux version 3.17.0-oxnas-tld-1 (root@tldDebian) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP PREEMPT Sat Oct 25 15:59:43 PDT 2014
[ 0.000000] CPU: ARMv6-compatible processor [410fb025] revision 5 (ARMv7), cr=00c5787d
[ 0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[ 0.000000] Machine model: Pogoplug Pro
[ 0.000000] Memory policy: Data cache writealloc
[ 0.000000] DT missing boot CPU MPIDR[23:0], fall back to default cpu_logical_map
[ 0.000000] Start Ox820 platform
[ 0.000000] PERCPU: Embedded 7 pages/cpu @c7ee3000 s6592 r8192 d13888 u32768
[ 0.000000] Built 1 zonelists in Zone order, mobility grouping on. Total pages: 32512
[ 0.000000] Kernel command line: console=ttyS0,115200 root=/dev/sda1 rootdelay=10
[ 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] Memory: 119844K/131072K available (5686K kernel code, 286K rwdata, 1680K rodata, 174K init, 233K bss, 11228K reserved)
[ 0.000000] Virtual kernel memory layout:
[ 0.000000] vector : 0xffff0000 - 0xffff1000 ( 4 kB)
[ 0.000000] fixmap : 0xffc00000 - 0xffe00000 (2048 kB)
[ 0.000000] vmalloc : 0xc8800000 - 0xff000000 ( 872 MB)
[ 0.000000] lowmem : 0xc0000000 - 0xc8000000 ( 128 MB)
[ 0.000000] modules : 0xbf000000 - 0xc0000000 ( 16 MB)
[ 0.000000] .text : 0xc0008000 - 0xc0739db0 (7368 kB)
[ 0.000000] .init : 0xc073a000 - 0xc07659c0 ( 175 kB)
[ 0.000000] .data : 0xc0766000 - 0xc07adb00 ( 287 kB)
[ 0.000000] .bss : 0xc07adb00 - 0xc07e809c ( 234 kB)
[ 0.000000] SLUB: HWalign=32, Order=0-3, MinObjects=0, CPUs=2, Nodes=1
[ 0.000000] Preemptible hierarchical RCU implementation.
[ 0.000000] NR_IRQS:160
[ 0.000015] sched_clock: 24 bits at 390kHz, resolution 2560ns, wraps every 42949670400ns
[ 0.000181] Console: colour dummy device 80x30
[ 0.000209] Calibrating delay loop... 339.14 BogoMIPS (lpj=1695744)
[ 0.050042] pid_max: default: 32768 minimum: 301
[ 0.050199] Mount-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.050219] Mountpoint-cache hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.051038] Initializing cgroup subsys net_cls
[ 0.051100] CPU: Testing write buffer coherency: ok
[ 0.051486] Setting up static identity map for 0x60567fa0 - 0x60567fd8
[ 0.110446] CPU1: Booted secondary processor
[ 0.170140] Brought up 2 CPUs
[ 0.170165] SMP: Total of 2 processors activated.
[ 0.171092] devtmpfs: initialized
[ 0.175060] prandom: seed boundary self test passed
[ 0.178977] prandom: 100 self tests passed
[ 0.179000] pinctrl core: initialized pinctrl subsystem
[ 0.181788] NET: Registered protocol family 16
[ 0.182305] DMA: preallocated 256 KiB pool for atomic coherent allocations
[ 0.186421] gpio-oxnas 44000000.gpio: at address c8846000
[ 0.186693] gpio-oxnas 44100000.gpio: at address c8848000
[ 0.187251] pinctrl-oxnas pinctrl: initialized OX820 pinctrl driver
[ 0.198405] vgaarb: loaded
[ 0.198912] SCSI subsystem initialized
[ 0.199777] usbcore: registered new interface driver usbfs
[ 0.199884] usbcore: registered new interface driver hub
[ 0.200135] usbcore: registered new device driver usb
[ 0.200273] pps_core: LinuxPPS API ver. 1 registered
[ 0.200289] pps_core: Software ver. 5.3.6 - Copyright 2005-2007 Rodolfo Giometti <giometti@linux.it>
[ 0.200337] PTP clock support registered
[ 0.201820] cfg80211: Calling CRDA to update world regulatory domain
[ 0.202286] Switched to clocksource rps_clocksource_timer
[ 0.215956] NET: Registered protocol family 2
[ 0.217082] TCP established hash table entries: 1024 (order: 0, 4096 bytes)
[ 0.217126] TCP bind hash table entries: 1024 (order: 1, 8192 bytes)
[ 0.217159] TCP: Hash tables configured (established 1024 bind 1024)
[ 0.217244] TCP: reno registered
[ 0.217267] UDP hash table entries: 256 (order: 1, 8192 bytes)
[ 0.217308] UDP-Lite hash table entries: 256 (order: 1, 8192 bytes)
[ 0.217620] NET: Registered protocol family 1
[ 0.218106] RPC: Registered named UNIX socket transport module.
[ 0.218127] RPC: Registered udp transport module.
[ 0.218140] RPC: Registered tcp transport module.
[ 0.218150] RPC: Registered tcp NFSv4.1 backchannel transport module.
[ 0.218503] Unpacking initramfs...
[ 0.418465] Freeing initrd memory: 1904K (c7c4d000 - c7e29000)
[ 0.419545] futex hash table entries: 512 (order: 2, 16384 bytes)
[ 0.438397] NFS: Registering the id_resolver key type
[ 0.438466] Key type id_resolver registered
[ 0.438481] Key type id_legacy registered
[ 0.438520] nfs4filelayout_init: NFSv4 File Layout Driver Registering...
[ 0.438540] Installing knfsd (copyright (C) 1996 okir@monad.swb.de).
[ 0.439365] fuse init (API version 7.23)
[ 0.440668] msgmni has been set to 237
[ 0.441154] Key type big_key registered
[ 0.444884] alg: No test for stdrng (krng)
[ 0.518494] Block layer SCSI generic (bsg) driver version 0.4 loaded (major 252)
[ 0.518528] io scheduler noop registered
[ 0.518548] io scheduler deadline registered
[ 0.518894] io scheduler cfq registered (default)
[ 0.519493] Serial: 8250/16550 driver, 1 ports, IRQ sharing disabled
[ 0.520814] console [ttyS0] disabled
[ 0.520936] 44200000.uart: ttyS0 at MMIO 0x44200000 (irq = 55, base_baud = 390625) is a 16550A
[ 1.018657] console [ttyS0] enabled
[ 1.023910] scsi host0: sata_oxnas
[ 1.027904] ata1: SATA max UDMA/133 irq 50
[ 1.032322] ox820sata: reseting SATA core
[ 1.041666] nand: Could not find valid ONFI parameter page; aborting
[ 1.048030] nand: device found, Manufacturer ID: 0xad, Chip ID: 0xf1
[ 1.054382] nand: Hynix NAND 128MiB 3,3V 8-bit
[ 1.058805] nand: 128MiB, SLC, page size: 2048, OOB size: 64
[ 1.064463] Scanning device for bad blocks
[ 1.150269] 2 ofpart partitions found on MTD device 41000000.nand
[ 1.156352] Creating 2 MTD partitions on "41000000.nand":
[ 1.161743] 0x000000000000-0x000000e00000 : "boot"
[ 1.167900] 0x000000e00000-0x000008000000 : "data"
[ 1.174594] stmmaceth 40400000.ethernet: no reset control found
[ 1.180528] stmmac - user ID: 0x12, Synopsys ID: 0x35
[ 1.185548] Ring mode enabled
[ 1.188582] DMA HW capability register supported
[ 1.193100] Enhanced/Alternate descriptors
[ 1.197429] Enabled extended descriptors
[ 1.201428] RX Checksum Offload Engine supported (type 2)
[ 1.206881] TX Checksum insertion supported
[ 1.211136] Wake-Up On Lan supported
[ 1.214778] Enable RX Mitigation via HW Watchdog Timer
[ 1.241195] libphy: stmmac: probed
[ 1.244595] eth0: PHY ID 001cc914 at 0 IRQ POLL (stmmac-0:00) active
[ 1.250938] eth0: PHY ID 001cc914 at 3 IRQ POLL (stmmac-0:03)
[ 1.256785] PPP generic driver version 2.4.2
[ 1.261562] ehci_hcd: USB 2.0 'Enhanced' Host Controller (EHCI) Driver
[ 1.268072] ehci-pci: EHCI PCI platform driver
[ 1.273093] oxnas-ehci 40200100.ehci: EHCI Host Controller
[ 1.278589] oxnas-ehci 40200100.ehci: new USB bus registered, assigned bus number 1
[ 1.286382] oxnas-ehci 40200100.ehci: irq 39, io mem 0x40200100
[ 1.310545] oxnas-ehci 40200100.ehci: USB 2.0 started, EHCI 1.00
[ 1.316797] usb usb1: New USB device found, idVendor=1d6b, idProduct=0002
[ 1.323581] usb usb1: New USB device strings: Mfr=3, Product=2, SerialNumber=1
[ 1.330787] usb usb1: Product: EHCI Host Controller
[ 1.335644] usb usb1: Manufacturer: Linux 3.17.0-oxnas-tld-1 ehci_hcd
[ 1.342069] usb usb1: SerialNumber: 40200100.ehci
[ 1.347578] hub 1-0:1.0: USB hub found
[ 1.351424] hub 1-0:1.0: 2 ports detected
[ 1.356070] usbcore: registered new interface driver cdc_acm
[ 1.361738] cdc_acm: USB Abstract Control Model driver for USB modems and ISDN adapters
[ 1.369797] usbcore: registered new interface driver cdc_wdm
[ 1.375651] usbcore: registered new interface driver usb-storage
[ 1.381908] usbcore: registered new interface driver usbserial
[ 1.387781] usbcore: registered new interface driver usbserial_generic
[ 1.394393] usbserial: USB Serial support registered for generic
[ 1.400704] mousedev: PS/2 mouse device common for all mice
[ 1.406264] i2c /dev entries driver
[ 1.410836] usbcore: registered new interface driver usbhid
[ 1.416384] usbhid: USB HID core driver
[ 1.420569] TCP: cubic registered
[ 1.424998] NET: Registered protocol family 10
[ 1.430784] sit: IPv6 over IPv4 tunneling driver
[ 1.436372] NET: Registered protocol family 17
[ 1.441098] Key type dns_resolver registered
[ 1.560020] ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 310)
[ 1.568353] ata1.00: ATA-7: ST940210AS, 3.ALC, max UDMA/100
[ 1.573936] ata1.00: 78140160 sectors, multi 0: LBA48 NCQ (depth 0/32)
[ 1.585013] ata1.00: configured for UDMA/100
[ 1.600450] scsi 0:0:0:0: Direct-Access ATA ST940210AS C PQ: 0 ANSI: 5
[ 1.609704] sd 0:0:0:0: [sda] 78140160 512-byte logical blocks: (40.0 GB/37.2 GiB)
[ 1.618137] sd 0:0:0:0: [sda] Write Protect is off
[ 1.623157] sd 0:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[ 1.670589] usb 1-1: new high-speed USB device number 2 using oxnas-ehci
[ 1.804971] sda: sda1 sda2 sda3
[ 1.810398] sd 0:0:0:0: [sda] Attached SCSI disk
[ 1.815275] Freeing unused kernel memory: 172K (c073a000 - c0765000)
[ 1.821969] usb 1-1: New USB device found, idVendor=05e3, idProduct=0608
[ 1.828648] usb 1-1: New USB device strings: Mfr=0, Product=1, SerialNumber=0
[ 1.840599] usb 1-1: Product: USB2.0 Hub
Loading, please [ 1.845744] hub 1-1:1.0: USB hub found
wait...
[ 1.850183] hub 1-1:1.0: 4 ports detected
[ 1.969438] udevd[68]: starting version 175
[ 2.130908] usb 1-1.4: new high-speed USB device number 3 using oxnas-ehci
[ 2.263872] usb 1-1.4: New USB device found, idVendor=058f, idProduct=6387
[ 2.275553] usb 1-1.4: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[ 2.298001] usb 1-1.4: Product: Mass Storage
[ 2.302451] usb 1-1.4: Manufacturer: Generic
[ 2.306716] usb 1-1.4: SerialNumber: 0ED6D477
[ 2.318965] usb-storage 1-1.4:1.0: USB Mass Storage device detected
[ 2.351685] scsi host1: usb-storage 1-1.4:1.0
[ 2.458508] usbcore: registered new interface driver uas
[ 3.362298] scsi 1:0:0:0: Direct-Access Generic Flash Disk 8.07 PQ: 0 ANSI: 2
[ 3.376430] sd 1:0:0:0: [sdb] 15794176 512-byte logical blocks: (8.08 GB/7.53 GiB)
[ 3.384778] sd 1:0:0:0: [sdb] Write Protect is off
[ 3.391173] sd 1:0:0:0: [sdb] No Caching mode page found
[ 3.396477] sd 1:0:0:0: [sdb] Assuming drive cache: write through
[ 3.412917] sdb: sdb1 sdb2
[ 3.423534] sd 1:0:0:0: [sdb] Attached SCSI removable disk
Begin: Loading essential drivers ... done.
Begin: Running /scripts/init-premount ... done.
Begin: Mounting root file system ... Begin: Running /scripts/local-top ... done.
Begin: Running /scripts/local-premount ... done.
[ 13.095697] EXT4-fs (sda1): mounted filesystem with ordered data mode. Opts: (null)
Begin: Running /scripts/local-bottom ... done.
done.
Begin: Running /scripts/init-bottom ... done.
INIT: version 2.88 booting
[info] Using makefile-style concurrent boot in runlevel S.
[....] Starting the hotplug events dispatcher: udevd[ 15.322741] udevd[265]: starting version 175
. ok
[ ok ] Synthesizing the initial hotplug events...done.
[....] Waiting for /dev to be fully populated...[ 16.067015] random: nonblocking pool is initialized
done.
[ ok ] Activating swap...done.
[ 17.733242] EXT4-fs (sda1): re-mounted. Opts: (null)
[....] Checking root file system...fsck from util-linux 2.20.1
rootfs: clean, 13125/131072 files, 95851/524288 blocks
done.
[ 18.068764] EXT4-fs (sda1): re-mounted. Opts: errors=remount-ro
[ ok ] Loading kernel modules...done.
[ ok ] Cleaning up temporary files... /tmp /lib/init/rw.
[ ok ] Activating lvm and md swap...done.
[....] Checking file systems...fsck from util-linux 2.20.1
done.
[ ok ] Mounting local filesystems...done.
[ ok ] Activating swapfile swap...done.
[ ok ] Cleaning up temporary files....
[ ok ] Setting kernel variables ...done.
[....] Configuring network interfaces...Internet Systems Consortium DHCP Client 4.2.2
Copyright 2004-2011 Internet Systems Consortium.
All rights reserved.
For info, please visit https://www.isc.org/software/dhcp/
Listening on LPF/eth0/00:25:31:02:9a:90
Sending on LPF/eth0/00:25:31:02:9a:90
Sending on Socket/fallback
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPREQUEST on eth0 to 255.255.255.255 port 67
[ 30.160176] stmmaceth 40400000.ethernet eth0: Link is Up - 1Gbps/Full - flow control rx/tx
DHCPDISCOVER on eth0 to 255.255.255.255 port 67 interval 7
DHCPREQUEST on eth0 to 255.255.255.255 port 67
DHCPOFFER from 192.168.178.1
DHCPACK from 192.168.178.1
bound to 192.168.178.39 -- renewal in 378001 seconds.
done.
[ ok ] Starting rpcbind daemon....
[ ok ] Starting NFS common utilities: statd idmapd.
[ ok ] Cleaning up temporary files....
INIT: Entering runlevel: 2
[info] Using makefile-style concurrent boot in runlevel 2.
[ ok ] Starting NTP server: ntpd.
[ ok ] Starting rpcbind daemon...[....] Already running..
[....] Starting busybox' syslogd implementation : syslogdStarting /sbin/syslogd...
1811 (syslogd)
. ok
[ ok ] Starting system message bus: dbus.
[ ok ] Starting NFS common utilities: statd idmapd.
[....] Starting busybox' klogd implementation : klogdStarting /sbin/klogd...
[warn] Not starting NFS kernel daemon: no exports. ... (warning).
[ ok ] Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
[ ok ] Starting OpenBSD Secure Shell server: sshd.
1806 (klogd)
. ok
Debian GNU/Linux 7 debian ttyS0
debian login: root
Password:
Last login: Tue Apr 15 17:03:23 PDT 2014 from 192.168.0.100 on pts/0
Linux debian 3.17.0-oxnas-tld-1 #1 SMP PREEMPT Sat Oct 25 15:59:43 PDT 2014 armv6l
The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.
Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
root@debian:~#
Thank you very much Bodhi for efforts to help!
:))
Robert
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 11, 2015 11:03AM |
Registered: 11 years ago Posts: 214 |
@Robert,
SATA booting seams to work now. With your current setting you are booting an old kernel uImage_2.6.31.14_OX820_1.2_shv.Pro where you don't have the module path. You only need to change you boot settings by changing one line to:
dt_ide_bootcmd=run ide_set_bootargs; run dt_ide_boot
With this change you will use the files uImage, uInitrd, ox820-pogoplug-pro.dtb for booting. Then I would recommend you to save the boot directory and untar bodhis rootfs image:
Afterwards you must copy necessary files back from boot.bak to boot: u-boot.env, u-boot.img, u-boot-spl.bin(even not necessary), dts/ox820-pogoplug-pro.dtb(if not contained in rootfs image). uImage and uInitrd shall already be available there from rootfs image.
You can try booting then.
If you have non Pro devices or dtb is part of uImage you may need to adapt the boot-env setting to it. Just ask again if it is not working.
-shv
Edited 3 time(s). Last edit at 02/11/2015 11:06AM by shv.
SATA booting seams to work now. With your current setting you are booting an old kernel uImage_2.6.31.14_OX820_1.2_shv.Pro where you don't have the module path. You only need to change you boot settings by changing one line to:
dt_ide_bootcmd=run ide_set_bootargs; run dt_ide_boot
setenv dt_ide_bootcmd 'run ide_set_bootargs; run dt_ide_boot'
With this change you will use the files uImage, uInitrd, ox820-pogoplug-pro.dtb for booting. Then I would recommend you to save the boot directory and untar bodhis rootfs image:
mv boot boot.bak tar ...
Afterwards you must copy necessary files back from boot.bak to boot: u-boot.env, u-boot.img, u-boot-spl.bin(even not necessary), dts/ox820-pogoplug-pro.dtb(if not contained in rootfs image). uImage and uInitrd shall already be available there from rootfs image.
You can try booting then.
If you have non Pro devices or dtb is part of uImage you may need to adapt the boot-env setting to it. Just ask again if it is not working.
-shv
Edited 3 time(s). Last edit at 02/11/2015 11:06AM by shv.
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 11, 2015 11:21AM |
Admin Registered: 13 years ago Posts: 18,997 |
@Robert,
Do what shv suggesting above to boot SATA. You are very close! And then you can flash NAND SPL (if necessary u-boot too) from Linux shell. It's good to have alternatives, and SATA booting is a good rescue mechanism, too, even if you don't plan to use it every day.
However, as of right now, you can also flash it in u-boot console, if needed. The flashing commands are different from ones used in Linux shell.
..... And I've just realized that, as above with tftp, you are already in Debian prompt, so you can flash it from there now :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 02/11/2015 11:28AM by bodhi.
Do what shv suggesting above to boot SATA. You are very close! And then you can flash NAND SPL (if necessary u-boot too) from Linux shell. It's good to have alternatives, and SATA booting is a good rescue mechanism, too, even if you don't plan to use it every day.
However, as of right now, you can also flash it in u-boot console, if needed. The flashing commands are different from ones used in Linux shell.
..... And I've just realized that, as above with tftp, you are already in Debian prompt, so you can flash it from there now :)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 02/11/2015 11:28AM by bodhi.
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 11, 2015 01:35PM |
Registered: 10 years ago Posts: 64 |
Hi Bodhi, and Shv,
Thanks for advises.
I cleared and flashed uboot.850
I tried to follow instructions but boot failed again.
What is wrong again? :(
Thanks for advises.
I cleared and flashed uboot.850
I tried to follow instructions but boot failed again.
OX820 # reset
resetting ...
U-Boot SPL 2013.10-g3a0f380-dirty (Jul 26 2014 - 14:31:34)
Boot device: SATA
Attempting to set PLLA to 850 MHz ...
plla_ctrl0 : 0000020a
plla_ctrl1 : 00330000
plla_ctrl2 : 0065008b
plla_ctrl3 : 000000f1
PLLA Set
Bus 0: OK
Device 0:
** File not found /boot/bootargs.bin **
U-Boot 2013.10-g3a0f380-dirty (Jul 26 2014 - 10:18:57) for OXNAS
DRAM: 128 MiB
IDE: Bus 0: OK
Device 0: Model: ST940210AS Firm: 3.ALC Ser#: 5QX21TEE
Type: Hard Disk
Supports 48-bit addressing
Capacity: 38154.3 MB = 37.2 GB (78140160 x 512)
NAND: 128 MiB
In: serial
Out: serial
Err: serial
Net:
Led: GREEN
mii0
Main Loop
Hit any key to stop autoboot: 0
ide - IDE sub-system
Usage:
ide reset - reset IDE controller
ide info - show available IDE devices
ide device [dev] - show or set current device
ide part [dev] - print partition table of one or all IDE devices
ide read addr blk# cnt
ide write addr blk# cnt - read/write `cnt' blocks starting at block `blk#'
to/from memory address `addr'
4102704 bytes read in 636 ms (6.2 MiB/s)
1953812 bytes read in 315 ms (5.9 MiB/s)
7029 bytes read in 46 ms (148.4 KiB/s)
## Booting kernel from Legacy Image at 60500000 ...
Image Name: Linux-3.17.0-oxnas-tld-1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 4102640 Bytes = 3.9 MiB
Load Address: 60008000
Entry Point: 60008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 60e00000 ...
Image Name: initramfs-3.17.0-oxnas-tld-1
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 1953748 Bytes = 1.9 MiB
Load Address: 60000000
Entry Point: 60000000
Verifying Checksum ... OK
## Flattened Device Tree blob at 62c00000
Booting using the fdt blob at 0x62c00000
Loading Kernel Image ... OK
Loading Ramdisk to 67c4b000, end 67e27fd4 ... OK
Loading Device Tree to 67c46000, end 67c4ab74 ... OK
Led: GREEN
Starting kernel ...
Uncompressing Linux... done, booting the kernel.
OX820 # printenv autoload=no baudrate=115200 bootargs=console=ttyS0,115200n8 bootcmd=run dt_bootcmd_ide bootdelay=3 console=console=ttyS0,115200n8 dt_bootcmd_ide=ide start; run dt_ide_bootcmd; ide stop; reset dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr dt_ide_boot=run dt_ide_load_uimage; run dt_ide_load_initrd; run dt_ide_load_dtb; run dt_bootm dt_ide_bootcmd=run ide_set_bootargs; run dt_ide_boot dt_ide_load_dtb=ext2load ide 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb dt_ide_load_initrd=ext2load ide 0:1 $uinitrd_addr /boot/uInitrd dt_ide_load_uimage=ext2load ide 0:1 $uimage_addr /boot/uImage dt_load_dtb=ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage dt_sata_boot=ext2load ide 0:1 $uimage_addr /boot/uImage_2.6.31.14_OX820_1.2_shv.Pro; bootm $uimage_addr dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot dtb_addr=0x62c00000 ethact=mii0 ethaddr=00:25:31:02:9A:90 ide_set_bootargs=setenv bootargs root=/dev/sda1 rootfstype=ext4 console=ttyS0,115200 mem=128M if_netconsole=ping $serverip ipaddr=192.168.178.40 mtdids=nand0=41000000.nand mtdparts=mtdparts=41000000.nand:14m(boot),-(data) preboot_nc=run if_netconsole start_netconsole sata_bootcmd=run usb_set_bootargs; run sata_boot serverip=192.168.178.33 start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version stderr=serial stdin=serial stdout=serial uimage_addr=0x60500000 uinitrd_addr=0x60e00000 usb_device=0:1 usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10 Environment size: 1869/16380 bytes
What is wrong again? :(
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 11, 2015 02:02PM |
Admin Registered: 13 years ago Posts: 18,997 |
@robert
Make sure uImage is the one that came from the rootfs tarball. It should not have DTB embedded in it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Starting kernel ... Uncompressing Linux... done, booting the kernel.
Make sure uImage is the one that came from the rootfs tarball. It should not have DTB embedded in it.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 11, 2015 02:35PM |
Registered: 10 years ago Posts: 64 |
Thanks Bodhi,
> Make sure uImage is the one that came from the rootfs tarball. It should not have DTB embedded in it.
On rootfs, date and size is same as in tar.bz2
> Make sure uImage is the one that came from the rootfs tarball. It should not have DTB embedded in it.
On rootfs, date and size is same as in tar.bz2
/media/b/rootfs/boot big2 boot # ls -la összesen 18004 drwxr-xr-x 3 root root 4096 febr 11 20:06 . drwxr-xr-x 23 root root 4096 febr 11 20:08 .. -rw-r--r-- 1 root root 98866 okt 26 01:08 config-3.17.0-oxnas-tld-1 drwxr-xr-x 2 root root 4096 nov 1 08:05 dts -rw-r--r-- 1 root root 1953748 nov 1 08:05 initrd.img-3.17.0-oxnas-tld-1 -rw-r--r-- 1 root root 1519590 okt 26 01:08 System.map-3.17.0-oxnas-tld-1 -rwxr-xr-x 1 root root 16384 jan 1 1970 u-boot.env -rw-r--r-- 1 root root 525880 aug 3 2014 u-boot.img -rwxr-xr-x 1 root root 32120 aug 3 2014 u-boot-spl.bin -rw-r--r-- 1 root root 4102704 nov 1 08:16 uImage -rw-r--r-- 1 root root 1953812 nov 1 08:18 uInitrd -rwxr-xr-x 1 root root 4102640 okt 26 01:08 vmlinuz-3.17.0-oxnas-tld-1 -rwxr-xr-x 1 root root 4102640 okt 26 01:00 zImage-3.17.0-oxnas-tld-1
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 11, 2015 02:46PM |
Registered: 11 years ago Posts: 214 |
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 12, 2015 01:15AM |
Registered: 10 years ago Posts: 64 |
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 12, 2015 01:34AM |
Registered: 10 years ago Posts: 12 |
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 12, 2015 02:48AM |
Registered: 10 years ago Posts: 64 |
Dear Bodhi, Shv, Morph027
YESS!! SATA UBoot booted!
Rename x820-pogoplug-classic.dtb to ox820-pogoplug-pro.dtb solves the last problem.
THANK YOU VERY MUCH GUYS!!
You are so helpful, and I couldnt thank you enought.
I respect you all for so deep knowledge - I know you - work for very hard.
My original problem was to screw up Uboot in Nand with update in a wrong way.
So I will reflash uboot on nand, and try to eliminate sata boot, because I would use this box without sata or Usb.
Just NAND booting Embdebian.
But this will be the next challenge. :)
Now I have small problem with env. but hope will solved with reflashing uboot env.img.
Best Regards,
Robert
YESS!! SATA UBoot booted!
Rename x820-pogoplug-classic.dtb to ox820-pogoplug-pro.dtb solves the last problem.
THANK YOU VERY MUCH GUYS!!
You are so helpful, and I couldnt thank you enought.
I respect you all for so deep knowledge - I know you - work for very hard.
My original problem was to screw up Uboot in Nand with update in a wrong way.
So I will reflash uboot on nand, and try to eliminate sata boot, because I would use this box without sata or Usb.
Just NAND booting Embdebian.
But this will be the next challenge. :)
Now I have small problem with env. but hope will solved with reflashing uboot env.img.
root@debian:~# fw_printenv
Warning: Bad CRC, using default environment
bootcmd=bootp; setenv bootargs root=/dev/nfs nfsroot=${serverip}:${rootpath} ip=${ipaddr}:${serverip}:${gatewayip}:${netmask}:${hostname}::off; bootm
bootdelay=5
baudrate=115200
root@debian:~#
Best Regards,
Robert
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 12, 2015 04:29AM |
Registered: 10 years ago Posts: 64 |
Just for reference to others, I made a very detailed summary.
Please revise my comment are there right in technical aspect. (?? if I have doubt - I will revise based on your comment)
Synopsys:
My device Pogo Plug P24 - V3 (nonpci) - oxnas 820
I have serial connection,
I Screw up UBoot in NAND - Therefore no boot from USB,
and NOTHING appears on Serial console!!!
Only way to boot is well prepared SATA because oxnas tries to boot Uboot on SATA then Uboot on NAND then USB. (?? is that right??)
Steps
1. Get a SATA HDD. You have to delete all partition from it. Sorry :(
2. Put it to USB HDD frame. Attache to PC. Umount all partition if automount happened.
3. remove partitions, and create new.
4. mkext4 fs.
( If you have problems with "mkfs.ext4 /dev/sdb is not a block special device."
Detach USB _and_ reboot your PC. and attache again - will solve the problem...)
5 Labell it:
6.Mount rootfs
7. Prepare Sata uboot file on PC :
a.) Extract the content Shv made ox820-sata-uboot.tar.gz to your PC
(It is only a boot directory on your PC)
Navigate to /yourpath/boot/dts directory and rename this files:
-it is only needed in case noPCI devices like P24.
b.) and copy modified /yourpath/boot directory to the rootfs partition.
c.)Modify 2 lines in disk create script on your PC:
c1.) disk=/dev/sdb
c2.) workarea="/yourpath"
d.) save changes
8. Now you have to run Sata uboot SCRIPT on your PC.
It will write U-Boot SPL to Sata disk on the beginning (in the first 2048 sector) on the disk.
8a.) Umount - Just to be safe side: Not write to disk which is mounted... - skip if brave.
8b.) Run Sata uboot SCRIPT
Prepare Debian Rootfs files.
9.) Mount rootfs again:
10.) Extract debian files to your PC /yourpath directory. Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
11. Copy all directory from PC to your rootfs partition BUT /boot . (It means do not overwrite the existing /boot on rootfs!!)
detach from PC and attache to Pogo.
Attache serial TTL connector and see output. Trust Bodhi, Picocom is better than GNU Screen. I learned :)
Power on your POGO.
Debian will not boot because Uboot env not well set for this configuration. try it but for sure it will freeze. :) then power on - and - of again.
Now Stop the counter by press a key:
Now set the environment to this setup:
Boot success!!
I hope -you Masters (Bodhi, SHV, Morph) - find my guide is useful. :) and it is a little benefit give back to community. Respect.
Edited 3 time(s). Last edit at 02/14/2015 04:24PM by robert1968@gmail.com.
Please revise my comment are there right in technical aspect. (?? if I have doubt - I will revise based on your comment)
Synopsys:
My device Pogo Plug P24 - V3 (nonpci) - oxnas 820
I have serial connection,
I Screw up UBoot in NAND - Therefore no boot from USB,
and NOTHING appears on Serial console!!!
Only way to boot is well prepared SATA because oxnas tries to boot Uboot on SATA then Uboot on NAND then USB. (?? is that right??)
Steps
1. Get a SATA HDD. You have to delete all partition from it. Sorry :(
2. Put it to USB HDD frame. Attache to PC. Umount all partition if automount happened.
3. remove partitions, and create new.
fdisk /dev/sdb o - create a new empty DOS partition table n - Create part 1 (start with 2048 ; size: +2G ) w - write q - exit
4. mkext4 fs.
mkfs.ext4 /dev/sdb1
( If you have problems with "mkfs.ext4 /dev/sdb is not a block special device."
Detach USB _and_ reboot your PC. and attache again - will solve the problem...)
5 Labell it:
tune2fs -L "rootfs" /dev/sdb1
6.Mount rootfs
mount /dev/sdb1 /media/rootfs
7. Prepare Sata uboot file on PC :
a.) Extract the content Shv made ox820-sata-uboot.tar.gz to your PC
cd /yourpath tar -xjf ox820-sata-uboot.tar.gz
(It is only a boot directory on your PC)
Navigate to /yourpath/boot/dts directory and rename this files:
-it is only needed in case noPCI devices like P24.
mv ox820-pogoplug-pro.dtb ox820-pogoplug-pro.dtb.ori cp ox820-pogoplug-classic.dtb ox820-pogoplug-pro.dtb
b.) and copy modified /yourpath/boot directory to the rootfs partition.
c.)Modify 2 lines in disk create script on your PC:
c1.) disk=/dev/sdb
c2.) workarea="/yourpath"
d.) save changes
8. Now you have to run Sata uboot SCRIPT on your PC.
It will write U-Boot SPL to Sata disk on the beginning (in the first 2048 sector) on the disk.
8a.) Umount - Just to be safe side: Not write to disk which is mounted... - skip if brave.
umount rootfs
8b.) Run Sata uboot SCRIPT
./disk_create_shv
Prepare Debian Rootfs files.
9.) Mount rootfs again:
mount /dev/sdb1 /media/rootfs
10.) Extract debian files to your PC /yourpath directory. Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
tar -xjf Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
11. Copy all directory from PC to your rootfs partition BUT /boot . (It means do not overwrite the existing /boot on rootfs!!)
detach from PC and attache to Pogo.
Attache serial TTL connector and see output. Trust Bodhi, Picocom is better than GNU Screen. I learned :)
picocom -b 115200 /dev/ttyUSB0
Power on your POGO.
Debian will not boot because Uboot env not well set for this configuration. try it but for sure it will freeze. :) then power on - and - of again.
Now Stop the counter by press a key:
Hit any key to stop autoboot: 3
Now set the environment to this setup:
OX820 # setenv dt_ide_bootcmd 'run ide_set_bootargs; run dt_ide_boot' OX820 # setenv ide_set_bootargs setenv bootargs 'root=/dev/sda1 rootfstype=ext4 console=ttyS0,115200 mem=128M' OX820 # saveenv OX820 # reset
Boot success!!
I hope -you Masters (Bodhi, SHV, Morph) - find my guide is useful. :) and it is a little benefit give back to community. Respect.
Edited 3 time(s). Last edit at 02/14/2015 04:24PM by robert1968@gmail.com.
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 12, 2015 12:41PM |
Registered: 11 years ago Posts: 214 |
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 14, 2015 02:45AM |
Registered: 10 years ago Posts: 64 |
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 14, 2015 03:21AM |
Admin Registered: 13 years ago Posts: 18,997 |
@Robert,
Should be:
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Quote
It will write UBOOT to Sata disk on the beginning (in the first 2048 sector) on the disk (not on rootfs.) (??)
Should be:
Quote
It will write U-Boot SPL to Sata disk on the beginning (in the first 2048 sector) on the disk.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 14, 2015 04:23PM |
Registered: 10 years ago Posts: 64 |
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 15, 2015 10:41PM |
Registered: 10 years ago Posts: 3 |
I've been following Robert's struggle for the past few posts and seem to be having the same issue. I have at least 6 pogoplugs i've been working with and on over the last couple of years. I've successfully installed Debian on a V3 and a V3Pro. I borked a V4 while trying to get a decent serial connection soldered onto the board. I'm back to working on another of the V3's and wanted to try a newer kernel.
Thankfully I have serial connections for all my devices and can easily monitor the boot output. This is where the boot process stops:
A quick look at the uboot info gives me this:
I have a usb thumb drive I've used before to boot one of the other V3's and it fails to boot, I have a blank usb drive to test with, and 60GB sata drive. I've spent the past 2 days trying every configuration and "post" and I'm certain I've managed to goof up the uboot configuration. Any thoughts or suggestions would be much appreciated.
Thankfully I have serial connections for all my devices and can easily monitor the boot output. This is where the boot process stops:
U-Boot SPL 2013.10 (Apr 27 2014 - 19:08:27) Boot device: NAND Attempting to set PLLA to 800 MHz ... plla_ctrl0 : 0000030a plla_ctrl1 : 00400000 plla_ctrl2 : 007f0068 plla_ctrl3 : 00000193 PLLA Set U-Boot 2013.10-tld-3 (May 15 2014 - 14:54:14) for OXNAS DRAM: 128 MiB NAND: 128 MiB In: serial Out: serial Err: serial Net: Led:.GREEN mii0 Main Loop Hit any key to stop autoboot: 5 ... 4 ... 3 ... 2 ... 1 ... 0 ## Error: "ideboot" not defined OX820 #
A quick look at the uboot info gives me this:
autoload=no baudrate=115200 bootargs=root=/dev/sda1 rootfstype=ext4 console=ttyS0,115200 mem=128M bootcmd=run ideboot bootdelay=5 console=console=ttyS0,115200n8 ethact=mii0 ethaddr=00:25:31:01:66:5F ide_set_bootargs=root=/dev/sda1 rootfstype=ext4 console=ttyS0,115200 mem=128M ipaddr=192.168.0.13 keypressed=1 mtdids=nand0=41000000.nand mtdparts=mtdparts=41000000.nand:14m(boot),-(data) netcon=echo switch to net console;setenv stderr nc;setenv stdin nc;setenv stdout nc;echo switch to net console safeboot=setexpr.b keypressed '*44200005' '&' 1;if test $keypressed = 0;then run netcon;fi serialcon=echo switch to serial console;setenv stderr serial;setenv stdin serial;setenv stdout serial;echo switch to serial console serverip=192.168.0.20 stderr=serial stdin=serial stdout=serial
I have a usb thumb drive I've used before to boot one of the other V3's and it fails to boot, I have a blank usb drive to test with, and 60GB sata drive. I've spent the past 2 days trying every configuration and "post" and I'm certain I've managed to goof up the uboot configuration. Any thoughts or suggestions would be much appreciated.
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 15, 2015 11:04PM |
Registered: 9 years ago Posts: 429 |
Looks like your V3 is trying to boot from ide. If what you posted is your complete printenv, you are missing some stuff.
Here is my ide boot setenv's (partial) for a frame of reference:
setenv uinitrd_addr '0x60e00000'
setenv uimage_addr '0x60500000'
setenv dtb_addr '0x62c00000'
setenv ide_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr'
setenv dt_load_dtb 'ext2load ide 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb'
setenv dt_load_initrd 'ext2load ide 0:1 $uinitrd_addr /boot/uInitrd'
setenv dt_load_uimage 'ext2load ide 0:1 $uimage_addr /boot/uImage'
setenv dt_ide_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm'
setenv dt_ide_bootcmd 'run ide_set_bootargs; run dt_ide_boot'
setenv dt_bootcmd_ide 'ide reset; run dt_ide_bootcmd; reset'
setenv bootcmd 'run dt_bootcmd_ide'
And for usb booting it's this (complete):
setenv autoload no
setenv baudrate 115200
setenv bootargs console=ttyS0,115200n8
setenv bootdelay 10
setenv console console=ttyS0,115200n8
setenv ethact mii0
setenv ethaddr (removed for security)
setenv ipaddr 192.168.1.100
setenv mtdids nand0=41000000.nand
setenv mtdparts mtdparts=41000000.nand:14m(boot),-(data)
setenv serverip 192.168.1.110
setenv stderr serial
setenv stdin serial
setenv stdout serial
setenv usb_device 0:1
setenv if_netconsole ping $serverip
setenv preboot_nc run if_netconsole start_netconsole
setenv start_netconsole setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
setenv usb_set_bootargs setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
setenv uinitrd_addr 0x60e00000
setenv uimage_addr 0x60500000
setenv dtb_addr 0x62c00000
setenv dt_load_dtb ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
setenv dt_load_initrd ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
setenv dt_load_uimage ext2load usb 0:1 $uimage_addr /boot/uImage
setenv dt_bootm bootm $uimage_addr $uinitrd_addr $dtb_addr
setenv dt_usb_boot run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
setenv dt_usb_bootcmd run usb_set_bootargs; run dt_usb_boot
setenv dt_bootcmd_usb usb start; run dt_usb_bootcmd; usb stop; reset
setenv bootcmd run dt_bootcmd_usb
I think your V3 uses another dtb so you might need to change that.
Do a printenv and try to determine what you are missing based on what I have posted. Note that my boot env's are pretty simple compared to some of the really complicated netconsole / tftp ones I have seen on the forum so you might want to take a look at some of those if you wanna get funky.
Here is my ide boot setenv's (partial) for a frame of reference:
setenv uinitrd_addr '0x60e00000'
setenv uimage_addr '0x60500000'
setenv dtb_addr '0x62c00000'
setenv ide_set_bootargs 'setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10'
setenv dt_bootm 'bootm $uimage_addr $uinitrd_addr $dtb_addr'
setenv dt_load_dtb 'ext2load ide 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb'
setenv dt_load_initrd 'ext2load ide 0:1 $uinitrd_addr /boot/uInitrd'
setenv dt_load_uimage 'ext2load ide 0:1 $uimage_addr /boot/uImage'
setenv dt_ide_boot 'run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm'
setenv dt_ide_bootcmd 'run ide_set_bootargs; run dt_ide_boot'
setenv dt_bootcmd_ide 'ide reset; run dt_ide_bootcmd; reset'
setenv bootcmd 'run dt_bootcmd_ide'
And for usb booting it's this (complete):
setenv autoload no
setenv baudrate 115200
setenv bootargs console=ttyS0,115200n8
setenv bootdelay 10
setenv console console=ttyS0,115200n8
setenv ethact mii0
setenv ethaddr (removed for security)
setenv ipaddr 192.168.1.100
setenv mtdids nand0=41000000.nand
setenv mtdparts mtdparts=41000000.nand:14m(boot),-(data)
setenv serverip 192.168.1.110
setenv stderr serial
setenv stdin serial
setenv stdout serial
setenv usb_device 0:1
setenv if_netconsole ping $serverip
setenv preboot_nc run if_netconsole start_netconsole
setenv start_netconsole setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
setenv usb_set_bootargs setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
setenv uinitrd_addr 0x60e00000
setenv uimage_addr 0x60500000
setenv dtb_addr 0x62c00000
setenv dt_load_dtb ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
setenv dt_load_initrd ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
setenv dt_load_uimage ext2load usb 0:1 $uimage_addr /boot/uImage
setenv dt_bootm bootm $uimage_addr $uinitrd_addr $dtb_addr
setenv dt_usb_boot run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
setenv dt_usb_bootcmd run usb_set_bootargs; run dt_usb_boot
setenv dt_bootcmd_usb usb start; run dt_usb_bootcmd; usb stop; reset
setenv bootcmd run dt_bootcmd_usb
I think your V3 uses another dtb so you might need to change that.
Do a printenv and try to determine what you are missing based on what I have posted. Note that my boot env's are pretty simple compared to some of the really complicated netconsole / tftp ones I have seen on the forum so you might want to take a look at some of those if you wanna get funky.
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 15, 2015 11:50PM |
Admin Registered: 13 years ago Posts: 18,997 |
@thebladerunner,
You are running the new u-boot, but with the default envs from internal u-boot settings. You should have also flashed the default envs image (step 10) if you are going to run an FDT kernel/rootfs such as this rootfs.
So right now, to recover you can do either one of the following at u-boot console prompt:
1. Copy and paste each of the default envs listing from step 12. And boot
2. Copy and paste each of the envs from Leggo's post above. And boot.
After you have booted successfully into Debian, flash the envs image in step 10.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 02/15/2015 11:51PM by bodhi.
You are running the new u-boot, but with the default envs from internal u-boot settings. You should have also flashed the default envs image (step 10) if you are going to run an FDT kernel/rootfs such as this rootfs.
10. Flash uboot environment to 0x00100000 (See caveat in step 2, do not flash this if the kernel is not FDT)
So right now, to recover you can do either one of the following at u-boot console prompt:
1. Copy and paste each of the default envs listing from step 12. And boot
12. For sanity check, print out uBoot envs to see if they were flashed OK. If there is error in listing the envs, do not reboot and post your problem here.
2. Copy and paste each of the envs from Leggo's post above. And boot.
After you have booted successfully into Debian, flash the envs image in step 10.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Edited 1 time(s). Last edit at 02/15/2015 11:51PM by bodhi.
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 18, 2015 05:59PM |
Registered: 10 years ago Posts: 3 |
Ok. I'm pleased to report that I was able to get my PP V3 up and running. It ended up being a problem with the uBoot env variables. The configuration that finally worked is listed below:
Specifically I think there was a conflict in one of the boot commands and its arguments. Many thanks to LeggoMyEggo and Bodhi.
I was also able to get a usb wifi dongle to work. I've been using the Realtek based dongles on my RBPi boxen for the past couple of years and had an extras to test with.
autoload=no baudrate=115200 boot_nand=run load_nand boot || run load_nand2 boot bootargs=console=ttyS0,115200n8 bootcmd=run dt_bootcmd_usb bootdelay=5 console=console=ttyS0,115200n8 dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr dt_load_dtb=ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-classic.dtb dt_load_image=ext2load usb 0:1 $uimage_addr /boot/uImage dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot dtb_addr=0x62c00000 ethact=mii0 ethaddr=00:25:31:xx:xx:xx ipaddr=192.168.0.4 keypressed=1 mtdids=nand0=41000000.nand mtdparts=mtdparts=41000000.nand:14m(boot),-(data) netmask=255.255.0.0 serverip=192.168.0.20 stderr=serial stdin=serial stdout=serial uimage_addr=0x60500000 uinitrd_addr=0x60e00000 usb_device=0:1 usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
Specifically I think there was a conflict in one of the boot commands and its arguments. Many thanks to LeggoMyEggo and Bodhi.
I was also able to get a usb wifi dongle to work. I've been using the Realtek based dongles on my RBPi boxen for the past couple of years and had an extras to test with.
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) February 18, 2015 08:27PM |
Registered: 9 years ago Posts: 429 |
Myself not the brightest bulb in the bunch what I have discovered recently, besides the obvious necessity and importance of having serial console, is when you are in the middle of trying to diagnose boot env issues, sometimes it's best to printenv then copy and paste them and then print them out on paper so that you can follow the logic and instruction sequencing. I believe 'bootcmd' is what the firmware uses to start the whole process of booting regardless if booting from NAND, USB drive, SD card or SATA depending on platform so if every setting and command execution that flows from that is logical and calls for variables that have been set properly, then you should be ok. It also helps to print them to a document so that you can tweak them all at once, check for errors or typos and then copy/paste/enter them all at once with confidence that you haven't left something out. And always remember to 'saveenv' or 'fw_saveenv' frequently so you don't lose your work.
Edited 3 time(s). Last edit at 02/18/2015 08:36PM by LeggoMyEggo.
Edited 3 time(s). Last edit at 02/18/2015 08:36PM by LeggoMyEggo.
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) March 05, 2015 01:08AM |
Admin Registered: 13 years ago Posts: 18,997 |
I've uploaded the uboot.2013.10-tld-4 u-Boot image for Pogoplug V3 Oxnas. Please see 1st post for download link.
This u-boot supports the following latest U-Boot features (among others):
- Ability to customize u-boot envs in a script (uEnv.txt) during boot, without committing changes to NAND. This feature also can be used for rescue purpose where the u-boot envs were messed up, or when the NAND envs block is bad.
- both FDT and non-FDT kernel booting
- supports EFI/GPT partition > 2TB (SATA and USB) either for booting or just attached.
- boot Ext4 rootfs
- SNTP (Simple NTP to set date time during U-Boot booting)
- bootz (boot with zImage).
- Run the Pogo V3 at 850mhz (for whatever reason, if you wish to run at 700Mhz as previous version did, then use the old u-boot SPL version uboot.spl.2013.10.ox820.mtd0.img). U-boot image proper is independent of the SPL, so it can still be updated to uboot.2013.10-tld-4.
Note: this version does not have NAND jffs2 file system supports (it is gotten quite big, so this was removed to save space, ubifs is preferred anyway).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
This u-boot supports the following latest U-Boot features (among others):
- Ability to customize u-boot envs in a script (uEnv.txt) during boot, without committing changes to NAND. This feature also can be used for rescue purpose where the u-boot envs were messed up, or when the NAND envs block is bad.
- both FDT and non-FDT kernel booting
- supports EFI/GPT partition > 2TB (SATA and USB) either for booting or just attached.
- boot Ext4 rootfs
- SNTP (Simple NTP to set date time during U-Boot booting)
- bootz (boot with zImage).
- Run the Pogo V3 at 850mhz (for whatever reason, if you wish to run at 700Mhz as previous version did, then use the old u-boot SPL version uboot.spl.2013.10.ox820.mtd0.img). U-boot image proper is independent of the SPL, so it can still be updated to uboot.2013.10-tld-4.
Note: this version does not have NAND jffs2 file system supports (it is gotten quite big, so this was removed to save space, ubifs is preferred anyway).
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) March 05, 2015 04:57PM |
Registered: 9 years ago Posts: 429 |
OK bodhi, here is the screen print from reflashing the new u-boot and it shows the bad blocks I have and the inability to store the u-envs. I'll try to set up the uenv.txt file in /boot and see how it goes.
root@new-host-2:/boot# dmesg | grep -i 'bad'
[ 1.554009] Scanning device for bad blocks
[ 1.558776] Bad eraseblock 8 at 0x000000100000
[ 1.605959] Bad eraseblock 539 at 0x000004360000
[ 1.618984] Bad eraseblock 645 at 0x0000050a0000
root@new-host-2:/boot# wget http://download.doozan.com/uboot/nanddump
--2015-03-05 14:48:38-- http://download.doozan.com/uboot/nanddump
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 21286 (21K) []
Saving to: `nanddump'
100%[========================================================>] 21,286 --.-K/s in 0.07s
2015-03-05 14:48:38 (301 KB/s) - `nanddump' saved [21286/21286]
root@new-host-2:/boot# wget http://download.doozan.com/uboot/nandwrite
--2015-03-05 14:48:47-- http://download.doozan.com/uboot/nandwrite
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 11500 (11K) []
Saving to: `nandwrite'
100%[========================================================>] 11,500 --.-K/s in 0.05s
2015-03-05 14:48:48 (224 KB/s) - `nandwrite' saved [11500/11500]
root@new-host-2:/boot# wget http://download.doozan.com/uboot/flash_erase
--2015-03-05 14:48:58-- http://download.doozan.com/uboot/flash_erase
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 12819 (13K) []
Saving to: `flash_erase'
100%[========================================================>] 12,819 --.-K/s in 0.06s
2015-03-05 14:48:58 (212 KB/s) - `flash_erase' saved [12819/12819]
root@new-host-2:/boot# wget http://download.doozan.com/uboot/fw_printenv
--2015-03-05 14:49:08-- http://download.doozan.com/uboot/fw_printenv
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 668497 (653K) []
Saving to: `fw_printenv'
100%[========================================================>] 668,497 1.25M/s in 0.5s
2015-03-05 14:49:09 (1.25 MB/s) - `fw_printenv' saved [668497/668497]
root@new-host-2:/boot# wget http://download.doozan.com/uboot/fw_env.config
--2015-03-05 14:49:18-- http://download.doozan.com/uboot/fw_env.config
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 329 []
Saving to: `fw_env.config'
100%[========================================================>] 329 --.-K/s in 0s
2015-03-05 14:49:18 (3.95 MB/s) - `fw_env.config' saved [329/329]
root@new-host-2:/boot# wget http://download.doozan.com/uboot/files/environment/uboot.environment
--2015-03-05 14:49:27-- http://download.doozan.com/uboot/files/environment/uboot.environment
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 131072 (128K) []
Saving to: `uboot.environment'
100%[========================================================>] 131,072 381K/s in 0.3s
2015-03-05 14:49:28 (381 KB/s) - `uboot.environment' saved [131072/131072]root@new-host-2:/boot# chmod a+x flash*
root@new-host-2:/boot# chmod a+x fw_printenv
root@new-host-2:/boot# chmod a+x nand*
root@new-host-2:/boot# ./flash_erase /dev/mtd0 0x0 6
Erase Total 6 Units
Performing Flash Erase of length 131072 at offset 0xa0000 done
root@new-host-2:/boot# ./nandwrite /dev/mtd0 uboot.spl.2013.10.ox820.850mhz.mtd0.img
Writing data to block 0 at offset 0x0
root@new-host-2:/boot# ./nandwrite -s 262144 /dev/mtd0 uboot.2013.10-tld-4.ox820.mtd0.img
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
root@new-host-2:/boot# ./flash_erase /dev/mtd0 0x00100000 1
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0x100000
MTD Erase failure: Input/output error
root@new-host-2:/boot# ./nandwrite -s 1048576 /dev/mtd0 pogopro_uboot_env.img
Writing data to block 8 at offset 0x100000
Bad block at 100000, 1 block(s) from 100000 will be skipped
Writing data to block 9 at offset 0x120000
root@new-host-2:/boot# dmesg | grep -i 'bad'
[ 1.554009] Scanning device for bad blocks
[ 1.558776] Bad eraseblock 8 at 0x000000100000
[ 1.605959] Bad eraseblock 539 at 0x000004360000
[ 1.618984] Bad eraseblock 645 at 0x0000050a0000
root@new-host-2:/boot# wget http://download.doozan.com/uboot/nanddump
--2015-03-05 14:48:38-- http://download.doozan.com/uboot/nanddump
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 21286 (21K) []
Saving to: `nanddump'
100%[========================================================>] 21,286 --.-K/s in 0.07s
2015-03-05 14:48:38 (301 KB/s) - `nanddump' saved [21286/21286]
root@new-host-2:/boot# wget http://download.doozan.com/uboot/nandwrite
--2015-03-05 14:48:47-- http://download.doozan.com/uboot/nandwrite
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 11500 (11K) []
Saving to: `nandwrite'
100%[========================================================>] 11,500 --.-K/s in 0.05s
2015-03-05 14:48:48 (224 KB/s) - `nandwrite' saved [11500/11500]
root@new-host-2:/boot# wget http://download.doozan.com/uboot/flash_erase
--2015-03-05 14:48:58-- http://download.doozan.com/uboot/flash_erase
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 12819 (13K) []
Saving to: `flash_erase'
100%[========================================================>] 12,819 --.-K/s in 0.06s
2015-03-05 14:48:58 (212 KB/s) - `flash_erase' saved [12819/12819]
root@new-host-2:/boot# wget http://download.doozan.com/uboot/fw_printenv
--2015-03-05 14:49:08-- http://download.doozan.com/uboot/fw_printenv
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 668497 (653K) []
Saving to: `fw_printenv'
100%[========================================================>] 668,497 1.25M/s in 0.5s
2015-03-05 14:49:09 (1.25 MB/s) - `fw_printenv' saved [668497/668497]
root@new-host-2:/boot# wget http://download.doozan.com/uboot/fw_env.config
--2015-03-05 14:49:18-- http://download.doozan.com/uboot/fw_env.config
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 329 []
Saving to: `fw_env.config'
100%[========================================================>] 329 --.-K/s in 0s
2015-03-05 14:49:18 (3.95 MB/s) - `fw_env.config' saved [329/329]
root@new-host-2:/boot# wget http://download.doozan.com/uboot/files/environment/uboot.environment
--2015-03-05 14:49:27-- http://download.doozan.com/uboot/files/environment/uboot.environment
Resolving download.doozan.com (download.doozan.com)... 50.116.34.13
Connecting to download.doozan.com (download.doozan.com)|50.116.34.13|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 131072 (128K) []
Saving to: `uboot.environment'
100%[========================================================>] 131,072 381K/s in 0.3s
2015-03-05 14:49:28 (381 KB/s) - `uboot.environment' saved [131072/131072]root@new-host-2:/boot# chmod a+x flash*
root@new-host-2:/boot# chmod a+x fw_printenv
root@new-host-2:/boot# chmod a+x nand*
root@new-host-2:/boot# ./flash_erase /dev/mtd0 0x0 6
Erase Total 6 Units
Performing Flash Erase of length 131072 at offset 0xa0000 done
root@new-host-2:/boot# ./nandwrite /dev/mtd0 uboot.spl.2013.10.ox820.850mhz.mtd0.img
Writing data to block 0 at offset 0x0
root@new-host-2:/boot# ./nandwrite -s 262144 /dev/mtd0 uboot.2013.10-tld-4.ox820.mtd0.img
Writing data to block 2 at offset 0x40000
Writing data to block 3 at offset 0x60000
Writing data to block 4 at offset 0x80000
Writing data to block 5 at offset 0xa0000
root@new-host-2:/boot# ./flash_erase /dev/mtd0 0x00100000 1
Erase Total 1 Units
Performing Flash Erase of length 131072 at offset 0x100000
MTD Erase failure: Input/output error
root@new-host-2:/boot# ./nandwrite -s 1048576 /dev/mtd0 pogopro_uboot_env.img
Writing data to block 8 at offset 0x100000
Bad block at 100000, 1 block(s) from 100000 will be skipped
Writing data to block 9 at offset 0x120000
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) March 05, 2015 06:03PM |
Registered: 9 years ago Posts: 429 |
I loaded the latest u-boot and created uEnv.txt in /boot and IT WORKED ! :)
Here is what I put in uEnv.txt for a sample. I have to clean it up because it's not complete or comprehensive but it did work:
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
autoload=no
baudrate=115200
bootcmd=run dt_bootcmd_usb
bootdelay=3
console=console=ttyS0,115200n8
dt_bootcmd_ide=ide start; run dt_ide_bootcmd; ide stop; reset
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_ide_boot=run dt_ide_load_uimage; run dt_ide_load_initrd; run dt_ide_load_dtb; run dt_bootm
dt_ide_bootcmd=run ide_set_bootargs; run dt_ide_boot
dt_ide_load_dtb=ext2load ide 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
dt_ide_load_initrd=ext2load ide 0:1 $uinitrd_addr /boot/uInitrd
dt_ide_load_uimage=ext2load ide 0:1 $uimage_addr /boot/uImage
dt_load_dtb=ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
ethact=mii0
ethaddr=INSERT_YOUR_ETHADDRESS_HERE
ide_set_bootargs=setenv bootargs root=/dev/sda2 rootfstype=ext3 console=ttyS0,115200 mem=128M 'if_netconsole' ping $serverip
ipaddr=192.168.1.100
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
preboot_nc=run if_netconsole start_netconsole
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version stderr=serial
stdin=serial
stdout=serial
uimage_addr=0x60500000
uinitrd_addr=0x60e00000
dtb_addr=0x62c00000
usb_device=0:1
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
Here is what I put in uEnv.txt for a sample. I have to clean it up because it's not complete or comprehensive but it did work:
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
autoload=no
baudrate=115200
bootcmd=run dt_bootcmd_usb
bootdelay=3
console=console=ttyS0,115200n8
dt_bootcmd_ide=ide start; run dt_ide_bootcmd; ide stop; reset
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_addr
dt_ide_boot=run dt_ide_load_uimage; run dt_ide_load_initrd; run dt_ide_load_dtb; run dt_bootm
dt_ide_bootcmd=run ide_set_bootargs; run dt_ide_boot
dt_ide_load_dtb=ext2load ide 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
dt_ide_load_initrd=ext2load ide 0:1 $uinitrd_addr /boot/uInitrd
dt_ide_load_uimage=ext2load ide 0:1 $uimage_addr /boot/uImage
dt_load_dtb=ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-pro.dtb
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage
dt_usb_boot=run dt_load_uimage; run dt_load_initrd; run dt_load_dtb; run dt_bootm
dt_usb_bootcmd=run usb_set_bootargs; run dt_usb_boot
ethact=mii0
ethaddr=INSERT_YOUR_ETHADDRESS_HERE
ide_set_bootargs=setenv bootargs root=/dev/sda2 rootfstype=ext3 console=ttyS0,115200 mem=128M 'if_netconsole' ping $serverip
ipaddr=192.168.1.100
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
preboot_nc=run if_netconsole start_netconsole
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version stderr=serial
stdin=serial
stdout=serial
uimage_addr=0x60500000
uinitrd_addr=0x60e00000
dtb_addr=0x62c00000
usb_device=0:1
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootdelay=10
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) March 05, 2015 07:03PM |
Admin Registered: 13 years ago Posts: 18,997 |
LeggoMyEggo,
> I loaded the latest u-boot and created uEnv.txt in
> /boot and IT WORKED ! :)
Cool :)
> bootcmd=run dt_bootcmd_usb
I don't think it is needed, or will take effect at all, since the uEnv.txt is loaded as part of the default bootcmd (but it does not hurt anything).
To verify the sequence, boot with serial console, interrupt it, and then do
This will show the default envs from u-boot internals. And that are used, because the env NAND block is bad.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I loaded the latest u-boot and created uEnv.txt in
> /boot and IT WORKED ! :)
Cool :)
> bootcmd=run dt_bootcmd_usb
I don't think it is needed, or will take effect at all, since the uEnv.txt is loaded as part of the default bootcmd (but it does not hurt anything).
To verify the sequence, boot with serial console, interrupt it, and then do
printenv
This will show the default envs from u-boot internals. And that are used, because the env NAND block is bad.
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) March 07, 2015 05:51PM |
Registered: 9 years ago Posts: 429 |
bodhi Wrote:
-------------------------------------------------------
> LeggoMyEggo,
>
> > I loaded the latest u-boot and created uEnv.txt
> in
> > /boot and IT WORKED ! :)
>
> Cool :)
>
> > bootcmd=run dt_bootcmd_usb
>
> I don't think it is needed, or will take effect at
> all, since the uEnv.txt is loaded as part of the
> default bootcmd (but it does not hurt anything).
>
> To verify the sequence, boot with serial console,
> interrupt it, and then do
>
> This will show the default envs from u-boot
> internals. And that are used, because the env NAND
> block is bad.
bodhi,
I am having trouble booting using uEnv.txt in /boot while attempting unsupervised (i.e. no serial console) from a cold start. Am I mistaken in thinking the new u-boot automatically loads the uEnv.txt file and does a "saveenv" before going any further? That is, as long as I have a proper uEnv.txt in /boot that I can I boot this Pro (with the bad nand blocks where boot.env's are stored) without having to do anything else? If bootcmd that is performed is whatever the default in u-boot is, what are the contents of the bootcmd command ran by the new u-boot? If it would be easier to post a sample uEnv.txt contents then I could follow that as well.
LME
Edited 2 time(s). Last edit at 03/07/2015 05:54PM by LeggoMyEggo.
-------------------------------------------------------
> LeggoMyEggo,
>
> > I loaded the latest u-boot and created uEnv.txt
> in
> > /boot and IT WORKED ! :)
>
> Cool :)
>
> > bootcmd=run dt_bootcmd_usb
>
> I don't think it is needed, or will take effect at
> all, since the uEnv.txt is loaded as part of the
> default bootcmd (but it does not hurt anything).
>
> To verify the sequence, boot with serial console,
> interrupt it, and then do
>
> printenv >>
> This will show the default envs from u-boot
> internals. And that are used, because the env NAND
> block is bad.
bodhi,
I am having trouble booting using uEnv.txt in /boot while attempting unsupervised (i.e. no serial console) from a cold start. Am I mistaken in thinking the new u-boot automatically loads the uEnv.txt file and does a "saveenv" before going any further? That is, as long as I have a proper uEnv.txt in /boot that I can I boot this Pro (with the bad nand blocks where boot.env's are stored) without having to do anything else? If bootcmd that is performed is whatever the default in u-boot is, what are the contents of the bootcmd command ran by the new u-boot? If it would be easier to post a sample uEnv.txt contents then I could follow that as well.
LME
Edited 2 time(s). Last edit at 03/07/2015 05:54PM by LeggoMyEggo.
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) March 07, 2015 06:19PM |
Admin Registered: 13 years ago Posts: 18,997 |
@LeggoMyEggo,
> I am having trouble booting using uEnv.txt in
> /boot while attempting unsupervised (i.e. no
> serial console) from a cold start. Am I mistaken
> in thinking the new u-boot automatically loads the
> uEnv.txt file and does a "saveenv" before going
> any further?
Sorry LME, I've have misses a file version in the build :) that's why you can only run it in serial console currently. This only applies to your case where the NAND block is bad. For others, they can save the envs so it will work the next boot, without doing anything extra.
In your case, you can't save the envs at all because the NAND block is bad, so you will have to rely on the default envs internally defined by u-boot. The default bootcmd env must include the loading script to load the uEnv.txt file automatically as described in the 1st post.
So stay tune, I will rebuild and release another version :) In the mean time, you have to manually start your box like you are doing. Thanks for testing!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
> I am having trouble booting using uEnv.txt in
> /boot while attempting unsupervised (i.e. no
> serial console) from a cold start. Am I mistaken
> in thinking the new u-boot automatically loads the
> uEnv.txt file and does a "saveenv" before going
> any further?
Sorry LME, I've have misses a file version in the build :) that's why you can only run it in serial console currently. This only applies to your case where the NAND block is bad. For others, they can save the envs so it will work the next boot, without doing anything extra.
In your case, you can't save the envs at all because the NAND block is bad, so you will have to rely on the default envs internally defined by u-boot. The default bootcmd env must include the loading script to load the uEnv.txt file automatically as described in the 1st post.
So stay tune, I will rebuild and release another version :) In the mean time, you have to manually start your box like you are doing. Thanks for testing!
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) March 07, 2015 07:45PM |
Registered: 9 years ago Posts: 429 |
bodhi Wrote:
-------------------------------------------------------
> In your case, you can't save the envs at all
> because the NAND block is bad, so you will have to
> rely on the default envs internally defined by
> u-boot. The default bootcmd env must include the
> loading script to load the uEnv.txt file
> automatically as described in the 1st post.
Well that makes sense. When I do a printenv at the OX820 prompt my originally loaded bootcmd= is followed by giberish because that part of the nand boot envs is corrupted. I can setenv a new bootcmd but I can't saveenv it so in order to boot from the OX820 prompt I have to use bootm. So with a corrupted bootcmd, no matter what I change the other nand boot env's to be - and if they can be saved at all without corruption - it doesn't matter because my nand bootcmd is messed up. I guess at this point the only way I could do an unsupervised boot is via the specially prepared sata disk with stage 1 boot files referenced earlier in the thread. Hey its something.
I know I should give up on this thing. At least I'm learning :)
Edited 1 time(s). Last edit at 03/07/2015 07:47PM by LeggoMyEggo.
-------------------------------------------------------
> In your case, you can't save the envs at all
> because the NAND block is bad, so you will have to
> rely on the default envs internally defined by
> u-boot. The default bootcmd env must include the
> loading script to load the uEnv.txt file
> automatically as described in the 1st post.
Well that makes sense. When I do a printenv at the OX820 prompt my originally loaded bootcmd= is followed by giberish because that part of the nand boot envs is corrupted. I can setenv a new bootcmd but I can't saveenv it so in order to boot from the OX820 prompt I have to use bootm. So with a corrupted bootcmd, no matter what I change the other nand boot env's to be - and if they can be saved at all without corruption - it doesn't matter because my nand bootcmd is messed up. I guess at this point the only way I could do an unsupervised boot is via the specially prepared sata disk with stage 1 boot files referenced earlier in the thread. Hey its something.
I know I should give up on this thing. At least I'm learning :)
Edited 1 time(s). Last edit at 03/07/2015 07:47PM by LeggoMyEggo.
|
Re: 2013.10 U-Boot for Pogoplug V3 (OXNAS) March 07, 2015 08:52PM |
Admin Registered: 13 years ago Posts: 18,997 |
LeggoMyEggo Wrote:
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > In your case, you can't save the envs at all
> > because the NAND block is bad, so you will have
> to
> > rely on the default envs internally defined by
> > u-boot. The default bootcmd env must include
> the
> > loading script to load the uEnv.txt file
> > automatically as described in the 1st post.
>
> Well that makes sense. When I do a printenv at
> the OX820 prompt my originally loaded bootcmd= is
> followed by giberish because that part of the nand
> boot envs is corrupted. I can setenv a new
> bootcmd but I can't saveenv it so in order to boot
> from the OX820 prompt I have to use bootm. So
> with a corrupted bootcmd, no matter what I change
> the other nand boot env's to be - and if they can
> be saved at all without corruption - it doesn't
> matter because my nand bootcmd is messed up. I
> guess at this point the only way I could do an
> unsupervised boot is via the specially prepared
> sata disk with stage 1 boot files referenced
> earlier in the thread. Hey its something.
>
> I know I should give up on this thing. At least
> I'm learning :)
Why giving up? It's part of the hacking experience. NAND blocks are bound to be bad on these cheap plugs. Example: about half of my plugs have bad blocks. You're just unlucky that it's bad at the block where it counts:)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
-------------------------------------------------------
> bodhi Wrote:
> --------------------------------------------------
> -----
> > In your case, you can't save the envs at all
> > because the NAND block is bad, so you will have
> to
> > rely on the default envs internally defined by
> > u-boot. The default bootcmd env must include
> the
> > loading script to load the uEnv.txt file
> > automatically as described in the 1st post.
>
> Well that makes sense. When I do a printenv at
> the OX820 prompt my originally loaded bootcmd= is
> followed by giberish because that part of the nand
> boot envs is corrupted. I can setenv a new
> bootcmd but I can't saveenv it so in order to boot
> from the OX820 prompt I have to use bootm. So
> with a corrupted bootcmd, no matter what I change
> the other nand boot env's to be - and if they can
> be saved at all without corruption - it doesn't
> matter because my nand bootcmd is messed up. I
> guess at this point the only way I could do an
> unsupervised boot is via the specially prepared
> sata disk with stage 1 boot files referenced
> earlier in the thread. Hey its something.
>
> I know I should give up on this thing. At least
> I'm learning :)
Why giving up? It's part of the hacking experience. NAND blocks are bound to be bad on these cheap plugs. Example: about half of my plugs have bad blocks. You're just unlucky that it's bad at the block where it counts:)
-bodhi
===========================
Forum Wiki
bodhi's corner (buy bodhi a beer)
Sorry, you can't reply to this topic. It has been closed.