Print

[ckilmer75]

Hello All,

I'm hoping someone on the forums can help me with my issue as there seems to be sparse info so far on working with the MiraBox.

I just received a new Mirabox from Global Technologies and it's been good to go, until this last power cycle, now it will not load the kernel.  It boots into u-boot fine but then when it says loading kernel, it just freezes there and does nothing.  I have the debian image and rootfs files needed from the manufacturers website to re-install but there are no directions anywhere I can find through google to do so.  Everything I find is geared towards Sheeva or GuruPlug and I don't want to make matters worse by trying to follow one of them and it not be correct for my MiraBox.

Code: [Select]

|  \/  | __ _ _ ____   _____| | |
| |\/| |/ _` | '__\ \ / / _ \ | |
| |  | | (_| | |   \ V /  __/ | |
|_|  |_|\__,_|_|    \_/ \___|_|_|
         _   _     ____              _
        | | | |   | __ )  ___   ___ | |_
        | | | |___|  _ \ / _ \ / _ \| __|
        | |_| |___| |_) | (_) | (_) | |_
         \___/    |____/ \___/ \___/ \__|
 ** LOADER **


U-Boot 2009.08 (Sep 16 2012 - 22:50:06)Marvell version: 1.1.2 NQ
U-Boot Addressing:
       Code:            00600000:006AFFF0
       BSS:             006F8E40
       Stack:           0x5fff70
       PageTable:       0x8e0000
       Heap address:    0x900000:0xe00000
Board: DB-88F6710-BP
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: Detected No Link.
PEX 1: Root Complex Interface, Detected Link X1
DRAM:   1 GB
       CS 0: base 0x00000000 size 512 MB
       CS 1: base 0x20000000 size 512 MB
       Addresses 14M - 0M are saved for the U-Boot usage.
NAND:  1024 MiB
Bad block table found at page 262016, version 0x01
Bad block table found at page 261888, version 0x01
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Modules/Interfaces Detected:
       RGMII0 Phy
       RGMII1 Phy
       PEX0 (Lane 0)
       PEX1 (Lane 1)
phy16= 72
phy16= 72
MMC:   MRVL_MMC: 0
Net:   egiga0 [PRIME], egiga1
Hit any key to stop autoboot:  0

NAND read: device 0 offset 0x400000, size 0x400000
 4194304 bytes read: OK
## Booting kernel from Legacy Image at 06400000 ...
   Image Name:   Linux-2.6.35.9
   Created:      2012-08-24   2:13:39 UTC
   Image Type:   ARM Linux Kernel Image (uncompressed)
   Data Size:    3439332 Bytes =  3.3 MB
   Load Address: 00008000
   Entry Point:  00008000
   Verifying Checksum ... OK
   Loading Kernel Image ... OK
OK

Starting kernel ...

Uncompressing Linux... done, booting the kernel.



And that's where it stops.  I never get a login prompt.  So I'm assuming I need to re-flash the Debian OS and/or rootfs.  Anyone have any good info for me?

Thank you in advance,

Chris

[ckilmer75]

In the interest of sharing information in case anyone else runs into this problem, here is the information I received from GlobalScaleTechnologies Support"

Below is the method for mirabox reflash or restore.  It is for advanced users only and performed at user’s own risk.

Please download the MiraBox rescue disk https://docs.google.com/file/d/0B0imSF-34b8dZEc0SFo3N1Fzb0E/edit. On a Linux computer, format a micro SD card with first partition FAT 16 (size 100MB), second partition EXT 3 (size 900MB+), then place the file “mirabox” into the first partition and extract the file “rootfs.tgz” into the second partition. Under the uboot prompt, enter:
set bootcmd ‘usb start; fatload usb 1 0x6400000 mirabox; bootm 0x6400000’
set bootargs ‘console=ttyS0,115200 root=/dev/sdb2 rootwait’
boot
#this allows the mirabox to boot using the micro SD rescue disk, this change is not permanent and will be rolled back upon reboot
#after successfully boot up using the micro SD rescue disk. Place kernel and rootfs image file into a USB drive and plug into mirabox and run below commands
#here we assume the USB drive is mounted as /media/usb3, if it is mounted differently, please modify below commands accordingly
cd /media/usb3/
flash_eraseall /dev/mtd1
nandwrite -q -p /dev/mtd1 /media/usb3/<kernel file name>
ubiformat /dev/mtd2 --flash-image=<rootfs file name>
sync
reboot

Best Regards,

Support 1103
Globalscale Technologies, Inc.
Disclaimer: This e-mail message and all attachments transmitted with it are intended solely for the use of the addressee and may contain legally privileged and confidential information. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution, copying, or other use of this message or its attachments is strictly prohibited. If you have received this message in error, please notify the sender immediately by replying to this message and please delete it from your computer. Any views expressed in this message are those of the individual sender unless otherwise stated. Company has taken enough precautions to prevent the spread of viruses. However the company accepts no liability for any damage caused by any virus transmitted by this email.

[.Madox.]

Many thanks for sharing this useful information, this help me out.

Regards
Marcus

[Lotharyx]

Hi,

One thing I am not following from these instructions...they say:

"Place kernel and rootfs image file into a USB drive and plug into mirabox and run below commands"

What kernel and rootfs image, where do I get those?

Thanks!

[Confusticated]

What kernel and rootfs image, where do I get those?

Have you unrar'ed the archive file Mira-RescueDisk.rar ?

Please download the MiraBox rescue disk https://docs.google.com/file/d/0B0imSF-34b8dZEc0SFo3N1Fzb0E/edit

[Lotharyx]

Hi, yes I have, but that only contains "mirabox" and "rootfs.tgz".  rootfs.tgz is not a ubi image; it's just a gzipped tar'ed filesystem.  From what I have read about the ubiformat command and ubi images, that is not the same thing.

I understand that "mirabox" is a kernel image; is that the one to use on the nandwrite command? 

Do I have to create my own ubi image from the untar'ed rootfs.tgz? 

Thanks!

[Confusticated]

only contains "mirabox" and "rootfs.tgz"

So it contains only the rescue kernel and rescue root file system.

"mirabox" is a kernel image; is that the one to use

Although it is obviously compatible with the Mirabox, I cannot say if there is some functionality missing or not.

create my own ubi image from the untar'ed rootfs.tgz

That is possible (with the use of 'ubinize' after creating your own rootfs image file).
Rather than create your own based on the 'rescue' disk it would be safer to flash the stock OEM software that is installed on the Mirabox when you received it (which may in fact prove to be the same).

Which brings us full circle back to your original question...

What kernel and rootfs image, where do I get those?

1) If your Mirabox is working, you could use that to make backup images...
2) Google for them...
3) Or re-read ckilmer75's first post... (http://code.google.com/p/mirabox/downloads/list)

[Lotharyx]

"3) Or re-read ckilmer75's first post... (http://code.google.com/p/mirabox/downloads/list)"

...and that is the information I needed.  That link.  Now this thread is fully useful.  Thanks.

[fc]

IT didn't help me...  http://rapidshare.com/share/383FE2D9B8616D0504AB809AA5C37649 sent me to an advertisement - a video - etc.

I need a rootfs and the one I found and tried to use didn't function (rootfs_mira_debian7_v5_v7_arm8766.img). The Mira Rescue disk boots, but then I cannot create the img file.

I tried various variations - all ending essentially like this (sda2, mtdblock1, etc. tried):

md: Scanned 0 and added 0 devices.
md: autorun ...
md: ... autorun DONE.
Waiting for root device /dev/sda2...
hub 1-1:1.0: USB hub found
hub 1-1:1.0: 4 ports detected
usb 1-1.1: new high-speed USB device number 3 using ehci_marvell
usb-storage 1-1.1:1.0: Quirks match for vid 05e3 pid 0723: 8000
scsi2 : usb-storage 1-1.1:1.0
usb 1-1.2: new high-speed USB device number 4 using ehci_marvell
usb-storage 1-1.2:1.0: Quirks match for vid 05e3 pid 0723: 8000
scsi3 : usb-storage 1-1.2:1.0
scsi 2:0:0:0: Direct-Access     Generic  STORAGE DEVICE   9451 PQ: 0 ANSI: 0
sd 2:0:0:0: [sda] Attached SCSI removable disk
VFS: Cannot open root device "sda2" or unknown-block(8,2)
Please append a correct "root=" boot option; here are the available partitions:
1f00            6144 mtdblock0  (driver?)
1f01         1042432 mtdblock1  (driver?)
Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(8,2)

Is there an actual image of the actual as delivered from Mirabox?

[miran00b]

So the two part zips that made rootfs-debian6.0-gti-mirabox-v5-0-1-120924.img seemed to be about the as-shipped rootfs image to me.

I have just had success upgrading using ckilmer75's instructions from GlobalScaleTechnologies Support and the provided rescue disk and the rootfs_mira_debian7_v5_v7_arm8766.img -- did you use uImage_3.2.6_nand_new alongside that image?