Quantcast
Channel: Linux Device Hacking
Viewing all articles
Browse latest Browse all 3247

Bodhi Debian on Mirabox (1 reply)

$
0
0
It's been a while since I have posted, lurked mostly with nothing new to add. Picked up a Globalscale Mirabox cheaply and have tried to load bodhi Debian on it. Not sure what env's to use on the stock u-boot to get Debian-4.12.4-mvebu-tld-1 to boot from the external micro sd slot (mmcblk0).

Globalscale Mirabox specs:
1.2Ghz Marvell Armada CPU ARMADA 370 ARM v7 compliant
802.11b/g/n Wifi with Marvell 88W8787 and Bluetooth 3.0
1GB DDR3
1 GB NAND Flash
2 each 10/100/1000 Ethernet Ports
2 each USB 3.0 host
1 microsd card slot/reader, 1 additional Mini PCIe slot for expansion (internal)
For additional 2x2, 3x3, 4x4 WiFi Radios, or 3G modules
3 LED controlled by GPIO, reset button
external power supply
Port for JTAG and Debugging options

Stock uEnv's:


BootROM 1.08
Booting from SPI flash
DDR3 Training Sequence - Ver 4.4.0
DDR3 Training Sequence - Ended Successfully
Status = MV_OK
BootROM: Image checksum verification PASSED

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


U-Boot 2009.08 (Jul 15 2015 - 21:57:33)Marvell version: 1.1.2 NQ
U-Boot Addressing:
       Code:            00600000:006AFFF0
       BSS:             006F7240
       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.
SF: Detected MX25L1605D with page size 256, total 2097152 bytes
FPU not initialized
USB 0: Host Mode
USB 1: Host Mode
Modules/Interfaces Detected:
       RGMII0 Phy
       RGMII1 Phy
       PEX0 (Lane 0)
       SATA0 (Lane 2)
       SATA1 (Lane 3)
MMC:   MRVL_MMC: 0
Net:   egiga0 [PRIME], egiga1
flag =  ff
Hit any key to stop autoboot:  0


Marvell>> printenv
bootdelay=3
baudrate=115200
loads_echo=0
ipaddr=10.4.50.165
serverip=10.4.50.5
rootpath=/mnt/ARM_FS/
netmask=255.255.255.0
console=console=ttyS0,115200
sata_delay_reset=0
enaExtDisk=no
MALLOC_len=5
ethprime=egiga0
bootargs_root=root=/dev/nfs rw
bootargs_end=:10.4.50.254:255.255.255.0:KW40:eth0:none
image_name=uImage
load_addr=0x02000000
standalone=fsload $load_addr $image_name;setenv bootargs $console $mtdparts root=/dev/mtdblock0 rw ip=$ipaddr:$serverip$bootargs_end; bootm $load_addr;
ethmtu=1500
eth1mtu=1500
mvNetConfig=mv_net_config=1,(XX:XX:XX:XX:XX:XX,0:1:2:3:4),mtu=1500
usb0Mode=host
usb1Mode=host
usbActive=2
yuk_ethaddr=XX:XX:XX:XX:XX:XX
netretry=no
rcvrip=169.254.100.100
loadaddr=0x02000000
autoload=no
eeeEnable=no
ethact=egiga0
bootcmd=usb start; fatload usb 0 0x6400000 uimage_3.2.36.v9; bootm 0x6400000
ethaddr=XX:XX:XX:XX:XX:XX
eth1addr=XX:XX:XX:XX:XX:XX
stdin=serial
stdout=serial
stderr=serial
enaMonExt=no
pexMode=RC
setL2CacheWT=no
sata_dma_mode=yes
netbsd_en=no
vxworks_en=no
realboot=mmcinfo;fatload mmc 0 0x6400000 uImage; bootm 0x6400000
realboot1=run realboot
disaMvPnp=no
enaAutoRecovery=yes
pcieTune=no
bootargs=console=ttyS0,115200 root=/dev/mtdblock0 rw ip=10.4.50.165:10.4.50.5:10.4.50.254:255.255.255.0:KW40:eth0:none

Environment size: 1255/65532 bytes

The device successfully boots on the stock 3.2.36 Debian Wheezy 4 Gb rootfs which is on a micro-sd card internal on the motherboard and is considered a USB drive (not sure why internal is USB and external is MMC).

Am assuming because of stock u-boot being so old, it does not support separate dtb. Regardless of separate embedded dtb vs separate, not sure what memory areas to load uImage, uInitrd into during boot.

Can anybody provide some guidance as to uEnv's to try? Any help would be appreciated.

LME

Viewing all articles
Browse latest Browse all 3247

Trending Articles