bodhi,

nope doesn't show up in my router nor in wireshark - with usb_boot

if i just let it run start (with bootcmd=tftpload...) and provide our uImage it seems to get further, because the nas appears in the router.

Namme^ip^mac
PC-10-0-0-30	10.0.0.30	00:50:43:00:02:02

Edited 2 time(s). Last edit at 03/11/2017 08:35PM by helge.

helge,

> if i just let it run start (with bootcmd=tftpload.
> ..) and provide our uImage it seems to get further
> , because the nas appears in the router.
>

> Namme^ip^mac
> PC-10-0-0-30	10.0.0.30	00:50:43:00:02:02
>

This is a very good sign! so can you ping the box with 10.0.0.30 ? do this about 2 minutes after it seems to get stuck. If it responses to ping then try to ssh in to see what is the behavior, whether it is actually running.

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

Nope there is no connectivity. But i found something near 0004f0a0 . I haven't seen this arguments in stock medion uboot nor after i did a resetenv. It's still badly formatted,because i did it manual

|_|	.image_multi.Recovery	imgage will be	treated	in	multimode..Recovery	imgage	will	be	treated	in	normal	mode..usbload.usb.0:1.loadaddr./multiware.img./flashware.img.Trying	to	load	image	from	||USB	flash	drive	||using	FAT	FS..Tr|	|ying	to	load	ima||ge	from	USB	flas||h	drive	using	ex||t2	FS	partition	||0..0:0.Trying	to|		|	load	image	from||	USB	flash	drive using	ext2FS partition1..Couldn't	load	recovery	image	from	USB	flash	drive,	T||rying	network	in|	|terface..filesiz|			|e./upgrade.me.0x|			|000000000.dummya|			|ddr:%s..Multi:%s|			|,	Upgrade:%d..us|		|b_upgrade.Aquiring	an	IP	address	using	DHCP	afte||r	settling	netwo|	|rk.....DHCP	shou|		|ld	be	ready	for|Recovery...Starting	the	Recovery process	to	retreive the image file.....Missing	loadaddr	environment	variable	as|	|suming	default	(|	|0x200000)!..0x200000.Update	
bootcmd..eth1addr setenv	bootargs	$(console)	root=/dev/ram0	$(mvNetConfig)	recovery=%s	serverip=%d.%d.%d.%d	ethact=$(ethact)	ethaddr=%s	eth1addr=%s;	bootm	$(loadaddr);..
bootcmd(recovery-image-multi):setenv	bootargs	$(console)	root=/dev/ram0	$(mvNetConfig)	rootfstype=squashfs	initrd=0x%x,0x%x	ramdisk_size=%d	recovery=%s	serverip=%d.%|d.%d.%d	ethact=$(ethact)	ethaddr=%s	eth1addr=%s;	bootm	$(loadaddr);
bootcmd(recovery-image-normal):console.console=ttyS0,115200	mtdparts=spi_flash:0x100000@0x0(uboot)ro,0x200000@0x100000(uimage),0xb80000@0x300000(rootfs),0x180000@0xe80000(varfs),0xf00000@0x100000(flash)	varfs=/dev/mtdblock3
setenv	bootargs $(console)	rootfstype=squashfs	root=/dev/mtdblock2 ;bootm	0xf8100000;
setenv	bootargs $(console)	ubi.mtd=2	root=ubi0:rootfs rootfs type=ubifs	$(mvNetConfig)	$(mvPhoneConfig) $(lcd0_bootargs);	nand read.e	$(loadaddr)	0x100000	0x300000;	bootm	$(loadaddr); console=ttyS0,115200 
setenv	bootargs $(console)	rootfs type=squashfs	root=/dev/mtdblock2	$(mvNetConfig) $(mvPhoneConfig)	$(lcd0_bootargs);	nand	read.e	$(loadaddr)	0x100000	0x200000;	bootm	$(loadaddr);%d	is	RGMII..Module	%d	is	GMII..M||odule	%d	is	TS..||Module	%d	is	MII||..Module	%d	is	L||CD..console=ttyS|			|0,115200	mtdpart|		|s=nand_mtd:0x%x@|			|0(uboot)ro,0x%x@|			|0x%x(root).nandE|			|nvBase.mainlineL|			|inux.arcNumber.p|			|exMode.EP.ep.sat|			|a_dma_mode.MALLOC_len.ethprime.egiga1.egiga0.net|			
|bsd_en.netbsd_gw||.192.168.0.254 netbsd_mask=255.255.255.0 netbsd_fs=nfs netbsd_server=192.168.0.1 netbsd_ip=$(ipaddr) netbsd_rootdev.mgi0.netbsd_add.0x800000. netbsd_get.tftpboot	$(|		|netbsd_add)	$(im|		|age_name).netbsd|			|_set_args.setenv|			|	bootargs	nfsroo|	|t=$(netbsd_serve|			|r):$(rootpath)	fs=$(netbsd_fs)	ip=$(netbsd_ip)	serverip=$(netbsd_server)	mask=$(netbsd_mask)	gw=$(netbsd_gw)	rootdev=$(netbsd_rootdev)	ethaddr=$(ethaddr)	eth1addr=$(eth1addr)	ethmtu=$(ethmtu) eth1mtu=$(eth1mtu)	$(netbsd_netconfig).bootm	$(netbsd_add)	$(bootargs).netbsd_bootcmd.run	netbsd_get	;	run	netbsd_set_args	;	run	netbsd_boot. vxworks_en.mgi(0,0)|			|	host:vxWorks.st.serverip.	h=.	e|	|=.:ffff0000	u=anonymous	pw=target	.vxWorks_bootargs.bootargs_root.root=/dev/nfs rw.bootargs_end.|			|:::orion:eth0:no|			|ne.:::DB88FXX81:|			|eth0:none.image_|			|name.uImage.tftp|			|boot	0x2000000	$|	|(image_name);	se|		|tenv	bootargs	$(|	|console)	$(boota|		|rgs_root)	nfsroo|		|t=$(serverip):$(rootpath)	ip=$(ipaddr):$(serverip)$(bootargs_end)	$(mvNetConfig)	$(mvPhoneConfig)	video=dovefb:lcd0:$(lcd0_params)	clcd.lcd0_enable=$(lcd0_enable);	bootm	0x2000000;	.standalone.fsload	0x2000000	$(image_name);setenv	bootargs $(console)	root=/dev/mtdblock0	rw	ip=$(ipaddr):$(serverip)$(bootargs_end)	$(mvPhoneConfig);	bootm	0x2000000;.lcd0_enable.lcd0_params.640x480-16@60.bootdelay.disaMvPnp.00:50:43:%02x:%02x:%02x.ethmtu.eth1mtu.mvPhoneConfig. mv_phone_config=dev[0]:fxs,dev[1]:fxo.mvNetConfig.mv_net_config=(00:11:88:0f:62:81,0:1:2:3),mtu=1500 usb0Mode=host yuk_ethaddr.00:00:00:EE:51:81 nandEcc=1bit .netretry. rcvrip.169.254.100.100. 0x02000000 .autoload.enaAutoRecovery.USB

