Welcome! Log In Create A New Profile

Advanced

GTI Mirabox and Netgear RN120 (Armada 370) Installation

Posted by bodhi 
GTI Mirabox and Netgear RN120 (Armada 370) Installation
November 06, 2019 11:47PM
The GTI Mirabox and Netgear RN102/104 boxes use a special kernel version: linux-image-5.8.5-mvebu-370xp-tld-1. Other MVEBU kernel will not work with these 2 boxes. However, the rootfs is still common to all MVEBU boxes. This post contains the download link for the kernel each time if it is released. And the installation instruction specific to each box.

Note: The GTI Mirabox is a V5 version (it is powered by 5V power supply). There is an updated model (V9) for Mirabox, and this kernel will not work on the V9 model .

Credits:

- Thanks LeggoMyEggo and rayknight for the testing efforts to bring up the GTI Mirabox box (in various threads)
- Thanks Willy Tarreau for a very informative post about UART booting for Mirabox.
- Thanks whitepawn and tme (Trond Melen) for the testing efforts to bring up the Netgear RN102 box.


=======================================================================

Updated 06 Sept 2020:

Note: Please see this post and one after that for the latest DTB for the Mirabox and the RN102. These 2 DTBs have been modified (14 Nov 2020) after this kernel was released.

Download at Dropbox

linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2

md5:
17c3e1784dea18b2a3587a6ebb7aa894
sha256:
655646c0bd09b047b6c9ec198579cd2e345e19c5a8f32787a0979532a3b601d4

This tarball contains 6 files:

Quote

linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb
linux-headers-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb
zImage-5.8.5-mvebu-370xp-tld-1
config-5.8.5-mvebu-370xp-tld-1
linux-dtb-5.8.5-mvebu-370xp-tld-1.tar
linux-5.8.5-mvebu-370xp-tld-1.patch

And as always, please verify the hash of what you've downloaded!


Installation

Please scrolldown to the installation section for your box below.

I. Mirabox Intsallation (06 Sept 2020)
II. Netgear RN102 Intsallation (06 Sept 2020)


=======================================================================

I. Mirabox Intsallation
Updated 06 Sept 2020


Prerequiste

Serial console must be connected to perform the installation.

Installation Steps


A. Prepare rootfs on SD card (Using any Linux box)

1. Download rootfs Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 from the release thread and extract rootfs to an SD card (at least 4GB). See the release thread for instruction how to create rootfs.

2. Place the kernel tarball linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2 to the rootfs

Mount the rootfs Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2. Assuming the rootfs is mounted at /media/sdd1. Extract kernel files

mkdir -p /media/sdd1/usr/src/kernel
cd /media/sdd1/usr/src/kernel
Copy the downloaded linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2 to the current folder (/media/sdd1/usr/src/kernel).

And then extract it:
tar xf linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2

3. Make uImage for first boot

cd /media/sdd1/usr/src/kernel
tar -xvf linux-dtb-5.8.5-mvebu-370xp-tld-1.tar dts/armada-370-mirabox.dtb
cp -a zImage-5.8.5-mvebu-370xp-tld-1 zImage.fdt
cat dts/armada-370-mirabox.dtb >> zImage.fdt 
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.8.5-mvebu-370xp-tld-1 -d zImage.fdt uImage

4. Copy uImage to rootfs boot folder

cd /media/sdd1/boot
cp -a /media/sdd1/usr/src/kernel/uImage .
sync
sync
sync
Umount and remove the SD rootfs.

B. Boot the Mirabox with new kernel

1. Plug in the new SD roots to the external SD slot. Connect serial console. Power up and interrupt serial console at count down. And

printenv
Copy and paste the list of the envs from above command in a notepad. And then,
setenv set_bootargs_stock 'setenv bootargs "console=ttyS0,115200 $mtdparts ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs"'
setenv bootcmd_stock 'echo Booting Stock...; nand read 0x6400000 0x400000 0x400000; run set_bootargs_stock; bootm 0x6400000'
setenv load_image_addr 0x6400000
setenv load_initrd_addr 0x8400000
setenv load_uImage 'ext2load usb 1:1 $load_image_addr /boot/uImage'
setenv load_uInitrd 'ext2load usb 1:1 $load_initrd_addr /boot/uInitrd'
setenv set_bootargs_debian 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=pxa3xx_nand-0:4M(u-boot),4M(linux),-(filesystem) earlyprintk=serial'
setenv bootcmd_debian 'echo Booting Debian... ; usb start; run load_uImage; run load_uInitrd; run set_bootargs_debian; bootm $load_image_addr $load_initrd_addr'
setenv bootcmd 'run bootcmd_debian; run bootcmd_stock'

