Buffalo NAS-Central Forums

Welcome to the Linkstation Wiki community
It is currently Fri Nov 24, 2017 5:50 pm

All times are UTC+01:00




Post new topic  Reply to topic  [ 2 posts ] 
Author Message
PostPosted: Mon Mar 16, 2009 7:16 am 
Offline
Total Newbie

Joined: Sun Mar 15, 2009 2:14 pm
Posts: 3
Hello... I do not know what to do next. After reading many wiki pages, I just can't proceed. Please help. :?

Originally, I installed FreeLink on my KuroBox Pro following the Automatic Install procedure.
And now, since I successfully managed to have serial control access with the SCON-Kit Pro,
I am thinking of trying the Armel Debian - Manual Install procedure.

But since the HD had to be a new and unformatted HD, I "erased" the data as recommended in
FreeLink Automatic Install page for non-virgin HDs (i.e. I placed the HD on an external casing and
executed "cat /dev/zero > /dev/sdb" on a linux workstation).

After inserting back the HD to KuroBoxPro, I started with the Armel procedure:
1. Connect up the blank unformatted hard drive
- DONE!
2. Connect ethernet to your network (it would be best to use the 192.168.11.x subnet)
- DONE!
3. Connect serial cable for serial console and power on.
- Hmmmm... it kept trying to connect to TFTP Server at 192.168.11.1 and looking for uImage.buffalo (see footer).
I tried to ignore this and went ahead to step 4.
4. Access the Samba share on the Kurobox Pro named mtd_device, the flash memory is available via Samba with
the native EM mode at: smb://kuroip/mtd_device
- I cannot seem to connect to this directory. I tried to access via windows (\\192.168.11.150\mtd_device\) or
via linux (smb://192.168.11.150/mtd_device) but failed.

To install Armel Debian, should the KuroBox Pro need to be reset to factory defaults?

If so, also from the Freelink Automatic Install page, I noticed that for non-virgin KuroBoxes
"change u-boot settings (require a serial console access) to set u-boot to boot on /dev/mtdblock2".

So how can I set u-boot? Please help.



-------------- KurobBox Pro serial output log --------------
Code:
Orion1   CPU =  Low 

=== KURO U-Boot. ===
 ** LOADER **
 ** KUROBOX BOARD: KURO_BOX  LE (CFG_ENV_ADDR=fffff000)


U-Boot 1.1.1 (Apr 10 2007 - 18:10:08) Marvell version: 1.12.1 - TINY

DRAM CS[0] base 0x00000000   size 128MB
DRAM Total size 128MB
[256kB@fffc0000] Flash: 256 kB
Addresses 20M - 0M are saved for the U-Boot usage.
Mem malloc Initialization (20M - 16M): Done
NAND: 256 MB

Soc: 88F5182 A2
CPU: ARM926 (Rev 0) running @ 500Mhz
Orion 1 streaming disabled
SysClock = 250Mhz , TClock = 166Mhz


USB 0: host mode
USB 1: host mode
PCI 0: PCI Express Root Complex Interface
PCI 1: Conventional PCI, speed = 33000000
Net:   egiga0 [PRIME]
Using 88E1118 phy
hit any key to switch tftp boot.
Hit any key to stop autoboot:  0
<<system_bootend>>
Hit any key to stop autoboot:  0

Reset IDE:
Marvell Serial ATA Adapter
Integrated Sata device found
  Device 0: OK
Model: ST31500341AS                             Firm: CC1G     Ser#:             9VS0KJDQ
            Type: Hard Disk
            Supports 48-bit addressing
            Capacity: 1430799.3 MB = 1397.2 GB (-1364690128 x 512)

Using device ide0, partition 1
** Bad partition 1 **
<<stop_sound>>
## Booting image at 00100000 ...
Bad Magic Number
bootm fail.
<<system_not_found>>
Using egiga0 device
TFTP from server 192.168.11.1; our IP address is 192.168.11.150
Filename 'uImage.buffalo'.
Load address: 0x100000
Loading: T T
Retry count exceeded; starting again


Top
   
PostPosted: Mon Mar 16, 2009 10:13 am 
Offline
Total Newbie

Joined: Sun Mar 15, 2009 2:14 pm
Posts: 3
It didn't occur to me that a "Ctrl+C" should do it.
Good thing I read the other posts and got the idea from viewtopic.php?f=51&t=5281

Here is my current printenv output:
------------- KuroBox Pro log -------------
Code:
Marvell>> <INTERRUPT>
Marvell>>
Marvell>>
Marvell>> printenv
baudrate=115200
loads_echo=0
ipaddr=192.168.11.150
serverip=192.168.11.1
rootpath=/nfs/arm
cpuName=926
CASset=min
MALLOC_len=4
bootargs_end=:::DB88FXX81:eth0:none
ethact=egiga0
ethaddr=00:16:01:A4:DB:F5
buffalo_ver=BOOTVER=1.091
build_time=18:10:02
initrd=initrd.buffalo
kernel=uImage.buffalo
nand_uImage_offset=20000
default_initrd_addr=0x02000000
def_tftp=tftp $(default_kernel_addr) $(kernel); tftp $(default_initrd_addr) $(initrd); setenv bootargs $(bootargs_base) $(bootargs_root)  rw initrd=0x02000040,20M panic=5 $(buffalo_ver); bootm $(default_kernel_addr) $(default_initrd_addr)
default_kernel_addr=0x00100000
bootargs_base=console=ttyS0,115200
bootargs_root=root=/dev/sda2 rw panic=5
bootargs=console=ttyS0,115200 root=/dev/sda2 rw panic=5 BOOTVER=1.09
bootcmd=ide reset; ext2load ide 0:1 $(default_kernel_addr) /$(kernel); bootm $(default_kernel_addr)
nand_boot=no
stdin=serial
stdout=serial
stderr=serial
enaMonExt=no
enaFlashBuf=yes
enaCpuStream=no
ethprime=egiga0
bootdelay=3
disaMvPnp=no
overEthAddr=no
usb0Mode=host
usb1Mode=host

Environment size: 1046/4092 bytes


So, I will encode the following commands in the Marvell>> prompt to restore KuroBox Pro, right? :?
(reference: Kurobox Pro u-boot environment variable settings FLASH BOOT section)

------------- u-boot environment variable settings -------------
Code:
setenv default_kernel_addr 0x00100000 
setenv bootargs_base console=ttyS0,115200
setenv bootargs_root root=/dev/mtdblock2 rw
setenv bootargs $(bootargs_base) $(bootargs_root) $(buffalo_ver)
setenv uImage_block 0
setenv uImage_offset 0x00020000
setenv bootcmd 'nboot $(default_kernel_addr) $(uImage_block) $(uImage_offset); bootm $(default_kernel_addr)'


Please someone confirm before I proceed... (I fear a mistake will brick the box).


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

All times are UTC+01:00


Who is online

Users browsing this forum: No registered users and 1 guest


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:
Powered by phpBB® Forum Software © phpBB Limited