Quantcast
Viewing all 902 articles
Browse latest View live
↧

Bad block on Goflex net Nand (1 reply)

August 22, 2016, 4:45 pm
$
0
0
Hello,
I want to install Openwrt in my Goflex Net, I check Uboot with Kwboot-tool and this is the output:


U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net

SoC: Kirkwood 88F6281_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 1 USB Device(s) found
scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: ide_preinit failed

no USB devices available

IDE device 0 not available
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command
ERROR: can't get kernel image!
resetting ...


U-Boot 1.1.4 Cloud Engines 1.1.2 (3.4.22) SATA PHYADDR=0

U-Boot code: 00600000 -> 0067FFF0 BSS: -> 00691750

Soc: 88F6281 A1 (DDR2)
CPU running @ 1200Mhz L2 running @ 400Mhz
SysClock = 400Mhz , TClock = 200Mhz

DRAM CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000 size 128MB
DRAM Total size 128MB 16bit width
Addresses 8M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (8M - 7M): Done
NAND:256 MB
Flash: 0 kB

CPU : Marvell Feroceon (Rev 1)
CLOUD ENGINES BOARD: DISCOVERY:0.1

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: interface detected no Link.
Net: egiga0 [PRIME]
Hit any key to stop autoboot: 0

NAND read: device 0 offset 0x100000, size 0x300000

Is it all ok or there are any problem?

Then I check the Nand block memory and I have this answer:

-sh-3.2# dmesg | grep -i bad
[ 1.080000] Scanning device for bad blocks
[ 1.140000] Bad eraseblock 1431 at 0x0b2e0000

Can I proceed with the boot upgrade or is there a serious problem ?

Thank you, and sorry for my bad English
↧
Search

issues when booting something different from Debian uImages (12 replies)

September 4, 2016, 1:03 am
$
0
0
I'm doing some testing on a possible new recovery firmware based off LEDE (OpenWrt fork), but booting anything that isn't a Debian uImage gives weird results.

I suspect that there is something wrong in my images, but any opinion on it is welcome.

I build kirkwood generic target from source, and I took the zimage and appended the dtb as stated (different names to suit my case)

EDIT: I checked with ghex (a hex editor), the zimage I'm using does NOT have a dtb appended. Images I build show the text from the dtb at the end of the uImage or zImage. 

cp -a zImage-3.17.0-kirkwood-tld-1  zImage.fdt
cat dts/kirkwood-goflexnet.dtb  >> zImage.fdt
mv uImage uImage.orig
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-3.17.0-kirkwood-tld-1 -d /media/sdb1/boot/zImage.fdt /media/sdb1/boot/uImage
sync

But when I try booting it (either from NAND or from a usb thumbdrive)
with this bootcmd (or with fatload instead of nand read) 
bootcmd_recovery=run recovery_bootargs; nand read 0x8000 nand0,7 ; bootm 0x8000

I get this 

NAND read: device 0 offset 0x4640000, size 0xa00000
 10485760 bytes read: OK
## Booting kernel from Legacy Image at 00008000 ...
   Image Name:   Recovery-nsa310b-lmsensor-redusb
   Created:      2016-08-29  21:58:22 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1873248 Bytes = 1.8 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK

Starting kernel ...

This means the Uboot detects a valid uImage and checksums match, but something fails when starting it.

Anything shown after that (if it worked at all) would have come first from the uImage's onboard kernel decompression tool, and then from kernel itself.

For example if I try to start stock kernel image i get also a "decompressing image ..............................................................................................(and so on).............done, booting" before it hangs, so the uImage's decompressor works even if the kernel fails afterwards.

Same thing as above happens with trying to boot a zimage with the dtb appended 

NSA310> fatload usb 0 0x8000 zimage-kirkwood-nsa310b-lmsensor-redusbled 
reading zimage-kirkwood-nsa310b-lmsensor-redusbled
1873248 bytes read in 85 ms (21 MiB/s)
NSA310> bootz 0x8000
Kernel image @ 0x008000 [ 0x000000 - 0x1c6408 ]

Starting kernel ...

For the sake of doing it (as it usually works too) I used also the "go" command instead of bootm/z 

NSA310> fatload usb 0 0x8000 uimage-kirkwood-nsa310b-lmsensor-redusbled
reading uimage-kirkwood-nsa310b-lmsensor-redusbled
1873312 bytes read in 91 ms (19.6 MiB/s)
NSA310> go 0x8000
## Starting application at 0x00008000 ...

And it hangs there.

But it does not end here. I tried also with other uImages+appended-dtb generated by LEDE build system. 

NSA310> fatload usb 0 0x8000 lede-kirkwood-dockstar-uimage
reading lede-kirkwood-dockstar-uimage
1871076 bytes read in 89 ms (20 MiB/s)
NSA310> bootm 0x8000
Wrong Image Format for bootm command
Error occured, error code = 112
ERROR: can't get kernel image!
lolwtf?
That's called "uImage" but cannot start with a bootm? Wat?