And then go ahead with booting to Debian
boot

2. Login using SSH or serial console with root/root credential

Find the Mirabox dynamic IP address in the network. Or try to ping its hostname
ping debian.local

Log in and check what kernel is running.
uname -a
Expect Output:
Linux version 5.8.5-mvebu-370xp-tld-1 (root@tldDebianVM) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0, GNU ld (GNU Binutils for Ubuntu) 2.30) #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020

At this point the system is running with the new kernel 5.8.5-mvebu-370xp-tld-1, but with older rootfs.

3. Install full kernel

cd /boot
cp -a uImage uImage.mirabox.bak
cp -a uInitrd uInitrd.bak    
dpkg -i /usr/src/kernel/linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb 
tar xf /usr/src/kernel/linux-dtb-5.8.5-mvebu-370xp-tld-1.tar 
cp -a /usr/src/kernel/zImage-5.8.5-mvebu-370xp-tld-1 .
cp -a zImage-5.8.5-mvebu-370xp-tld-1 zImage.fdt 
cat dts/armada-370-mirabox.dtb >> zImage.fdt 
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.8.5-mvebu-370xp-tld-1 -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.8.5-mvebu-370xp-tld-1 -d initrd.img-5.8.5-mvebu-370xp-tld-1 uInitrd

4. Setup envs for booting Debian permanently

a. Check NAND mtds
cat /proc/mtd
Expected Output:
dev:    size   erasesize  name
mtd0: 00400000 00080000 "u-boot"
mtd1: 00400000 00080000 "linux"
mtd2: 3f800000 00080000 "filesystem"

b. Set up envs area

echo "/dev/mtd0 0x100000 0x00080000 0x00080000" > /etc/fw_env.config

c. Do a sanilty check and then set the envs permanently

fw_setenv test_xxxx yes
fw_printenv test_xxxx
fw_printenv
Expected Output: If you can list the envs and they look like the envs listed in Step B.1 (with the additional test_xxxx env just set), then it's all checked out. If there is any error at this point then please stop and post question.

Go ahead set these permanently.
fw_setenv set_bootargs_stock 'setenv bootargs "console=ttyS0,115200 $mtdparts ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs"'
fw_setenv bootcmd_stock 'echo Booting Stock...; nand read 0x6400000 0x400000 0x400000; run set_bootargs_stock; bootm 0x6400000'
fw_setenv load_image_addr 0x6400000
fw_setenv load_initrd_addr 0x8400000
fw_setenv load_uImage 'ext2load usb 1:1 $load_image_addr /boot/uImage'
fw_setenv load_uInitrd 'ext2load usb 1:1 $load_initrd_addr /boot/uInitrd'
fw_setenv set_bootargs_debian 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=pxa3xx_nand-0:4M(u-boot),4M(linux),-(filesystem) earlyprintk=serial'
fw_setenv bootcmd_debian 'echo Booting Debian... ; usb start; run load_uImage; run load_uInitrd; run set_bootargs_debian; bootm $load_image_addr $load_initrd_addr'
fw_setenv bootcmd 'run bootcmd_debian; run bootcmd_stock'

And then print them again
fw_printenv
Copy and paster the envs to a notepad, for safe keeing.

5. Reboot

You are readdy to reboot the system.
sync
sync
sync
shutdown -r now


=======================================================================

II. Netgear RN102 Intsallation
Updated 06 Sept 2020


Prerequiste

Serial console must be connected to perform the installation.

Installation Steps


A. Prepare rootfs on USB drive (Using any Linux box)

1. Download rootfs Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2 from the release thread and extract rootfs to a USB drive (at least 4GB). See the release thread for instruction how to create rootfs.


2. Place the kernel tarball linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2 to the rootfs