helge,

Is there a suport website where you can look for u-boot source code? or perhaps request it from the manufacturer?

We'd never know what they did in the code that could have changed the bootargs, or did similar things.

For example, if you look in the MVEBU kernel thread, NAS326 installation section:
http://forum.doozan.com/read.php?2,32146

In this NAS326 box, Zyxel actually had a hardcoded bootcmd (doh!). I could only control stock u-boot bootcmd after looking at their source code.

So we are basically blind without the GPL :)

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

Hi bodhi,

>Is there a suport website where you can look for u-boot source code? or perhaps request it from the manufacturer?
there is just a manual and a reset tool. The "manufacturer" is just one of those "i buy a bunch of devices and let the manufacturer label it with my name" company. Most of the times they just do wired stuff to the software, so its not working well and behaves different than stock software.
So our guess that they did something to bootrom or u-boot isn't that low ;)

But since they just resell stuff, i don't think they can/wan't to provide full source. But i'll write a mail to support.
But altough they do software sloppy, i also think they stick to GPL. SO i did some diging
€
I always wondered how they do internet reset. In:

medionsource\recoveryfs\sbin\startrecovery
#!/bin/sh

echo "Recovery started..."

/bin/led_indicator recovery-start

#call the start_usb_burn to see if we can do everything from USB
/sbin/start_usb_burn

Ok USB recovery. So lets have a look at that file:

cp /mnt/usb/recoveryfullfs.tar.gz /recoveryfullfs.tar.gz
gunzip /recoveryfullfs.tar.gz
tar xf /recoveryfullfs.tar
#/dev needs to be populated for recoveryfullfs
cd /
tar c dev | tar x -C /recoveryfullfs

echo "changing root to /recoveryfullfs"
chroot /recoveryfullfs /init

So we need recoveryfullfs to proceed. Lets get back to "startrecovery"

echo "USB Reflash unsuccessful. Attempting online recovery"
/sbin/start_network
/sbin/get_recovery_script

Oh thats nice ONLINE.
Start_network really start network. SO lets look at get_recovery_script

wget -O /sbin/recovery_script -T 30 -t 1 -q \
http://recovery.medion.hipserv.com/downloads/recovery/get_recovery_script.php\

Oha! so let's download recovery_script and have a look at it. (The other code in get_recovery_script is the same as in usb_burn)

wget -O /recoveryfullfs.tar.gz.....

Now we have the file recoveryfullfs.tar.gz and start_recovery is calling downloaded recovery_script.
---------------------------
#If we've reached this point /sbin/recovery_script has been downloaded
#so execute it
/sbin/recovery_script
--------------------------
Recovery script chrooting into downloaded and extracted recoveryfullfs.tar.gz calling init

chroot /recoveryfullfs /init

Init himself

flash_eraseall /dev/mtd2
wget http://recovery.medion.hipserv.com/downloads/recovery/get_firmware.php | ubiformat /dev/mtd2 -s 2048 -O 2048 -S $UBISIZE -f -
ubiattach /dev/ubi_ctrl -m 2 -O 2048
mount -t ubifs ubi0:rootfs /mnt/
exec sh

Get_firmware downloads hipserv2_netgear-20111019.ubi which is indeed a ubifs

first bytes: UBI#############

DOWNLOAD

As always i've uploaded all new files here. I am using my windows today so it had to be .zip
I also dont know yet what is in "sh" cause my windows wont extract it (symlinks...)

But as i googled some params. it seems to be the same on all storas SO nothing new for you :P

But than new hope rises. I was writing my mail to medion and decided to visit the FAQ
finding a FW Update
If you google that number you quickly find a forum, where the ftp server with a FW Update from 2012 is named
It didnt say kernel Update, just some Software Updats and "general" fixes
:



Edited 7 time(s). Last edit at 03/13/2017 06:53PM by helge.

helge,

Let's hack our way in, slowly step by step

setenv arcNumber 4931
setenv mainlineLinux yes
setenv set_bootargs 'setenv bootargs console=ttyS0,115200'
setenv usb_load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
setenv usb_load_uinitrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
setenv usb_boot 'usb start; run set_bootargs; run usb_load_uimage; run usb_load_uinitrd; bootm 0x800000 0x1100000'
run usb_boot

See if we get the kernel running at all.

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



Edited 1 time(s). Last edit at 03/16/2017 07:48AM by bodhi.

hi bodhi,