But the plot thickens, I also try bootz on the same thing 
NSA310> bootz 0x8000
Kernel image @ 0x008000 [ 0x000000 - 0x1c6408 ]

Starting kernel ...

[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Linux version 4.4.19 (alby@openSUSE-xeon) (gcc version 5.4.0 (LEDE GCC 5.4.0 r1435) ) #0 Tue Aug 23 22:21:34 2016
[    0.000000] CPU: Feroceon 88FR131 [56251311] revision 1 (ARMv5TE), cr=0005397f
[    0.000000] CPU: VIVT data cache, VIVT instruction cache
[    0.000000] Machine model: Seagate FreeAgent Dockstar

## and goes on and on for a while until it finally figures out something is wrong as this isn't a Dockstar, panics and reboots.

So, with bootz it starts it. Also tried with "go" command and it starts it too.

What happens if I try to bootz my own uImages? 

NSA310> fatload usb 0 0x8000 uimage-kirkwood-nsa310b-lmsensor-redusbled
reading uimage-kirkwood-nsa310b-lmsensor-redusbled
1873312 bytes read in 91 ms (19.6 MiB/s)
NSA310> bootz 0x8000
Bad Linux ARM zImage magic!
No. Still not like it.

Also tried to change memory address for loading and starting, same results.

ARGHHHH :(

I'm now going to try out other things like making the images from Debian, in the box (as currently I'm making them with the mkimage of OpenSUSE, since I'm using OpenSUSE), or trying to see where the damn LEDE buildsystem assembles the images and mimic it (and/or use its own tool to do it, as the build system builds also the whole toolchain from source), so I can at least get a uImage that boots with bootz for lulz but at least boots.

EDIT: for those interested, these are the images I'm using (if it gives a 404 error retry later, it's probably still uploading) https://dl.dropboxusercontent.com/u/47541136/linux/tools_for_Kirkwood_installer/uImages_to_test.tar.bz2
↧
↧

Boot stock firmware while no USB/IDE present for Pogoplug V3 OXNAS (4 replies)

September 1, 2016, 12:28 am
$
0
0
Hi,

I tried to modify the Uboot env settings to try to boot from USB or IDE first,
if both are not present, then boot from the internal flash/stock firmware. 
bootcmd=run bootcmd_uenv; run dt_bootcmd_usb; run bootcmd_stock; reset


the complete system configration: 

Stock Pogoplug OS:

 U-Boot (1.1.2 Jul 29 2010)

cat /proc/mtd0

mtd0: 08000000 00020000 "NAND 128MiB 3,3V 8-bit"
mtd1: 00e00000 00020000 "boot"
mtd2: 07200000 00020000 "rootfs

U-boot 2013.10 install per instructions here
http://forum.doozan.com/read.php?3,16017,page=1

The new Uboot env settings:
root@debian:/# fw_printenv
autoload=no
baudrate=115200
bootargs=console=ttyS0,115200n8
bootdelay=10
console=console=ttyS0,115200n8
ethact=mii0
mtdids=nand0=41000000.nand
mtdparts=mtdparts=41000000.nand:14m(boot),-(data)
stderr=serial
stdin=serial
stdout=serial
usb_device=0:1
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version
uinitrd_addr=0x60e00000
uimage_addr=0x60500000
dtb_addr=0x62c00000
dt_load_initrd=ext2load usb 0:1 $uinitrd_addr /boot/uInitrd
dt_load_uimage=ext2load usb 0:1 $uimage_addr /boot/uImage
dt_bootm=bootm $uimage_addr $uinitrd_addr $dtb_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
dt_bootcmd_usb=usb start; run dt_usb_bootcmd; usb stop; reset
ipaddr=192.168.1.3
serverip=192.168.1.10
ethaddr=00:25:XX:XX:XX:XX
devices=usb ide
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
uenv_import=echo importing envs ...; env import -t 0x60500000
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 0x60500000 /boot/uEnv.txt; then setenv uenv_loaded 1; fi
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
dt_load_dtb=ext2load usb 0:1 $dtb_addr /boot/dts/ox820-pogoplug-classic.dtb
rootfstype=ext3
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=/dev/sda1 rootfstype=$rootfstype rootdelay=10
bootcmd=run bootcmd_uenv; run dt_bootcmd_usb; run bootcmd_stock; reset
bootcmd_stock=setenv autoload n; setenv bootargs_stock "root=ubi0:rootfs ubi.mtd=2,512 rootfstype=ubifs console=ttyS0,115200 elevator=cfq mac_adr=0x00,0x25,0x31,0x02,0x5E,0x91 mem=128M"; setenv poweroutage yes; setenv boot "bootm 60500000"; setenv bootcmd_stock_fw "run set_bootargs_stock; run boot_nand"; setenv boot bootm 60500000; setenv boot_nand "run load_nand boot || run load_nand2 boot"; setenv kernflmode s; setenv load_nand2 "nboot 60500000 0 800000"; setenv load_nand "nboot 60500000 0 200000"; setenv set_bootargs_stock "setenv bootargs $bootargs_stock"; setenv mainlinelinux no; run bootcmd_stock_fw
preboot=run preboot_nc
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi


rootfs:Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2 (02 Nov 2014)

however while no usb/ide present, it will try to reboot instead of boot the internal stock firmware: 

U-Boot 2013.10-tld-4 (Sep 08 2014 - 19:43:38) for OXNAS
gcc (Debian 4.6.3-14) 4.6.3
GNU ld (GNU Binutils for Debian) 2.22
Hit any key to stop autoboot:  0
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found

Reset IDE: SATA PHY not ready for device 0
ide_preinit failed

no USB devices available

no IDE devices available
(Re)start USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices... 0 Storage Device(s) found
** Bad device usb 0 **
** Bad device usb 0 **
** Bad device usb 0 **
Wrong Image Format for bootm command

Led:    ORANGE (Failed)
ERROR: can't get kernel image!
stopping USB..
resetting ...

I can stop the booting process and have it boot to stock firmware via running
run bootcmd_stock

what should I change here to have it auto boot the stock firmware if no usb/ide present?

Thanks in adavance
↧

Help on getting u-boot replacement on stock Buffalo LS-WVL (2 replies)

September 5, 2016, 1:13 am
$
0
0
Hi All,

I have managed to get serial working on my buffalo LS-WVL and here attached is the stock u-boot log. Is there a replacement u-boot that I can try with this device?
↧

Help on getting u-boot replacement on stock Buffalo LS421DE (3 replies)

September 6, 2016, 1:58 pm
$
0
0
I am starting this new thread as I also have a Buffalo LS421DE. I got serial working and here is the boot log:

BootROM 1.08
Booting from SPI flash
DDR3 Training Sequence - Ver 2.3.5
DDR3 Training Sequence - Ended Successfully
BootROM: Image checksum verification PASSED

=========================
==== Welcome to YANAGI ==
=========================

** LOADER **


U-Boot 2009.08 ( 8月 28 2013 - 21:36:20)Marvell version: 1.1.3 NQ
U-Boot Addressing:
Code: 00600000:006AFFF0
BSS: 006F8360
Stack: 0x5fff70
PageTable: 0x8e0000
Heap address: 0x900000:0xe00000
BUFFALO_BOOTVER=0.13
Board: Buffalo LS-M 88f6710
SoC: MV6710 A1
CPU: Marvell PJ4B v7 UP (Rev 1) LE
CPU @ 1200Mhz, L2 @ 600Mhz
DDR @ 600Mhz, TClock @ 200Mhz
DDR 16Bit Width, FastPath Memory Access
PEX 0: Root Complex Interface, Detected Link X1
PEX 1: Detected No Link.
DRAM: 512 MB
CS 0: base 0x00000000 size 512 MB
Addresses 14M - 0M are saved for the U-Boot usage.
SF: Detected MX25L8006E with page size 256, total 1048576 bytes
NAND: 512 MiB
u-boot envinit tval=e4b4c857
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Shutting down unused interfaces:
AUDIO
TDM
Modules/Interfaces Detected:
SDIO
RGMII0 Phy
RGMII1 Phy
PEX0 (Lane 0)
PEX1 (Lane 1)
SATA0 (Lane 2)
SATA1 (Lane 3)

Marvell Serial ATA Adapter
Integrated Sata device found

MAC Address : 10:6F:3F:xx:xx:xx
MMC: MRVL_MMC: 0
Net: egiga0, egiga1 [PRIME]
hit any key to switch tftp boot.
Hit any key to stop autoboot: 0
switched to TFTP boot.
Hit any key to stop autoboot: 0
BUFFALO>>
↧
↧

Help with Pogoplug v4 – blinks green for ten seconds and reboots in a loop (1 reply)

September 7, 2016, 4:40 pm
$
0
0
Bodhi and everyone else here: you've done some amazing work. I wanted to honor that and not end up needing help but...

I started to flash my Pogoplug v4-A3-01 years ago with some tutorial but abandoned the project. I started it again recently and found that I could boot into Arch with root:root. I tried picking up Qui Hong's tutorial but his links are down, so I tried a combination of that and Bodhi's 2016.05 tutorial. When I rebooted (the "cross your fingers" part), it no longer boots into the USB drive I was using or the SD card, which I formatted in the tutorial (with both or either inserted). I removed the power cord to power cycle and the status light immediately blinks/flashes green for about ten seconds then goes dark for a second or two and begins the cycle again. (I assume that it's restarting during that pause.) Just as it goes dark, the ethernet jack briefly lights both orange and green. I formatted another SD card with the Debian-4.4 in case it was a file system issue and had the same result (also that wouldn't explain why the unmodified USB drive used for the original flash no longer registers). When I formatted this SD card, it was formerly FAT 32 and while its partition is ext3, the `pttype="dos"` instead of "gpt" when I run blkid—not sure if that's an issue. The device doesn't go solid green so I can't SSH and netconnect is not installed. Would you know whether this is a bad flash or what I might need to do to restart and try over?

Appreciate your help. I'd be willing to rewrite the Qui tutorial with your updated materials so that future installs can go more smoothly. I still have another Pogoplug Mobile I'd like to try, but hopefully I can get this v4 up if it isn't bricked.
↧

Help with Pogoplug v4 - Unable to SSH in (3 replies)

September 10, 2016, 1:54 pm
$
0
0
I'm having issues enabling SSH on my Pogoplug v4. The web interface on the Pogoplug site does not show the option no matter how many times I delete and register the device. I have also tried running the following curl script:

curl -k "https://root:ceadmin@[PogoplugIPAddress]/sqdiag/HBPlug?action=command&command=dropbear%20start";

This device refuses the connection. I'm new to Linux and am not sure if I just need to modify the command or approach this a different way.
↧

SysClock vs TClock (3 replies)

September 13, 2016, 1:44 pm
$
0
0
Sorry to be a noob but can you guys shed some light on what SysClock = 533Mhz , TClock = 200Mhz means?

Is SysClock the actual speed of the ram? What is TClock?
↧
Search

Tips for adding support to latest uBoot when I have 1.1.1 level source (6 replies)

September 20, 2016, 8:01 pm
$
0
0
I have source code to an ancient uBoot version 1.1.1 I'd like to port this to the latest uboot, but I have no idea where to start and documentation on the uBoot site appears to be seriously out of date. I am an experienced C developer (over 20 years experience) and was a contributor to Linux back when m68k Macs were still a viable platform. I'd just like some pointers as I have not been able to decipher the structure of uboot (i.e. where to begin adding support).

Ray
↧
↧

Problem installing U-Boot and kernel for Pogoplug V3 (OXNAS OX820) (25 replies)

September 23, 2016, 9:00 am
$
0
0
Hey all.

Followed the instructions at http://blog.qnology.com/2015/04/hacking-pogoplug-v3oxnas-proclassic.html to try to flash uboot and boot debian from a usb. I used:

Debian-3.17.0-oxnas-tld-1-rootfs-bodhi.tar.bz2
uboot.2013.10-tld-3.ox820.bodhi.tar.gz

Everything more or less seems to have gone allright except I cannot actually boot with uboot, getting the following from terminal starting at the main loop after autoboot:

(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
** No partition table - usb 0 **
** No partition table - usb 0 **
** No partition table - usb 0 **
Wrong Image Format for bootm command

Led: ORANGE (Failed)
ERROR: can't get kernel image!
stopping USB..
resetting...

This makes me think that either I made a mistake in installing u-boot, the debian/uboot versions I took off the forum are the wrong ones or incompatible, or I simply screwed up formatting and moving the debian tar.bz2 to the USB from my raspberry pi. Any help with figuring out where I went wrong would be greatly appreciated :)
↧

Booting from USB Problems (3 replies)

September 28, 2016, 3:54 pm
$
0
0
I cant boot Goflex Net from USB.
It stop with the following output error:

U-Boot 2011.12 (Apr 18 2012 - 23:08:20)
Seagate GoFlexNet

SoC: Kirkwood 88F6281_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 3 ### 2 ### 1 ### 0
(Re)start USB...
................... omissis.....................

Found bootable drive on usb 0:1
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
3154896 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
7179935 bytes read
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-4.4.0-kirkwood-tld-1
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 3154832 Bytes = 3 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
Image Name: initramfs-4.4.0-kirkwood-tld-1
Image Type: ARM Linux RAMDisk Image (gzip compressed)
Data Size: 7179871 Bytes = 6.8 MiB
Load Address: 00000000
Entry Point: 00000000
Verifying Checksum ... OK
Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.


Error: unrecognized/unsupported machine ID (r1 = 0x00000831).


Available machine support:


ID (hex) NAME

ffffffff Generic DT based system

ffffffff Marvell Kirkwood (Flattened Device Tree)


Please check your kernel config and/or bootloader.

What is wrong.
Many thanks for help
↧

Trouble booting and SSH into USB (Arch linux) with Pogo E02 (5 replies)

October 3, 2016, 8:43 am
$
0
0
Booting and SSH-ing issues into Arch Linux in POGO....

It boots into the Pogo OS fine and provides the correct IP to ssh in, but once I plug in the USB (on the top port) and do a busybox reboot, it isn't pingable or sshable anymore.
I set up a netconsole to view the boot process, and this (see below) is what I get... I also have the output of 'fw_printenv' for you to look at. I had made some changes to the original one while trying to fix it, but none have worked so far.....

When it is booted into PogoOS, I could ssh in (192.168.11.33) and see the mounted disk in /tmp/.cment/mnt_sda1...

I would be happy to provide any additional information if you need. Thanks a lot for any help... 

~ $ nc -ul 6666

U-Boot 2011.12 (Feb 20 2012 - 21:21:59)
Pogoplug E02
arm-none-linux-gnueabi-gcc (Sourcery G++ Lite 2009q3-67) 4.4.1
GNU ld (Sourcery G++ Lite 2009q3-67) 2.19.51.20090709
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/rescueme" from usb device 0:1 (usbda1)
** File not found /rescueme
reading /rescueme.txt

** Unable to read "/rescueme.txt" from usb 0:1 **
Creating 1 MTD partitions on "nand0":
0x000002500000-0x000008000000 : "mtd=3"
UBI: attaching mtd1 to ubi0
UBI: physical eraseblock size:   131072 bytes (128 KiB)
UBI: logical eraseblock size:    129024 bytes
UBI: smallest flash I/O unit:    2048
UBI: sub-page size:              512
UBI: VID header offset:          512 (aligned 512)
UBI: data offset:                2048
UBI: attached mtd1 to ubi0
UBI: MTD device name:            "mtd=3"
UBI: MTD device size:            91 MiB
UBI: number of good PEBs:        726
UBI: number of bad PEBs:         2
UBI: max. allowed volumes:       128
UBI: wear-leveling threshold:    4096
UBI: number of internal volumes: 1
UBI: number of user volumes:     0
UBI: available PEBs:             715
UBI: total number of reserved PEBs: 11
UBI: number of PEBs reserved for bad PEB handling: 7
UBI: max/mean erase counter: 1/1
UBIFS error (pid 0): ubifs_get_sb: cannot open "ubi:rootfs", error -19
Error reading superblock on volume 'ubi:rootfs'!
(Re)start USB...
USB:   Register 10011 NbrPorts 1
USB EHCI 1.00
scanning bus for devices... 3 USB Device(s) found
       scanning bus for storage devices... 1 Storage Device(s) found
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
4028544 bytes read
Loading file "/boot/uImage" from usb device 0:1 (usbda1)
4028544 bytes read
Loading file "/boot/uInitrd" from usb device 0:1 (usbda1)
** File not found /boot/uInitrd
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.18.1-1-ARCH
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    4028480 Bytes = 3.8 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...


Output of fw_printenv 
-bash-4.3# fw_printenv               
ethact=egiga0
bootdelay=3
baudrate=115200
mainlineLinux=yes
console=ttyS0,115200
led_init=green blinking
led_exit=green off
led_error=orange blinking
mtdparts=mtdparts=orion_nand:1M(u-boot),4M(uImage),32M(rootfs),-(data)
mtdids=nand0=orion_nand
partition=nand0,2
stdin=serial
stdout=serial
stderr=serial
rescue_installed=0
rescue_set_bootargs=setenv bootargs console=$console ubi.mtd=2 root=ubi0:rootfs ro rootfstype=ubifs $mtdparts $rescue_custom_params
rescue_bootcmd=if test $rescue_installed -eq 1; then run rescue_set_bootargs; nand read.e 0x800000 0x100000 0x400000; bootm 0x800000; else run pogo_bootcmd; fi
pogo_bootcmd=if fsload uboot-original-mtd0.kwb; then go 0x800200; fi
force_rescue=0
force_rescue_bootcmd=if test $force_rescue -eq 1 || ext2load usb 0:1 0x1700000 /rescueme 1 || fatload usb 0:1 0x1700000 /rescueme.txt 1; then run rescue_bootcmd; fi
ubifs_mtd=3
ubifs_set_bootargs=setenv bootargs console=$console ubi.mtd=$ubifs_mtd root=ubi0:rootfs rootfstype=ubifs $mtdparts $ubifs_custom_params
ubifs_bootcmd=run ubifs_set_bootargs; if ubi part data && ubifsmount rootfs && ubifsload 0x800000 /boot/uImage && ubifsload 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; fi
usb_scan=usb_scan_done=0;for scan in $usb_scan_list; do run usb_scan_$scan; if test $usb_scan_done -eq 0 && ext2load usb $usb 0x800000 /boot/uImage 1; then usb_scan_done=1; echo "Found bootable drive on usb $usb"; setenv usb_device $usb; setenv usb_root /dev/$dev; fi; done
usb_scan_list=1 2 3 4
usb_scan_1=usb=0:1 dev=sda1
usb_scan_2=usb=1:1 dev=sdb1
usb_scan_3=usb=2:1 dev=sdc1
usb_scan_4=usb=3:1 dev=sdd1
usb_device=0:1
usb_root=/dev/sda1
usb_rootdelay=10
usb_set_bootargs=setenv bootargs console=$console root=$usb_root rootdelay=$usb_rootdelay rootfstype=$usb_rootfstype $mtdparts $usb_custom_params
usb_bootcmd=run usb_init; run usb_set_bootargs; run usb_boot
usb_boot=mw 0x800000 0 1; ext2load usb $usb_device 0x800000 /boot/uImage; if ext2load usb $usb_device 0x1100000 /boot/uInitrd; then bootm 0x800000 0x1100000; else bootm 0x800000; fi
bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run rescue_bootcmd; run pogo_bootcmd; reset
ethaddr=00:25:31:04:A1:A6
arcNumber=2097
usb_init=usb start; if ext2load usb 0:1 0x800000 /boot/uImage; then setenv usb_device 0:1; setenv usb_root /dev/sda1; elif ext2load usb 1:1 0x800000 /boot/uImage; then setenv usb_device 1:1; setenv usb_root /dev/sdb1; elif ext2load usb 2:1 0x800000 /boot/uImage; then setenv usb_device 2:1; setenv usb_root /dev/sdc1; elif ext2load usb 3:1 0x800000 /boot/uImage; then setenv usb_device 3:1;setenv usb_root /dev/sdd1;fi;
serverip=192.168.11.19
ipaddr=192.168.11.33
if_netconsole=ping $serverip
start_netconsole=setenv ncip $serverip; setenv bootdelay 10; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
preboot=run if_netconsole start_netconsole
usb_rootfstype=ext2
↧

bricked iconnect (3 replies)

October 3, 2016, 4:38 pm
$
0
0
Hello all,
I did read the manual of how to upgrade the UBoot from bodhi: 2016.05 U-Boot Kirkwood.
What i did not realized was the (B) section (shame on me!) and as of this i reboot the iconnect, without
flashing the env to 0xC0000.


The result is this:

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:38:04 -0700)
Iomega iConnect