Mount the rootfs Debian-5.2.9-mvebu-tld-1-rootfs-bodhi.tar.bz2. Assuming the rootfs is mounted at /media/sdd1. Extract kernel files

mkdir -p /media/sdd1/usr/src/kernel
cd /media/sdd1/usr/src/kernel
Copy the downloaded linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2 to the current folder (/media/sdd1/usr/src/kernel).


And then extract it:
tar xf linux-5.8.5-mvebu-370xp-tld-1-bodhi.tar.bz2


3. Make uImage for first boot

cd /media/sdd1/usr/src/kernel
tar -xvf linux-dtb-5.8.5-mvebu-370xp-tld-1.tar dts/armada-370-netgear-rn102.dtb
cp -a zImage-5.8.5-mvebu-370xp-tld-1 zImage.fdt
cat dts/armada-370-netgear-rn102.dtb >> zImage.fdt 
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.8.5-mvebu-370xp-tld-1 -d zImage.fdt uImage


4. Copy uImage to rootfs boot folder

cd /media/sdd1/boot
cp -a /media/sdd1/usr/src/kernel/uImage .
sync
sync
sync
Umount and remove the USB rootfs.


B. Boot the RN102 with new kernel

1. Plug in the new USB roots to the front USB port. Connect serial console. Power up and interrupt serial console at count down. And

printenv
Copy and paste the list of the envs from above command in a notepad. And then,
setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)'
setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial'
setenv load_uimage 'ext2load usb 0:1 0x2000000 /boot/uImage'
setenv load_uinitrd 'ext2load usb 0:1 0x3000000 /boot/uInitrd'
setenv usb_boot 'run load_uimage; if run load_uinitrd; then bootm 0x2000000 0x3000000; else bootm 0x2000000; fi'
setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset'
setenv fdt_skip_update yes


And then go ahead with booting to Debian
boot


2. Login using SSH or serial console with root/root credential

Find the RN102 dynamic IP address in the network. Or try to ping its hostname
ping debian.local

Log in and check what kernel is running.
uname -a
Expect Output:
Linux version 5.8.5-mvebu-370xp-tld-1 (root@tldDebianVM) (arm-linux-gnueabihf-gcc (Ubuntu/Linaro 7.5.0-3ubuntu1~18.04) 7.5.0, GNU ld (GNU Binutils for Ubuntu) 2.30) #1.0 SMP PREEMPT Mon Aug 31 00:00:32 PDT 2020


At this point the system is running with the new kernel 5.8.5-mvebu-370xp-tld-1, but with older rootfs.

3. Install full kernel

cd /boot
cp -a uImage uImage.RN102.bak
cp -a uInitrd uInitrd.bak    
dpkg -i /usr/src/kernel/linux-image-5.8.5-mvebu-370xp-tld-1_1.0_armhf.deb 
tar xf /usr/src/kernel/linux-dtb-5.8.5-mvebu-370xp-tld-1.tar 
cp -a /usr/src/kernel/zImage-5.8.5-mvebu-370xp-tld-1 .
cp -a zImage-5.8.5-mvebu-370xp-tld-1 zImage.fdt 
cat dts/armada-370-netgear-rn102.dtb >> zImage.fdt 
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-5.8.5-mvebu-370xp-tld-1 -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-5.8.5-mvebu-370xp-tld-1 -d initrd.img-5.8.5-mvebu-370xp-tld-1 uInitrd


4. Setup envs for booting Debian permanently

a. Check NAND mtds
cat /proc/mtd
Expected Output:
dev:    size   erasesize  name
dev:    size   erasesize  name
mtd0: 00180000 00020000 "u-boot"
mtd1: 00020000 00020000 "u-boot-env"
mtd2: 00600000 00020000 "uImage"
mtd3: 00400000 00020000 "minirootfs"
mtd4: 07400000 00020000 "ubifs"

b. Set up envs area

echo "/dev/mtd1 0x00000 0x20000 0x20000" > /etc/fw_env.config


c. Do a sanilty check and then set the envs permanently

fw_setenv test_xxxx yes
fw_printenv test_xxxx
fw_printenv
Expected Output: If you can list the envs and they look like the envs listed in Step B.1 (with the additional test_xxxx env just set), then it's all checked out. If there is any error at this point then please stop and post question.