thanks for your reply. But it's behavior is still the same:

         __  __                      _ _
        |  \/  | __ _ _ ____   _____| | |
        | |\/| |/ _` | '__\ \ / / _ \ | |
        | |  | | (_| | |   \ V /  __/ | |
        |_|  |_|\__,_|_|    \_/ \___|_|_|
 _   _     ____              _
| | | |   | __ )  ___   ___ | |_
| | | |___|  _ \ / _ \ / _ \| __|
| |_| |___| |_) | (_) | (_) | |_
 \___/    |____/ \___/ \___/ \__|
 ** MARVELL BOARD: DB6702A-GMtech LE

U-Boot 1.1.4 (Jun  5 2013 - 10:49:39) Marvell version: 3.6.0

U-Boot code: 00600000 -> 0067FFF0  BSS: -> 006CFB00

Soc: 88F6702 A1 CPU running @ 1000Mhz L2 running @ 500Mhz
SysClock = 400Mhz , TClock = 166Mhz

DRAM (DDR2) CAS Latency = 5 tRP = 5 tRAS = 18 tRCD=6
DRAM CS[0] base 0x00000000   size 256MB
DRAM Total size 256MB  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)

Streaming disabled
Write allocate disabled


USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0
Marvell>> setenv arcNumber 4931
Marvell>> setenv set_bootargs 'setenv bootargs console=ttyS0,115200'
Marvell>> setenv mainlineLinux yes
Marvell>> setenv usb_load_uimage 'ext2load usb 0:1 0x800000 /boot/uImage'
Marvell>> setenv usb_load_uinitrd 'ext2load usb 0:1 0x1100000 /boot/uInitrd'
Marvell>> setenv usb_boot 'usb start; run set_bootargs; run usb_load_uimage; run usb_load_uinitrd; bootm 0x800000 0x1100000'
Marvell>> run usb
  usb_load_uImage usb_load_uInitrd usb_cmd usb_bootargs usb0Mode
  usb_load_uimage usb_load_uinitrd usb_boot
Marvell>> run usb_boot
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
....
.
......
............
.........................
...................................................
......................................................................................................
............................................................................

2878838 bytes read
....
.
......
............
.........................
...................................................
......................................................................................................
............................................................................................................................................................................................................
....
...............................................................................................................................................................................................................................

6535284 bytes read
## Booting image at 00800000 ...
   Image Name:   bla3185-320
   Created:      2017-03-12  16:51:34 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2878774 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initramfs-3.18.5-kirkwood-tld-1
   Created:      2015-02-19   1:49:36 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6535220 Bytes =  6.2 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

I've hooked up the device on a hub and connected it with my laptop running isc-dhcpd. I see 0 on my interface if we run custom kernel.

In the meanwhile (and before i even posted here) i tried openstoras kernel. The result is the same. In the wiki it says Medion Lifecloud 2-bay NAS supported



Edited 3 time(s). Last edit at 03/17/2017 02:34PM by helge.

helge,

If the bootargs is that simple and we could not get it to run, most likely the DTB is wrong one.

These have the same SoCs:

NSA310S
NSA320S
Pogo V4

So perhaps we want to try all 3.

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

same here .. tested with all mentioned DTBs ..

my kirkwood kernel builds
my oxnas kernel builds
Tvheadend Kirkwood Debian packages

my kirkwood devices:
- 1x hp t5325 (1,2 GHz, 88F6281 / 512 MB / 4x USB)

my oxnas devices
- 2x pogoplug

my dove devices
- 2x Chip PC LXD8541 (800 MHz, 88F510 / 1024 MB / 6x USB)
- 1x Wyse T50 (1,0 GHz, 88F510 / 1024 MB / 4x USB)

my amlogic devices
- several s905x / s912 devices

hi bodhi,
hi pengu,

i confirm that the device won't boot with the mentioned DTB. As always without a response.

@pengu
Have you seen the "strange" broadcasts the Medion NAS does while in Recovery? Its shouting "Hail dictator-of-germany-'till-1945"... in my network oO



Edited 4 time(s). Last edit at 03/27/2017 02:02PM by helge.

helge,

> Its shouting "Hail dic
> tator-of-germany-'till-1945"... in my network oO

Haha :) some sick joke.

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

helge,


Here is another approach. Let's try booting a non-FDT kernel. This is the rootfs that has non-FDT kernel.

Updated 02 Sept 2014 (rootfs): 

Rootfs Debian-3.16.0-kirkwood-tld-2 was uploaded. This rootfs is to keep in sync with kernel Linux-3.16.0-kirkwood-tld-2 (and its new features).

And then you would want to set arcNumber and machid to the correct values for Pogo V4 in serial console:

setenv arcNumber 3960
setenv machid f78

The rest of the envs are exactly as before.

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

bodhi Wrote:
-------------------------------------------------------
> helge,
>
> > Its shouting "Hail dic
> > tator-of-germany-'till-1945"... in my network oO
>
> Haha :) some sick joke.

The tech guy has a bad sense of humor :P
I've confronted Medion with my Wireshark "Hail..." Packets. Lets see if they respond with U-boot code :D

same as before..

...

USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
reading /uImage
.............................................................................................................................................................

2756040 bytes read
reading /uInitrd
.............................................................................................................................................................

6032465 bytes read
## Booting image at 00800000 ...
   Image Name:   Linux-3.16.0-kirkwood-tld-2
   Created:      2014-09-01  23:18:31 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2755976 Bytes =  2.6 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initramfs-3.16.0-kirkwood-tld-2
   Created:      2014-09-01  23:18:48 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6032401 Bytes =  5.8 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

and with the last known version of the kernel 3.16 ..

...
USB 0: host mode
PEX 0: PCI Express Root Complex Interface
PEX interface detected Link X1
Net:   egiga0 [PRIME]
Hit any key to stop autoboot:  0 
(Re)start USB...
USB:   scanning bus for devices... 2 USB Device(s) found
Waiting for storage device(s) to settle before scanning...
1 Storage Device(s) found
reading /uImage
...........................................................................................................................................................

2786896 bytes read
reading /uInitrd
...........................................................................................................................................................

6308708 bytes read
## Booting image at 00800000 ...
   Image Name:   vmlinuz-3.16.42-kirkwood-tld-3
   Created:      2017-03-30  18:07:50 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    2786832 Bytes =  2.7 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
OK
## Loading Ramdisk Image at 01100000 ...
   Image Name:   initramfs-3.16.42-kirkwood-tld-3
   Created:      2017-03-30  18:08:26 UTC
   Image Type:   ARM Linux RAMDisk Image (gzip compressed)
   Data Size:    6308644 Bytes =  6 MB
   Load Address: 00000000
   Entry Point:  00000000
   Verifying Checksum ... OK

Starting kernel ...

The LEDs indicate that there is some more stuff going on as with kernel 3.18.5 ..

The green one keeps blinking for one second then .. the red one is lighting up ..
With Kernel 3.18.5 ... only the blue LEDs lights up



Edited 2 time(s). Last edit at 03/30/2017 01:31PM by pengu.

pengu Wrote:
-------------------------------------------------------
> same as before..
>
>

> ...
> 
> USB 0: host mode
> PEX 0: PCI Express Root Complex Interface
> PEX interface detected Link X1
> Net:   egiga0 [PRIME]
> Hit any key to stop autoboot:  0
> (Re)start USB...
> USB:   scanning bus for devices... 2 USB Device(s)
> found
> Waiting for storage device(s) to settle before sca
> nning...
> 1 Storage Device(s) found
> reading /uImage
> ..................................................
> ..................................................
> ..................................................
> .......
> 
> 2756040 bytes read
> reading /uInitrd
> ..................................................
> ..................................................
> ..................................................
> .......
> 
> 6032465 bytes read
> ## Booting image at 00800000 ...
> Image Name:   Linux-3.16.0-kirkwood-tld-2
> Created:      2014-09-01  23:18:31 UTC
> Image Type:   ARM Linux Kernel Image (uncompres
> sed)
> Data Size:    2755976 Bytes =  2.6 MB
> Load Address: 00008000
> Entry Point:  00008000
> Verifying Checksum ... OK
> OK
> ## Loading Ramdisk Image at 01100000 ...
> Image Name:   initramfs-3.16.0-kirkwood-tld-2
> Created:      2014-09-01  23:18:48 UTC
> Image Type:   ARM Linux RAMDisk Image (gzip com
> pressed)
> Data Size:    6032401 Bytes =  5.8 MB
> Load Address: 00000000
> Entry Point:  00000000
> Verifying Checksum ... OK
> 
> Starting kernel ...
> 
> 
>

>
> and with the last known version of the kernel 3.16
> ..
>
>

> ...
> USB 0: host mode
> PEX 0: PCI Express Root Complex Interface
> PEX interface detected Link X1
> Net:   egiga0 [PRIME]
> Hit any key to stop autoboot:  0
> (Re)start USB...
> USB:   scanning bus for devices... 2 USB Device(s)
> found
> Waiting for storage device(s) to settle before sca
> nning...
> 1 Storage Device(s) found
> reading /uImage
> ..................................................
> ..................................................
> ..................................................
> .....
> 
> 2786896 bytes read
> reading /uInitrd
> ..................................................
> ..................................................
> ..................................................
> .....
> 
> 6308708 bytes read
> ## Booting image at 00800000 ...
> Image Name:   vmlinuz-3.16.42-kirkwood-tld-3
> Created:      2017-03-30  18:07:50 UTC
> Image Type:   ARM Linux Kernel Image (uncompres
> sed)
> Data Size:    2786832 Bytes =  2.7 MB
> Load Address: 00008000
> Entry Point:  00008000
> Verifying Checksum ... OK
> OK
> ## Loading Ramdisk Image at 01100000 ...
> Image Name:   initramfs-3.16.42-kirkwood-tld-3
> Created:      2017-03-30  18:08:26 UTC
> Image Type:   ARM Linux RAMDisk Image (gzip com
> pressed)
> Data Size:    6308644 Bytes =  6 MB
> Load Address: 00000000
> Entry Point:  00000000
> Verifying Checksum ... OK
> 
> Starting kernel ...
> 
> 
>

>
> The LEDs indicate that there is some more stuff go
> ing on as with kernel 3.18.5 ..
>
> The green one keeps blinking for one second then .
> . the red one is lighting up ..
> With Kernel 3.18.5 ... only the blue LEDs lights u
> p

pengu,

Do you have earlyprintk=serial bootargs set in this run?

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

ok .. same as before .. nothing more ..
(tested with linux-3.16.42 and linux-4.4.6)



Edited 1 time(s). Last edit at 03/30/2017 04:57PM by pengu.

pengu Wrote:
-------------------------------------------------------
> ok .. same as before .. nothing more ..
> (tested with linux-3.16.42 and linux-4.4.6)


What is your u-boot envs or kernel load addresses? did you try both stock addresses and our convetional 0x8000000 ?

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

bodhi Wrote:
-------------------------------------------------------
> pengu Wrote:
> --------------------------------------------------
> -----
> > ok .. same as before .. nothing more ..
> > (tested with linux-3.16.42 and linux-4.4.6)
>
>
> What is your u-boot envs or kernel load addresses?
> did you try both stock addresses and our convetion
> al 0x8000000 ?

## Booting image at 00800000 .
## Loading Ramdisk Image at 01100000 ...

seems like he used 0x800000 for uImage and 0x1100000 for uInitrd.
Medions first reply doesn't look very promising. They just send me a mail, with a link where i should search for the source. They didn't even provided a direct link :P
But it took them four buisness days to respond....



Edited 2 time(s). Last edit at 03/31/2017 04:26PM by helge.

This is not exactly fitting the topic, but I use the same device and need help.
I think I bricked the board with a wrong u-boot (no leds except the green network one).
Sadly it seems that kwboot isn't working, so I think my last chance is the JTAG connector.
But to make it boot, I need a copy of the original/a working u-boot (stupidly I thought I'm much cleverer than anyone else and didn't make a backup). I don't want to buy a JTAG connector without an image of a working u-boot, so maybe someone, especially helge, could upload one.
Thanks for your help, jonrv

hi jonrv,

sad to hear that. But atleast you were so brave to flash a new uboot. Now we know it doesnt work :)

I have an untested nandbackup of mtd0,1 and 2, so hopefully you should be able to restore your u-boot. I'll post links, after i found my notebook.

Good to hear that, helping me a lot.
Thanks, jonrv

Here you go

https://drive.google.com/file/d/0B_YdeX8E4nUsTkNrYUV0N1Vad2c/view?usp=sharing

Thank you very much, hopefully it will work.
Bye

Hi jonrv,

did the backup work?

yes, this seems the only working "envs"

other than gives gives me a

pc : [<0064c700>]          lr : [<00620da0>]                                                                                        
sp : 005fb1d0  ip : 00000003     fp : 00000002                                                                                      
r10: 00690c80  r9 : 00000001     r8 : 005fffcc                                                                                      
r7 : dc87b18b  r6 : c19c3a76     r5 : 93e75275  r4 : 00000000                                                                       
r3 : 00000080  r2 : 006cf9c0     r1 : 000f4240  r0 : 00000001                                                                       
Flags: nZcv  IRQs off  FIQs off  Mode SVC_32                                                                                        
Resetting CPU ...

when changing the the load adress(es) to other than default, I get this when loading the initrd



Edited 2 time(s). Last edit at 06/05/2017 05:03PM by pengu.

pengu Wrote:
-------------------------------------------------------
> yes, this seems the only working "envs"
>
> other than ghis gives me a
>
>

> pc : [<0064c700>]          lr : [<00620da0>]
> sp : 005fb1d0  ip : 00000003     fp : 00000002
> r10: 00690c80  r9 : 00000001     r8 : 005fffcc
> r7 : dc87b18b  r6 : c19c3a76     r5 : 93e75275  r4
> : 00000000
> r3 : 00000080  r2 : 006cf9c0     r1 : 000f4240  r0
> : 00000001
> Flags: nZcv  IRQs off  FIQs off  Mode SVC_32
> Resetting CPU ...
>

Sorry, I don't understand what you are saying. Can you be more specific? and quote the previous post.

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