SoC: Kirkwood 88F6281_A0
DRAM: 256 MiB
WARNING: Caches not enabled
NAND: 512 MiB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: egiga0
Hit any key to stop autoboot: 0
starting USB...
USB0: USB EHCI 1.00
scanning bus 0 for devices... 4 USB Device(s) found
scanning usb for storage devices... 1 Storage Device(s) found

Partition Map for USB device 0 -- Partition Type: DOS

Part Start Sector Num Sectors UUID Type
1 362496 7469056 a536a0ea-01 83
2 8192 354304 a536a0ea-02 82
loading envs from usb 0 ...
** File not found /boot/uEnv.txt **
2631368 bytes read in 363 ms (6.9 MiB/s)
** File not found /boot/uInitrd **
## Booting kernel from Legacy Image at 00800000 ...
Image Name: Linux-3.3.2-iconnect
Created: 2012-04-15 12:37:51 UTC
Image Type: ARM Linux Kernel Image (uncompressed)
Data Size: 2631304 Bytes = 2.5 MiB
Load Address: 00008000
Entry Point: 00008000
Verifying Checksum ... OK
Loading Kernel Image ... OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.

Then the iconnect just do nothing..... and the serial console won't react on keystroke.
----------

My question is now, how do i use UBoot on serial console to fix it?
The 3 Files of the default enviroment for the new UBoot I got here, as well as the old env (c).