Go ahead set these permanently.
fw_setenv mtdparts 'mtdparts=pxa3xx_nand-0:0x180000@0(u-boot),0x20000@0x180000(u-boot-env),0x600000@0x200000(uImage),0x400000@0x800000(minirootfs),-(ubifs)'
fw_setenv usb_set_bootargs 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 $mtdparts earlyprintk=serial'
fw_setenv load_uimage 'ext2load usb 0:1 0x2000000 /boot/uImage'
fw_setenv load_uinitrd 'ext2load usb 0:1 0x3000000 /boot/uInitrd'
fw_setenv usb_boot 'run load_uimage; if run load_uinitrd; then bootm 0x2000000 0x3000000; else bootm 0x2000000; fi'
fw_setenv usb_bootcmd 'run usb_set_bootargs; run usb_boot'
fw_setenv bootcmd 'usb start; run usb_bootcmd; usb stop; reset'
fw_setenv fdt_skip_update yes

And then print them again
fw_printenv
Copy and paster the envs to a notepad, for safe keeing.


5. Reboot

You are readdy to reboot the system.
sync
sync
sync
shutdown -r now


======== Old installation Instruction =================

I. Mirabox Intsallation


This Mirabox uses a special kernel version: linux-4.20.6-mvebu-mirabox-tld-12. Other MVEBU kernel will not work with this box.

Download at Dropbox

linux-4.20.6-mvebu-mirabox-tld-12-bodhi.tar.bz2

md5sum
8cf3d08dee09d000cf8b50b2df2f4047
sha256sum
fc4eb7a66e2af7f17f31041581fa6d106ba3da22ec643ab80a24aa352084f201

This tarball contains 6 files:

Quote

linux-image-4.20.6-mvebu-mirabox-tld-12_12.0_armhf.deb
linux-headers-4.20.6-mvebu-mirabox-tld-12_12.0_armhf.deb
zImage-4.20.6-mvebu-mirabox-tld-12
config-4.20.6-mvebu-mirabox-tld-12
linux-dtb-4.20.6-mvebu-mirabox-tld-12.tar
linux-4.20.6-mvebu-tld-1.patch


Prerequiste

Serial console must be connected to perform the installation.

Installation Steps


A. Prepare rootfs on SD card

1. Download rootfs Debian-4.12.4-mvebu-tld-1-rootfs-bodhi.tar.bz2 from the release thread and extract rootfs to an SD card (at least 4GB). See the release thread for instruction how to create rootfs.

2. Copy the download Mirabox kernel tarball linux-4.20.6-mvebu-mirabox-tld-12-bodhi.tar.bz2 to rootfs

Mount the rootfs. Assuming the rootfs is mounted at /media/sdd1. Extract kernel files

mkdir -p /media/sdd1/usr/src/mirabox
cd /media/sdd1/usr/src/mirabox
tar xf linux-4.20.6-mvebu-mirabox-tld-12-bodhi.tar.bz2

3. Make Mirabox uImage for first boot

cd /media/sdd1/usr/src/mirabox
tar -xvf linux-dtb-4.20.6-mvebu-mirabox-tld-12.tar dts/armada-370-mirabox.dtb
cp zImage-4.20.6-mvebu-mirabox-tld-12 zImage.fdt
cp -a zImage-4.20.6-mvebu-mirabox-tld-12 zImage.fdt
cat dts/armada-370-mirabox.dtb >> zImage.fdt 
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.20.6-mvebu-mirabox-tld-12 -d zImage.fdt uImage

4. Copy Mirabox uImage to rootfs boot folder

cd /media/sdd1/boot
cp -a uImage uImage.bak
cp -a /media/sdd1/usr/src/mirabox/uImage .
sync


B. Boot the Mirabox with new kernel

1. Plug in the new SD roots to the external SD slot. Connect serial console. Power up and interrupt serial console at count down. And

