Debian on Action Tech SG200 and MI424WR-rev-I

Ray,

> Does it also automagically set the bootcmd?

No it does not. Every other envs are OK. Except bootdelay.

I've finished the mtds and envs configuration setting in Debian, will post that set up shortly.

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

By the way,

The GPL source we have (link in this thread)

https://forum.doozan.com/read.php?2,78499,78654#msg-78654
https://opensource.actiontec.com/sg200.html)

can only build the SG200 u-boot. The build scripts were not set up properly to build the MI4242WR-I box. Even that, the result SG200 u-boot binary is not usable.

That with the fact that the stock u-boot name is uboot-revI-128MbFlash.bin, I think the GPL is not up-to-date for MI4242WR.

I could not find how any of the build script can be used to build a binary named uboot-revI-128MbFlash.bin.

So there must be a build script for MI4242WR-I , but it is not in the GPL source.

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

bodhi,

https://opensource.actiontec.com/mi424wri.html

By the way, Verizon/Frontier used different firmware versions. Supposedly, Frontier had two Rev I units, one used 40.22.3.3 and the other used 52.0.7. The firmware were not interchangeable between the two units which suggests the use of slightly different hardware.

-budhi



Edited 10 time(s). Last edit at 02/13/2021 11:08PM by budhi.

budhi,

https://opensource.actiontec.com/mi424wri.html

Cool! Thanks for the info. That makes more sense :) hopefully I can find more info about the Ethernet Switch in this GPL. Everything else is easy, but the GPL switch info is a musthave to figure out how to write DTS correctly.

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

Wow; I didn't know they had two revisions of the Rev. I! I bet that's why they skipped straight from I to K (the gpl source for the google fiber network box refers to it as mi424wr rev k)

This also explains why a month ago, when I built the all firmwares from the actiontec gpl site you linked, I couldn't get any 5x firmware to boot, but the 4x firmwares all worked as expected. I guess that reveals which model I have.

Also, the U-Boot source code and config is distributed only with the 4x firmwares. I can't UART boot yet, but once I have that set up, I'll see if I can get the U-Boot source code to build, and if their config is portable to the a modern U-Boot.



Edited 1 time(s). Last edit at 02/14/2021 03:47PM by bkallus.

bkallus,

> and if their config is portable to the a modern
> U-Boot.

No, it is not. I've looked at the 5x FW briefly, it is the same as other Marvell u-boots. The information are valuable, though.

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



Edited 1 time(s). Last edit at 02/14/2021 04:25PM by bodhi.

Here to recap our current envs settings to boot Debian on USB. And also set up mtd partitions to allow u-boot envs read/write acess in Debian.

load_uimage=ext2load usb 0:1 0x800000 /boot/uImage
load_uinitrd=ext2load usb 0:1 0x2100000 /boot/uInitrd
usb_boot=echo Booting Debian ...; run load_uimage; run load_uinitrd; bootm 0x800000 0x2100000
usb_bootcmd=run usb_set_bootargs; run usb_boot
bootcmd_debian=usb start; run usb_bootcmd; usb stop; reset
bootcmd_stock=echo Booting Stock ...; ru jfs; ru jrun
mtdparts=mtdparts=orion_nand:2M(U-Boot),32M(JFFS2),80M(Firmware)
usb_set_bootargs=setenv bootargs console=ttyS0,115200 root=LABEL=rootfs rootdelay=10 ${mtdparts} earlyprintk=serial
bootcmd=run bootcmd_debian; run bootcmd_stock

Verify mtdparts in Debian:

# cat /proc/mtd

dev:    size   erasesize  name
mtd0: 00200000 00020000 "U-Boot"
mtd1: 02000000 00020000 "JFFS2"
mtd2: 05000000 00020000 "Firmware"

Set up envs area in Debian:

# cat /etc/fw_env.config

# MTD device name	Device offset	Env. size	Flash sector size	Number of sectors
/dev/mtd0		0xc0000		0x1000		0x20000

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



Edited 2 time(s). Last edit at 02/14/2021 05:08PM by bodhi.