could anyone point me in the right direction please
thank you

english is not my native language, so a lot of edits... sorry
↧
↧

No access after flashing default env img (2 replies)

October 3, 2016, 6:33 pm
$
0
0
Hi,

I flashed default uboot environment image following instructions from here http://forum.doozan.com/read.php?3,12381. (B: flashing uboot env image).
Now, I can't access the pogo-E02. It blinks rapidly. Please help.

Thanks

* EDIT
Now it has a solid green, but still no access. Neither on netconsole or ssh (well ssh was never working on the first place to let me go and do this)...
↧

Kirkwood U-Boot and Debian Installer Script - howto try? (2 replies)

October 4, 2016, 2:37 am
$
0
0
Hi

The rootfs flash drives from one of my Pogoplug E02 gave up and I think this might be the perfect time to try the new Installer script. I glanced over the thread relating to the script, but could not find any howto to test it?

Is it in a state so that I can use it?
What are the risks?
How can I use the script?

Thanks

Rainer
↧
Search

Problem booting Pogo Mobile (2 replies)

October 7, 2016, 4:46 pm
$
0
0
I own a pogoplug V4 and a mobile.
The first one runs fine since spring, so now I decided to upgrade the mobile as well as pogoplug was shutting down its services.
I installed U-Boot 2016.05 on both devices with modified default envs.
But while V4 boots fine, mobile gets stuck after loading kernel with same USB-stick, Doesn't load until IP-adress is assigned.
Tried with "dtb_file"env set and unset with same result.

Can someone give me a hint where the problem is?

fw_printenv: 
bootcmd_exec=run load_uimage; if run load_initrd; then if run load_dtb; then bootm $load_uimage_addr $load_initrd_addr $load_dtb_addr; else bootm $load_uimage_addr $load_initrd_addr; fi; else if run load_dtb; then bootm $load_uimage_addr - $load_dtb_addr; else bootm $load_uimage_addr; fi; fi
bootcmd_uenv=run uenv_load; if test $uenv_loaded -eq 1; then run uenv_import; fi
bootdev=usb
device=0:1
devices=usb ide mmc
disks=0 1 2 3
ethact=egiga0
if_netconsole=ping $serverip
led_error=orange blinking
led_exit=green off
led_init=green blinking
load_dtb_addr=0x1c00000
load_initrd_addr=0x1100000
load_uimage_addr=0x800000
load_dtb=echo loading DTB $dtb_file ...; load $bootdev $device $load_dtb_addr $dtb_file
load_initrd=echo loading uInitrd ...; load $bootdev $device $load_initrd_addr /boot/uInitrd
load_uimage=echo loading uImage ...; load $bootdev $device $load_uimage_addr /boot/uImage
mainlineLinux=yes
mtdids=nand0=orion_nand
partition=nand0,2
scan_disk=echo running scan_disk ...; scan_done=0; setenv scan_usb "usb start";  setenv scan_ide "ide reset";  setenv scan_mmc "mmc rescan"; for dev in $devices; do if test $scan_done -eq 0; then echo Scan device $dev; run scan_$dev; for disknum in $disks; do if test $scan_done -eq 0; then echo device $dev $disknum:1; if load $dev $disknum:1 $load_uimage_addr /boot/uImage 1; then scan_done=1; echo Found bootable drive on $dev $disknum; setenv device $disknum:1; setenv bootdev $dev; fi; fi; done; fi; done
set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts $custom_params
stderr=serial
stdin=serial
stdout=serial
uenv_addr=0x810000
uenv_import=echo importing envs ...; env import -t $uenv_addr $filesize
uenv_init_devices=setenv init_usb "usb start";  setenv init_ide "ide reset";  setenv init_mmc "mmc rescan"; for devtype in $devices; do run init_$devtype; done;
uenv_load=run uenv_init_devices; setenv uenv_loaded 0; for devtype in $devices;  do for disknum in 0; do run uenv_read_disk; done; done;
uenv_read_disk=if test $devtype -eq mmc; then if $devtype part; then run uenv_read;  fi; else if $devtype part $disknum; then run uenv_read; fi;  fi
uenv_read=echo loading envs from $devtype $disknum ...; if load $devtype $disknum:1 $uenv_addr /boot/uEnv.txt; then setenv uenv_loaded 1; fi
usb_ready_retry=15
ethaddr=aa:bb:cc:d:ee:ff
arcNumber=3960
machid=F78
usb_rootfstype=ext3
mtdparts=mtdparts=orion_nand:2M(u-boot),3M(uImage),3M(uImage2),8M(failsafe),112M(root)
preboot_nc=setenv nc_ready 0; for pingstat in 1 2 3 4 5; do; sleep 1; if run if_netconsole; then setenv nc_ready 1; fi; done; if test $nc_ready -eq 1; then run start_netconsole; fi
preboot=run preboot_nc
serverip=192.168.0.110
bootcmd_pogo=if ubi part root 2048 && ubifsmount ubi:rootfs && ubifsload 0x800000 uboot.mtd0.dockstar.original.kwb ; then go 0x800200; fi
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec; run bootcmd_pogo; reset
bootdelay=3
start_netconsole=setenv ncip $serverip; setenv bootdelay 3; setenv stdin nc; setenv stdout nc; setenv stderr nc; version;
dtb_file=/boot/dts/kirkwood-pogoplug_v4.dtb
ipaddr=192.168.0.106

NC output: 
U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:41:47 -0700)
Pogoplug V4
gcc (Debian 4.9.2-10) 4.9.2
GNU ld (GNU Binutils for Debian) 2.25
Hit any key to stop autoboot:  0
starting USB...
USB0:   USB EHCI 1.00
scanning bus 0 for devices... 2 USB Device(s) found
       scanning usb for storage devices...
Use USB retry period from the environment: 15 second(s)
1 Storage Device(s) found

Reset IDE: ide_preinit failed

Partition Map for USB device 0  --   Partition Type: DOS

Part    Start Sector    Num Sectors     UUID            Type
  1     2048            8017824         d5269418-01     83
loading envs from usb 0 ...
 usb
1 bytes read in 123 ms (0 Bytes/s)
Found bootable drive on usb 0
loading uImage ...
2875692 bytes read in 295 ms (9.3 MiB/s)
loading uInitrd ...
6183666 bytes read in 523 ms (11.3 MiB/s)
loading DTB /boot/dts/kirkwood-pogoplug_v4.dtb ...
10028 bytes read in 543 ms (17.6 KiB/s)
## Booting kernel from Legacy Image at 00800000 ...
   Image Name:   Linux-3.18.5-kirkwood-tld-1
   Created:      2016-05-26  23:38:38 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2875628 Bytes = 2.7 MiB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
## Loading init Ramdisk from Legacy Image at 01100000 ...
   Image Name:   initramfs-3.18.5-kirkwood-tld-1
   Created:      2016-05-26  23:38:40 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6183602 Bytes = 5.9 MiB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK
## Flattened Device Tree blob at 01c00000
   Booting using the fdt blob at 0x1c00000
↧

[SOLVED] Netgear Stora - type Control-D to continue... (3 replies)

October 12, 2016, 2:17 am
$
0
0
I've finally dusted off my old Stora and this weekend "upgraded" to Debian with the new 4.8 Kernel.

When I boot from Hard Disk I am being presented with the following output;

INIT: Entering runlevel: 1
[info] Using makefile-style concurrent boot in runlevel 1.
[ ok ] Asking all remaining processes to terminate...done.
[ ok ] All processes ended within 1 seconds....done.
[info] Will now switch to single-user mode.
INIT: Sending processes the TERM signal
INIT: Sending processes the KILL signal
Give root password for maintenance
(or type Control-D to continue):

having to type Ctrl-D in order to get it to finish booting. below is the output from printenv;

Netgear Stora> printenv
arcNumber=2743
baudrate=115200
bootargs=console=ttyS0,115200 root=/dev/sda1 bootdelay 1
bootcmd=ide reset; ext2load ide 0:1 0x800000 /boot/uImage; ext2load ide 0:1 0x1100000 /boot/uInitrd; bootargs $(console) root=LABEL=rootfs rootdelay=10; bootm 0x800000 0x1100000; reset
bootdelay=10
console=ttyS0,115200
ethact=egiga0
ethaddr=aa:bb:cc:dd:ee:ff (changed)
ipaddr=192.168.10.2
mainlineLinux=yes
rootfstype=ext2
serverip=192.168.10.1
set=bootargs_usb
stderr=serial
stdin=serial
stdout=serial
usb=start
usb_root=/dev/sda1

