General NAS-Central Forums

Welcome to the NAS community
It is currently Tue Nov 21, 2017 5:16 pm

All times are UTC




Post new topic Reply to topic  [ 7 posts ] 
Author Message
 Post subject: FW problem
PostPosted: Thu Feb 19, 2015 7:37 am 
Offline

Joined: Thu Feb 19, 2015 7:28 am
Posts: 3
Sry with my en.

I check problem in Terminal :

Code:
$ reset
Resetting Oxsemi NAS..

1.00 U-Boot 1.1.2 (Apr 10 2009 - 16:43:58)

U-Boot code: 48D00000 -> 48D17270  BSS: -> 48D1AF20
RAM Configuration:
        Bank #0: 48000000 128 MB
SRAM Configuration:
        128KB at 0x58000000
Flash:  4 MB
In:    serial
Out:   serial
Err:   serial
Hit any key to stop autoboot:  0
## Booting image at 41020000 ...
   Image Name:   Linux-2.6.24.4
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1771204 Bytes =  1.7 MB
   Load Address: 48008000
   Entry Point:  48008000
   Verifying Checksum ... Bad Data CRC


how to Flash?

or TFTP bootimage download to tftp in my computer?

Please help me.


Top
 Profile  
 
 Post subject: Re: FW problem
PostPosted: Thu Feb 19, 2015 11:53 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6073
I think the easiest way to flash it is too boot a tftp uploaded kernel, and then upgrade the firmware from the web UI. You can find uImage here, it's DATA_1000.


Top
 Profile  
 
 Post subject: Re: FW problem
PostPosted: Thu Feb 19, 2015 5:45 pm 
Offline

Joined: Thu Feb 19, 2015 7:28 am
Posts: 3
Mijzelf wrote:
I think the easiest way to flash it is too boot a tftp uploaded kernel, and then upgrade the firmware from the web UI. You can find uImage here, it's DATA_1000.


Thy,

and system start in console ? becouse need uprgrade from web UI :/

Code:
$ iminfo

## Checking Image at 48000000 ...
   Image Name:   Linux-2.6.24.4
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    1771216 Bytes =  1.7 MB
   Load Address: 48008000
   Entry Point:  48008000
   Verifying Checksum ... OK
$ printenv
bootcmd=cp 0x411e0000 0x4a000000 0x25c000; bootm 0x41020000
bootdelay=2
baudrate=115200
autoload=n
MODEL_ID=D401
PRODUCT_NAME=NSA-210
FEATURE_BIT=00
CONTRY_TYPE=FF
VENDOR_NAME=ZyXEL Communications Corp.
ethaddr=40:4A:03:08:94:7A
stdin=serial
stdout=serial
stderr=serial
bootargs=console=ttyS0,115200n8 root=/dev/ram0 rw init=/sbin/init initrd=0x4a000000,4M elevator=cfq mtdparts=physmap-flash.0:128k(ub
oot),1792k(kernel),1664k(initrd),448k(etc),48k(empty),8k(env1),8k(env2) mem=128M poweroutage=yes
filesize=1b0710
fileaddr=48000000
bootfile=uImage
gatewayip=192.168.137.1
netmask=255.255.255.0
ipaddr=192.168.137.68
serverip=192.168.137.1

Environment size: 640/8187 bytes
$


Thy


Top
 Profile  
 
 Post subject: Re: FW problem
PostPosted: Thu Feb 19, 2015 8:02 pm 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6073
You are not very verbose. I guess that uImage is somehow the DATA_1000? I guess you can boot it using 'bootm 0x48000000'. But as the load address is 0x48008000, I don't think 0x48000000 is a good address. I don't see how u-boot can copy the kernel to the load address without overwriting uImage.

Seeing your bootcommand:
bootcmd=cp 0x411e0000 0x4a000000 0x25c000; bootm 0x41020000

and commandline : initrd=0x4a000000, I guess the flash is directly accesible, and the kernel is (in flash) @0x41020000.

So the box might be booted with

tftp 49000000 uImage
0x411e0000 0x4a000000 0x25c000
bootm 0x49000000


Top
 Profile  
 
 Post subject: Re: FW problem
PostPosted: Thu Feb 19, 2015 9:19 pm 
Offline

Joined: Thu Jan 15, 2015 9:49 pm
Posts: 70
that boot command looks like

Code:
copy address address length


i guess the initrd is copied to the working location 0x4a000000....
from 0x411e0000 with length 0x25c000
I may be wrong .....


Top
 Profile  
 
 Post subject: Re: FW problem
PostPosted: Fri Feb 20, 2015 8:34 am 
Offline

Joined: Mon Jun 16, 2008 10:45 am
Posts: 6073
Yes, I think you are right. The original boot command is
Code:
cp 0x411e0000 0x4a000000 0x25c000
bootm 0x41020000
I think this means:
Copy 0x411e0000 to 0x4a000000 for length 0x25c000,
then boot the uImage at 0x41020000. 'Boot uImage' means it will copy the embedded kernel to the address specified in the uImage header (0x48008000) and then jump to the entry point (also 0x48008000)

So it seems your flash is memory mapped, else uImage should have to be copied to ram before executing bootm. I think it's mapped starting at 0x41000000. Further we know there is ram at addresses 0x48000000 and 0x4a000000 and beyond. That is a range of 32MiB. So I guess we can safely assume that whole range is available.
So my proposal:
Code:
tftp 49000000 uImage
cp 0x411e0000 0x4a000000 0x25c000
bootm 0x49000000
Tftp uImage to 0x49000000 (within the ram, about 16MiB after the kernel load address. Plenty of space to copy the kernel). Then copy the initrd from flash to ram.
boot the uImage at 0x49000000.

The address of the initrd is specified in the kernel command line, so the kernel can find it.


Top
 Profile  
 
 Post subject: Re: FW problem
PostPosted: Wed Feb 25, 2015 11:09 pm 
Offline

Joined: Thu Feb 19, 2015 7:28 am
Posts: 3
Thank You ALL..


Problem is allready o.k

In start kernel...

set ip
Code:
/sbin/ifconfig egiga0 192.168.x.x


and start utility zyxel, update fw...
Reset o.k


Top
 Profile  
 
Display posts from previous:  Sort by  
Post new topic Reply to topic  [ 7 posts ] 

All times are UTC


Who is online

Users browsing this forum: No registered users and 6 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot post attachments in this forum

Search for:
Jump to:  
Powered by phpBB® Forum Software © phpBB Group