printenv
Copy and paste the list of the envs from above command in a notepad. And then,
setenv set_bootargs_stock 'setenv bootargs "console=ttyS0,115200 $mtdparts ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs"'
setenv bootcmd_stock 'echo Booting Stock...; nand read 0x6400000 0x400000 0x400000; run set_bootargs_stock; bootm 0x6400000'
setenv load_image_addr 0x6400000
setenv load_initrd_addr 0x8400000
setenv load_uImage 'ext2load usb 1:1 $load_image_addr /boot/uImage'
setenv load_uInitrd 'ext2load usb 1:1 $load_initrd_addr /boot/uInitrd'
setenv set_bootargs_debian 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=pxa3xx_nand-0:4M(u-boot),4M(linux),-(filesystem) earlyprintk=serial'
setenv bootcmd_debian 'echo Booting Debian... ; usb start; run load_uImage; run load_uInitrd; run set_bootargs_debian; bootm $load_image_addr $load_initrd_addr'
setenv bootcmd 'run bootcmd_debian; run bootcmd_stock'

And then go ahead with booting to Debian
boot

2. Login using SSH or serial console with root/root credential

Find the Mirabox dynamic IP address in the network. Or try to ping its hostname
ping debian.local

Log in and check what kernel is running.
uname -a
Expect Output:
Linux debian 4.20.6-mvebu-mirabox-tld-12 #6 SMP PREEMPT Wed Mar 13 14:43:16 PDT 2019 armv7l GNU/Linux

At this point the system is running with the new kernel 4.20.6-mvebu-mirabox-tld-12, but with older rootfs.

3. Install full kernel

cd /boot
cp -a uImage uImage.mirabox.bak
cp -a uInitrd uInitrd.bak    
dpkg -i /usr/src/mirabox/linux-image-4.20.6-mvebu-mirabox-tld-12_12.0_armhf.deb 
tar xf /usr/src/mirabox/linux-dtb-4.20.6-mvebu-mirabox-tld-12.tar 
cp -a /usr/src/mirabox/zImage-4.20.6-mvebu-mirabox-tld-12 .
cp -a zImage-4.20.6-mvebu-mirabox-tld-12 zImage.fdt 
cat dts/armada-370-mirabox.dtb >> zImage.fdt 
mkimage -A arm -O linux -T kernel -C none -a 0x00008000 -e 0x00008000 -n Linux-4.20.6-mvebu-mirabox-tld-12 -d zImage.fdt uImage
mkimage -A arm -O linux -T ramdisk -C gzip -a 0x00000000 -e 0x00000000 -n initramfs-4.20.6-mvebu-mirabox-tld-12 -d initrd.img-4.20.6-mvebu-mirabox-tld-12 uInitrd

4. Setup envs for booting Debian permanently

a. Check NAND mtds
cat /proc/mtd
Expected Output:
dev:    size   erasesize  name
mtd0: 00400000 00080000 "u-boot"
mtd1: 00400000 00080000 "linux"
mtd2: 3f800000 00080000 "filesystem"

b. Set up envs area

echo "/dev/mtd0 0x100000 0x00080000 0x00080000" > /etc/fw_env.config

c. Do a sanilty check and then set the envs permanently

fw_setenv test_xxxx yes
fw_printenv test_xxxx
fw_printenv
Expected Output: If you can list the envs and they look like the envs listed in Step B.1 (with the additional test_xxxx env just set), then it's all checked out. If there is any error at this point then please stop and post question.

Go ahead set these permanently.
fw_setenv set_bootargs_stock 'setenv bootargs "console=ttyS0,115200 $mtdparts ubi.mtd=2 root=ubi0:rootfs rootfstype=ubifs"'
fw_setenv bootcmd_stock 'echo Booting Stock...; nand read 0x6400000 0x400000 0x400000; run set_bootargs_stock; bootm 0x6400000'
fw_setenv load_image_addr 0x6400000
fw_setenv load_initrd_addr 0x8400000
fw_setenv load_uImage 'ext2load usb 1:1 $load_image_addr /boot/uImage'
fw_setenv load_uInitrd 'ext2load usb 1:1 $load_initrd_addr /boot/uInitrd'
fw_setenv set_bootargs_debian 'setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 mtdparts=pxa3xx_nand-0:4M(u-boot),4M(linux),-(filesystem) earlyprintk=serial'
fw_setenv bootcmd_debian 'echo Booting Debian... ; usb start; run load_uImage; run load_uInitrd; run set_bootargs_debian; bootm $load_image_addr $load_initrd_addr'
fw_setenv bootcmd 'run bootcmd_debian; run bootcmd_stock'