It should be noted that when first "built" I was booting from USB, though found it gave I/O errors at times so moved to HD

Seems that the "transition" from USB to HDD boot required additional updates / changes to the boot loader config, which now looks like this;

arcNumber=2743
baudrate=115200
bootargs=ttyS0,115200 root=LABEL=rootfs bootdelay 10
bootcmd=ide reset; ext2load ide 0:1 0x800000 /boot/uImage; ext2load ide 0:1 0x1100000 /boot/uInitrd; rootdelay=10; bootm 0x800000 0x1100000; reset
console=ttyS0,115200
ethact=egiga0
ethaddr=aa:bb:cc:dd:ee:ff (changed)
ipaddr=192.168.10.2
mainlineLinux=yes
rootfstype=ext3
serverip=192.168.10.1
stderr=serial
stdin=serial
stdout=serial
↧
↧

U-Boot - GoFlexNet environment problem (9 replies)

November 11, 2016, 3:13 pm
$
0
0
Hello,
I started uploading new U-Boat on goflex net and everything went well until I entered this command:
flash_erase / dev / mtd0 0xc0000 1
before entered the command to load the new file uboot.environment the device restart, and now I have this at boot:

U-Boot 2016.05-tld-1 (Jun 12 2016 - 13:27:19 -0700)
Seagate GoFlex Net

SoC: Kirkwood 88F6281_A1
DRAM: 128 MiB
WARNING: Caches not enabled
NAND: 256 MiB
*** Warning - bad CRC, using default environment

In: serial
Out: serial
Err: serial
Net: egiga0
88E1116 Initialized on egiga0
Hit any key to stop autoboot: 0

Have you got any idea how to fix this problem?
thank you
↧

Wiki (no replies)

November 5, 2016, 4:13 pm
↧

What is the correct "bootcmd" value for NFS with the new uBoot? (13 replies)

November 10, 2016, 11:23 pm
$
0
0
With the new uBoot, the default env var 
bootcmd=run bootcmd_uenv; run scan_disk; run set_bootargs; run bootcmd_exec

According to some tutorial about NFS boot, 
Bootcmd=usb start; run force_rescue_bootcmd; run ubifs_bootcmd; run usb_bootcmd; usb stop; run net_bootcmd; run rescue_bootcmd; run pogo_bootcmd; reset
or 
bootcmd=run bootcmd_usb; run bootcmd_mmc; run bootcmd_sata; run net_bootcmd; run bootcmd_pogo; reset

I’ve read "Booting process in multiple drives configuration", but still I have no idea how to set the bootcmd to support NFS and other devices in the load chain for the new uBoot.
↧
Viewing all 902 articles
Browse latest View live
Search