And then print them again
fw_printenv
Copy and paster the envs to a notepad, for safe keeing.

5. Reboot

You are readdy to reboot the system.
sync
shutdown -r now

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 9 time(s). Last edit at 11/14/2020 05:49PM by bodhi.
Re: Mirabox (Armada 370) Installation
November 17, 2019 04:52AM
This entry should probably mention that this firmware image will not work on newer versions of the Mirabox that have U-Boot on a 2MB SPI NOR chip and the OS on a 4GB eMMC on the USB bus. The unit I have also uses Realtek USB wifi instead of the Marvell on earlier units. The earlier units are powered by 5V and this later version uses 12V power. It would be nice to get a working DTS file for these later versions as they also have support for MSATA SSD. My earlier version has Mira_Box_II_V5-0-1 silkscreened on the bottom front of the circuit board while the newer version has Mira_Box_II_V9-1-1 silkscreened on the top of board near the Ethernet chips. Although Globalscale still offers the Mirabox for $149 they don't provide any source code and do not appear to respond to email requesting it.

P.S.
I do have my V5-0-1 version using this firmware booted from the microSD card.

Ray
Re: Mirabox (Armada 370) Installation
November 17, 2019 05:08AM
Ray,

> This entry should probably mention that this
> firmware image will not work on newer versions of
> the Mirabox that have U-Boot on a 2MB SPI NOR chip
> and the OS on a 4GB eMMC on the USB bus.

Thanks for the reminder!

> The unit
> I have also uses Realtek USB wifi instead of the
> Marvell on earlier units. The earlier units are
> powered by 5V and this later version uses 12V
> power.

> It would be nice to get a working DTS file
> for these later versions as they also have support
> for MSATA SSD.

It's probably not too difficult, we'll get back to that working thread and figure out a few more details.

> My earlier version has
> Mira_Box_II_V5-0-1 silkscreened on the bottom
> front of the circuit board while the newer version
> has Mira_Box_II_V9-1-1 silkscreened on the top of
> board near the Ethernet chips. Although
> Globalscale still offers the Mirabox for $149 they
> don't provide any source code and do not appear to
> respond to email requesting it.

Yes, Globalscale is not developer-friendly, to say the least!

Eventhough I think I will have an easier time building new u-boot for this box, I still prefer to struggle with the Thecus N2350 DDR4 issue, because of this reason, among many others.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: GTI Mirabox and Netgear RN120 (Armada 370) Installation
September 02, 2020 02:58AM
FYI,

I'm revising the Installation Instruction in the 1st post.

In the mean time, if you have already installed the last kernel version on Mirabox or Netgear RN102, you can upgrade now. Please see 1st post for download link.

-bodhi
===========================
Forum Wiki
bodhi's corner
Re: Mirabox (Armada 370) Installation
September 02, 2020 06:42PM
Ray,


> It would be nice to get a working DTS file
> for these later versions as they also have support
> for MSATA SSD. My earlier version has
> Mira_Box_II_V5-0-1 silkscreened on the bottom
> front of the circuit board while the newer version
> has Mira_Box_II_V9-1-1 silkscreened on the top of
> board near the Ethernet chips.

I believe this Mirabox V9 version should work with kernel linux-5.8.5-mvebu-tld-1.

Let me make a new V9 DTB version and you can try it sometime.

-bodhi
===========================
Forum Wiki
bodhi's corner



Edited 1 time(s). Last edit at 09/02/2020 06:43PM by bodhi.
Re: Mirabox (Armada 370) Installation
September 05, 2020 01:29AM
Hi Ray,

Here is the Mirabox V9 DTB and DTS.

-bodhi
===========================
Forum Wiki
bodhi's corner
Attachments:
open | download - armada-370-mirabox_v9.dtb (12.9 KB)
open | download - armada-370-mirabox_v9.dts (3.3 KB)
Author:

Your Email:


Subject:


Spam prevention:
Please, enter the code that you see below in the input field. This is for blocking bots that try to post this form automatically. If the code is hard to read, then just try to guess it right. If you enter the wrong code, a new image is created and you get another chance to enter it right.
Message: