OpenWrt Forum Archive

Topic: Kingston Mobilelite G2 (MLWG2)

The content of this topic has been archived between 18 Apr 2018 and 6 May 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.

Thanks for the input

One thing I am not clear on, and hopefully you can help is if the RJ-45 is configured as WAN, and I assume it defaults to DHCP, how does one connect to the device (with a cat-5 cable).  Is there still access somehow with Putty or WinSCP, and if so how?

I am afraid to configure my device (currently A HooToo TM-02) with RJ-45 as WAN for fear of locking myself out.

Can you clarify your DHCP comments.  Channel\frequency do not bother me.  I expect the speed to go in half.  Want different subnet and SSIDs. 

Re Startup, I want to address the issue you have in post 21, but not using external storage.

The micro usb to PC was a factory FW feature.  I expect it looks like a USB drive to the PC, but not sure.

Thanks for validating the model info.

RangerZ

Anyone managed to hook to the button events? I tried different approach (hotplug.d, rc.button) with no success. It doesn't seem like the button scripts are getting called.

I was never able to get the power button to work. I didn't try the reset because it is recessed. You may want to look over on the G1 forum, I think someone there posted getting it to work and they should be the same or at least really similar.

ldpinney wrote:

CannGramps : Did you do both the mtd writes ?

mtd_write write /media/USB1/openwrt-ramips-mt7620n-mlwg2-squashfs-sysupgrade.bin KernelA

mtd_write -r write /media/USB1/openwrt-ramips-mt7620n-mlwg2-squashfs-sysupgrade.bin KernelB

Since there are two partitions and 16MB flash, does that mean we're limited to 8MB OpenWRT images?

King0fK0ng wrote:

Since there are two partitions and 16MB flash, does that mean we're limited to 8MB OpenWRT images?

NO here is the filesystem layout copied from the OpenWrt Wiki page.

FACTORY :
Creating 6 MTD partitions on "raspi":
0x000000000000-0x000000030000 : "Bootloader"
0x000000030000-0x000000040000 : "Config"
0x000000040000-0x000000050000 : "Factory"
0x000000050000-0x000000800000 : "KernelA"    <----
0x000000800000-0x000000fb0000 : "KernelB"     <----
0x000000fb0000-0x000001000000 : "User_CFG

OpenWrt :
Creating 5 MTD partitions on "spi32766.0":
0x000000000000-0x000000030000 : "u-boot"
0x000000030000-0x000000040000 : "u-boot-env"
0x000000040000-0x000000050000 : "factory"
0x000000050000-0x000000fb0000 : "firmware"      <----
0x000000fb0000-0x000001000000 : "user-config

King0fK0ng wrote:
ldpinney wrote:

CannGramps : Did you do both the mtd writes ?

mtd_write write /media/USB1/openwrt-ramips-mt7620n-mlwg2-squashfs-sysupgrade.bin KernelA

mtd_write -r write /media/USB1/openwrt-ramips-mt7620n-mlwg2-squashfs-sysupgrade.bin KernelB

Since there are two partitions and 16MB flash, does that mean we're limited to 8MB OpenWRT images?

You have to update to OpenWRT with a Image smaller than 8MB otherwise you get an error from mtd_write and your Router is bricked after reboot. When your OpenWRT works you can update to a bigger Image file (16MB limit).


Also do not update to 2.0.0.6

(Last edited by HLK on 11 Aug 2015, 15:01)

Anyone noticed the problem with nvram_upgrade?

When you upgrade to 2.0.0.6 Kingston boots from KernelB

## Booting image at bc800000 ...

instead of booting from

## Booting image at bc050000 ...

When updating to OpenWRT via mtd_write works for the first boot until OpenWrt resize the partitions.
After a reboot the bootloader trys to boot from KernelB which does not exist anymore.

I tried to upgrade right after the first flash but sysupgrade does not change the CFG_KERN_ADDR to bc050000. Only tftpboot reset CFG_KERN_ADDR to bc050000.

Has anyone an idea where I can manipulate CFG_KERN_ADDR?

** I can not flash via serial (got 5 Devices, only one is for developing)

Anyone found a way to enter in failsafe without TTL to usb adapter ?

If you solder the header parallel to the board the case will close with it on, also the case will stay closed with the screw out. that means it is almost as quick to use the adapter as it is to power it up and use luci or ssh.

Just don't drop it at the airport because it will pop open and security will have questions about "extra wires and stuff"

HLK wrote:

Anyone noticed the problem with nvram_upgrade?

When you upgrade to 2.0.0.6 Kingston boots from KernelB

## Booting image at bc800000 ...

instead of booting from

## Booting image at bc050000 ...

When updating to OpenWRT via mtd_write works for the first boot until OpenWrt resize the partitions.
After a reboot the bootloader trys to boot from KernelB which does not exist anymore.

I tried to upgrade right after the first flash but sysupgrade does not change the CFG_KERN_ADDR to bc050000. Only tftpboot reset CFG_KERN_ADDR to bc050000.

Has anyone an idea where I can manipulate CFG_KERN_ADDR?

** I can not flash via serial (got 5 Devices, only one is for developing)

Found a way to upgrade to OpenWRT without the risk of wrong KERN_ADDR. (and without TTL to usb adapter) smile

Instructions will be online tomorrow.

How to update to OpenWRT after you applied a Kingston Update.

Problem:
Kingston uses a two Kernel System. After every update it will switches to the new one.
For example you got a new device with Kernel A active and apply the 2.0.0.6 update, the router will switch to Kernel B and starts at bc800000. When you upgrade now to OpenWRT the CFG_KERN_ADDR will stay at bc800000. So after first start of the new OpenWRT Kernel and a reboot you will get a bootloop.

Solution (works for me):

mtd_write write yourimage.bin KernelA
uboot_env setenv bootstate 0
reboot


bootstate is responsible for the CFG_KERN_ADD.

0 = booting at bc050000
2 = booting at bc800000

Always remember that the first update has to be smaller than 8mb.

(Last edited by HLK on 12 Aug 2015, 18:29)

HLK wrote:
King0fK0ng wrote:
ldpinney wrote:

CannGramps : Did you do both the mtd writes ?

mtd_write write /media/USB1/openwrt-ramips-mt7620n-mlwg2-squashfs-sysupgrade.bin KernelA

mtd_write -r write /media/USB1/openwrt-ramips-mt7620n-mlwg2-squashfs-sysupgrade.bin KernelB

Since there are two partitions and 16MB flash, does that mean we're limited to 8MB OpenWRT images?

You have to update to OpenWRT with a Image smaller than 8MB otherwise you get an error from mtd_write and your Router is bricked after reboot. When your OpenWRT works you can update to a bigger Image file (16MB limit).


Also do not update to 2.0.0.6

Thanks for the reply. Which image are you referring to that is "smaller than 8MB"? Is the CC RC3 image "smaller than 8MB"?

I plan to compile my own image. Will it be a 8MB or 16MB image?

[Edit] - I installed the unofficial image from the wiki and see 11MB free so I think I'm good. Please disregard the question.

(Last edited by King0fK0ng on 13 Aug 2015, 07:18)

d.wonderful wrote:

If you solder the header parallel to the board the case will close with it on, also the case will stay closed with the screw out. that means it is almost as quick to use the adapter as it is to power it up and use luci or ssh.

Just don't drop it at the airport because it will pop open and security will have questions about "extra wires and stuff"

How do you open this thing? What screws? I just received mine, but I don't see any screws. There are pictures of it opened, but no specific instructions on how to open it up.

ldpinney wrote:
King0fK0ng wrote:

Since there are two partitions and 16MB flash, does that mean we're limited to 8MB OpenWRT images?

NO here is the filesystem layout copied from the OpenWrt Wiki page.

FACTORY :
Creating 6 MTD partitions on "raspi":
0x000000000000-0x000000030000 : "Bootloader"
0x000000030000-0x000000040000 : "Config"
0x000000040000-0x000000050000 : "Factory"
0x000000050000-0x000000800000 : "KernelA"    <----
0x000000800000-0x000000fb0000 : "KernelB"     <----
0x000000fb0000-0x000001000000 : "User_CFG

OpenWrt :
Creating 5 MTD partitions on "spi32766.0":
0x000000000000-0x000000030000 : "u-boot"
0x000000030000-0x000000040000 : "u-boot-env"
0x000000040000-0x000000050000 : "factory"
0x000000050000-0x000000fb0000 : "firmware"      <----
0x000000fb0000-0x000001000000 : "user-config

I just installed the "unofficial" image linked from the wiki and see the mtd as listed with "firmware" partition.

Now I'm working on compiling my own image. I'm selecting "Default Profile" as there is no specific profile for the MLWG2. However during the build process I'm getting a "rootfs is too big" error, but it looks like it's from a different device.

LZMA 4.65 : Igor Pavlov : Public domain : 2009-02-03
/home/kk/MLWG2/trunk/staging_dir/host/bin/mktplinkfw2 -V "ver. 2.0" -B "ArcherC20i" -j -o /home/kk/MLWG2/trunk/build_dir/target-mipsel_24kec+dsp_musl-1.1.10/linux-ramips_mt7620/openwrt-ramips-mt7620-ArcherC20i-squashfs-sysupgrade.bin -k /home/kk/MLWG2/trunk/build_dir/target-mipsel_24kec+dsp_musl-1.1.10/linux-ramips_mt7620/vmlinux-squashfs.bin.lzma -r /home/kk/MLWG2/trunk/build_dir/target-mipsel_24kec+dsp_musl-1.1.10/linux-ramips_mt7620/root.squashfs
[mktplinkfw2] *** error: rootfs image is too big

The "openwrt-ramips-mt7620-mlwg2-squashfs-sysupgrade.bin" bin file is generated though, so I think I'm good.

Can I get confirmation since I don't have a serial connection yet since I can't figure out how to open it up yet?

How do I remove the "ArcherC20i" device from building?

Thanks

(Last edited by King0fK0ng on 13 Aug 2015, 07:19)

Put this file 'kingston.mk' in target/linux/ramips/mt7620/profiles

then 'make dirclean'

define Profile/MLW221
    NAME:=Kingston MLW221
    PACKAGES:= kmod-usb-core kmod-usb2 kmod-usb3 kmod-usb-ohci kmod-ledtrig-usbdev kmod-ledtrig-heartbeat \
        kmod-scsi-generic kmod-ledtrig-netdev kmod-fs-ext4 kmod-fs-msdos kmod-nls-cp437 kmod-nls-iso8859-1 \
        kmod-nls-utf8 block-mount luci wput nano shadow-common shadow-passwd

endef

define Profile/MLW221/Description
        Package set compatible with MLW221
endef
$(eval $(call Profile,MLW221))

define Profile/MLWG2
    NAME:=Kingston MLWG2
    PACKAGES:= kmod-usb-core kmod-usb2 kmod-usb3 kmod-usb-ohci kmod-ledtrig-usbdev kmod-ledtrig-heartbeat \
        kmod-scsi-generic kmod-ledtrig-netdev kmod-fs-ext4 kmod-fs-msdos kmod-nls-cp437 kmod-nls-iso8859-1 \
        kmod-nls-utf8 block-mount luci wput nano shadow-common shadow-passwd
endef

define Profile/MLWG2/Description
        Package set compatible with MLWG2
endef
$(eval $(call Profile,MLWG2))

King0fK0ng wrote:
ldpinney wrote:
King0fK0ng wrote:

Since there are two partitions and 16MB flash, does that mean we're limited to 8MB OpenWRT images?

NO here is the filesystem layout copied from the OpenWrt Wiki page.

FACTORY :
Creating 6 MTD partitions on "raspi":
0x000000000000-0x000000030000 : "Bootloader"
0x000000030000-0x000000040000 : "Config"
0x000000040000-0x000000050000 : "Factory"
0x000000050000-0x000000800000 : "KernelA"    <----
0x000000800000-0x000000fb0000 : "KernelB"     <----
0x000000fb0000-0x000001000000 : "User_CFG

OpenWrt :
Creating 5 MTD partitions on "spi32766.0":
0x000000000000-0x000000030000 : "u-boot"
0x000000030000-0x000000040000 : "u-boot-env"
0x000000040000-0x000000050000 : "factory"
0x000000050000-0x000000fb0000 : "firmware"      <----
0x000000fb0000-0x000001000000 : "user-config

I just installed the "unofficial" image linked from the wiki and see the mtd as listed with "firmware" partition.

Now I'm working on compiling my own image. I'm selecting "Default Profile" as there is no specific profile for the MLWG2. However during the build process I'm getting a "rootfs is too big" error, but it looks like it's from a different device.

LZMA 4.65 : Igor Pavlov : Public domain : 2009-02-03
/home/kk/MLWG2/trunk/staging_dir/host/bin/mktplinkfw2 -V "ver. 2.0" -B "ArcherC20i" -j -o /home/kk/MLWG2/trunk/build_dir/target-mipsel_24kec+dsp_musl-1.1.10/linux-ramips_mt7620/openwrt-ramips-mt7620-ArcherC20i-squashfs-sysupgrade.bin -k /home/kk/MLWG2/trunk/build_dir/target-mipsel_24kec+dsp_musl-1.1.10/linux-ramips_mt7620/vmlinux-squashfs.bin.lzma -r /home/kk/MLWG2/trunk/build_dir/target-mipsel_24kec+dsp_musl-1.1.10/linux-ramips_mt7620/root.squashfs
[mktplinkfw2] *** error: rootfs image is too big

The "openwrt-ramips-mt7620-mlwg2-squashfs-sysupgrade.bin" bin file is generated though, so I think I'm good.

Can I get confirmation since I don't have a serial connection yet since I can't figure out how to open it up yet?

How do I remove the "ArcherC20i" device from building?

Thanks


You can ignore that error. The image for the mlwg2 is build before ArcherC20i.

How do I remove the "ArcherC20i" device from building?
Thanks

I removed all other devices by editing /target/linux/ramips/image/Makefile.

Before:

#
850    # MT7620A Profiles
851    #
852    
853    Image/Build/Profile/E1700=$(call BuildFirmware/UMedia/$(1),$(1),e1700,E1700,0x013326)
854    Image/Build/Profile/MT7620a=$(call BuildFirmware/Default8M/$(1),$(1),mt7620a,MT7620a)
855    Image/Build/Profile/MT7620a_MT7610e=$(call BuildFirmware/Default8M/$(1),$(1),mt7620a_mt7610e,MT7620a_MT7610e)
856    Image/Build/Profile/MT7620a_MT7530=$(call BuildFirmware/Default8M/$(1),$(1),mt7620a_mt7530,MT7620a_MT7530)
857    Image/Build/Profile/MT7620a_V22SG=$(call BuildFirmware/Default8M/$(1),$(1),mt7620a_v22sg,MT7620a_V22SG)
858    br100_mtd_size=8126464
859    Image/Build/Profile/AIBR100=$(call BuildFirmware/CustomFlash/$(1),$(1),ai-br100,AIBR100,$(br100_mtd_size),Ai-BR)
860    Image/Build/Profile/RP-N53=$(call BuildFirmware/Default8M/$(1),$(1),rp_n53,RP-N53)
861    whr_300hp2_mtd_size=7012352
862    Image/Build/Profile/WHR300HP2=$(call BuildFirmware/CustomFlash/$(1),$(1),whr-300hp2,WHR-300HP2,$(whr_300hp2_mtd_size))
863    Image/Build/Profile/WHR600D=$(call BuildFirmware/CustomFlash/$(1),$(1),whr-600d,WHR-600D,$(whr_300hp2_mtd_size))
864    whr_1166d_mtd_size=15400960
865    Image/Build/Profile/WHR1166D=$(call BuildFirmware/CustomFlash/$(1),$(1),whr-1166d,WHR-1166D,$(whr_1166d_mtd_size))
866    dlink810l_mtd_size=6881280
867    Image/Build/Profile/CF-WR800N=$(call BuildFirmware/Default8M/$(1),$(1),cf-wr800n,CF-WR800N)
868    Image/Build/Profile/DIR-810L=$(call BuildFirmware/CustomFlash/$(1),$(1),dir-810l,DIR-810L,$(dlink810l_mtd_size))
869    na930_mtd_size=20971520
870    Image/Build/Profile/NA930=$(call BuildFirmware/CustomFlash/$(1),$(1),na930,NA930,$(na930_mtd_size))
871    Image/Build/Profile/MZK-750DHP=$(call BuildFirmware/Default8M/$(1),$(1),mzk-750dhp,MZK-750DHP)
872    Image/Build/Profile/OY-0001=$(call BuildFirmware/Default16M/$(1),$(1),oy-0001,OY-0001)
873    Image/Build/Profile/Y1=$(call BuildFirmware/Default16M/$(1),$(1),Lenovo-y1,Y1)
874    Image/Build/Profile/Y1S=$(call BuildFirmware/Default16M/$(1),$(1),Lenovo-y1s,Y1S)
875    Image/Build/Profile/MLW221=$(call BuildFirmware/Default16M/$(1),$(1),mlw221,MLW221)
876    Image/Build/Profile/MLWG2=$(call BuildFirmware/Default16M/$(1),$(1),mlwg2,MLWG2)
877    Image/Build/Profile/WMR300=$(call BuildFirmware/Default8M/$(1),$(1),wmr-300,WMR300)
878    Image/Build/Profile/RT-N14U=$(call BuildFirmware/Default8M/$(1),$(1),rt-n14u,RT-N14U)
879    Image/Build/Profile/WR8305RT=$(call BuildFirmware/Default8M/$(1),$(1),wr8305rt,WR8305RT)
880    Image/Build/Profile/WRTNODE=$(call BuildFirmware/Default16M/$(1),$(1),wrtnode,WRTNODE)
881    Image/Build/Profile/WT3020=$(call BuildFirmware/PorayDualSize/$(1),$(1),wt3020,WT3020)
882    Image/Build/Profile/XIAOMI-MIWIFI-MINI=$(call BuildFirmware/Default16M/$(1),$(1),xiaomi-miwifi-mini,XIAOMI-MIWIFI-MINI)
883    Image/Build/Profile/ZTE-Q7=$(call BuildFirmware/Default8M/$(1),$(1),zte-q7,ZTE-Q7)
884    Image/Build/Profile/ZBT-WA05=$(call BuildFirmware/Default8M/$(1),$(1),zbt-wa05,ZBT-WA05)
885    Image/Build/Profile/ArcherC20i=$(call BuildFirmware/Tplink/$(1),$(1),ArcherC20i,ArcherC20i)
886    microwrt_mtd_size=16515072
887    Image/Build/Profile/MicroWRT=$(call BuildFirmware/CustomFlash/$(1),$(1),microwrt,MicroWRT,$(microwrt_mtd_size))
888    
889    
890    ifeq ($(SUBTARGET),mt7620)
891    define Image/Build/Profile/Default
892            $(call Image/Build/Profile/E1700,$(1))
893            $(call Image/Build/Profile/MT7620a,$(1))
894            $(call Image/Build/Profile/MT7620a_MT7610e,$(1))
895            $(call Image/Build/Profile/MT7620a_MT7530,$(1))
896            $(call Image/Build/Profile/MT7620a_V22SG,$(1))
897            $(call Image/Build/Profile/AIBR100,$(1))
898            $(call Image/Build/Profile/CF-WR800N,$(1))
899            $(call Image/Build/Profile/RP-N53,$(1))
900            $(call Image/Build/Profile/DIR-810L,$(1))
901            $(call Image/Build/Profile/WHR300HP2,$(1))
902            $(call Image/Build/Profile/WHR600D,$(1))
903            $(call Image/Build/Profile/WHR1166D,$(1))
904            $(call Image/Build/Profile/MZK-750DHP,$(1))
905            $(call Image/Build/Profile/NA930,$(1))
906            $(call Image/Build/Profile/OY-0001,$(1))
907            $(call Image/Build/Profile/Y1,$(1))
908            $(call Image/Build/Profile/Y1S,$(1))
909            $(call Image/Build/Profile/MLW221,$(1))
910            $(call Image/Build/Profile/MLWG2,$(1))
911            $(call Image/Build/Profile/WMR300,$(1))
912            $(call Image/Build/Profile/RT-N14U,$(1))
913            $(call Image/Build/Profile/WR8305RT,$(1))
914            $(call Image/Build/Profile/WRTNODE,$(1))
915            $(call Image/Build/Profile/WT3020,$(1))
916            $(call Image/Build/Profile/XIAOMI-MIWIFI-MINI,$(1))
917            $(call Image/Build/Profile/ZTE-Q7,$(1))
918            $(call Image/Build/Profile/ZBT-WA05,$(1))
919            $(call Image/Build/Profile/ArcherC20i,$(1))
920            $(call Image/Build/Profile/MicroWRT,$(1))
921    endef
922    endif

After:

#
# MT7620A Profiles
#

Image/Build/Profile/E1700=$(call BuildFirmware/UMedia/$(1),$(1),e1700,E1700,0x013326)
Image/Build/Profile/MT7620a=$(call BuildFirmware/Default8M/$(1),$(1),mt7620a,MT7620a)
Image/Build/Profile/MT7620a_MT7610e=$(call BuildFirmware/Default8M/$(1),$(1),mt7620a_mt7610e,MT7620a_MT7610e)
Image/Build/Profile/MT7620a_MT7530=$(call BuildFirmware/Default8M/$(1),$(1),mt7620a_mt7530,MT7620a_MT7530)
Image/Build/Profile/MT7620a_V22SG=$(call BuildFirmware/Default8M/$(1),$(1),mt7620a_v22sg,MT7620a_V22SG)
br100_mtd_size=8126464
Image/Build/Profile/AIBR100=$(call BuildFirmware/CustomFlash/$(1),$(1),ai-br100,AIBR100,$(br100_mtd_size),Ai-BR)
Image/Build/Profile/RP-N53=$(call BuildFirmware/Default8M/$(1),$(1),rp_n53,RP-N53)
whr_300hp2_mtd_size=7012352
Image/Build/Profile/WHR300HP2=$(call BuildFirmware/CustomFlash/$(1),$(1),whr-300hp2,WHR-300HP2,$(whr_300hp2_mtd_size))
Image/Build/Profile/WHR600D=$(call BuildFirmware/CustomFlash/$(1),$(1),whr-600d,WHR-600D,$(whr_300hp2_mtd_size))
whr_1166d_mtd_size=15400960
Image/Build/Profile/WHR1166D=$(call BuildFirmware/CustomFlash/$(1),$(1),whr-1166d,WHR-1166D,$(whr_1166d_mtd_size))
dlink810l_mtd_size=6881280
Image/Build/Profile/CF-WR800N=$(call BuildFirmware/Default8M/$(1),$(1),cf-wr800n,CF-WR800N)
Image/Build/Profile/DIR-810L=$(call BuildFirmware/CustomFlash/$(1),$(1),dir-810l,DIR-810L,$(dlink810l_mtd_size))
na930_mtd_size=20971520
Image/Build/Profile/NA930=$(call BuildFirmware/CustomFlash/$(1),$(1),na930,NA930,$(na930_mtd_size))
Image/Build/Profile/MZK-750DHP=$(call BuildFirmware/Default8M/$(1),$(1),mzk-750dhp,MZK-750DHP)
Image/Build/Profile/OY-0001=$(call BuildFirmware/Default16M/$(1),$(1),oy-0001,OY-0001)
Image/Build/Profile/Y1=$(call BuildFirmware/Default16M/$(1),$(1),Lenovo-y1,Y1)
Image/Build/Profile/Y1S=$(call BuildFirmware/Default16M/$(1),$(1),Lenovo-y1s,Y1S)
Image/Build/Profile/MLW221=$(call BuildFirmware/Default16M/$(1),$(1),mlw221,MLW221)
Image/Build/Profile/MLWG2=$(call BuildFirmware/Default16M/$(1),$(1),mlwg2,MLWG2)
Image/Build/Profile/WMR300=$(call BuildFirmware/Default8M/$(1),$(1),wmr-300,WMR300)
Image/Build/Profile/RT-N14U=$(call BuildFirmware/Default8M/$(1),$(1),rt-n14u,RT-N14U)
Image/Build/Profile/WR8305RT=$(call BuildFirmware/Default8M/$(1),$(1),wr8305rt,WR8305RT)
Image/Build/Profile/WRTNODE=$(call BuildFirmware/Default16M/$(1),$(1),wrtnode,WRTNODE)
Image/Build/Profile/WT3020=$(call BuildFirmware/PorayDualSize/$(1),$(1),wt3020,WT3020)
Image/Build/Profile/XIAOMI-MIWIFI-MINI=$(call BuildFirmware/Default16M/$(1),$(1),xiaomi-miwifi-mini,XIAOMI-MIWIFI-MINI)
Image/Build/Profile/ZTE-Q7=$(call BuildFirmware/Default8M/$(1),$(1),zte-q7,ZTE-Q7)
Image/Build/Profile/ZBT-WA05=$(call BuildFirmware/Default8M/$(1),$(1),zbt-wa05,ZBT-WA05)
Image/Build/Profile/ArcherC20i=$(call BuildFirmware/Tplink/$(1),$(1),ArcherC20i,ArcherC20i)
microwrt_mtd_size=16515072
Image/Build/Profile/MicroWRT=$(call BuildFirmware/CustomFlash/$(1),$(1),microwrt,MicroWRT,$(microwrt_mtd_size))


ifeq ($(SUBTARGET),mt7620)
define Image/Build/Profile/Default
    $(call Image/Build/Profile/MLWG2,$(1))
endef
endif

Just remove all calls for other Images

(Last edited by HLK on 13 Aug 2015, 12:20)

King0fK0ng wrote:
d.wonderful wrote:

If you solder the header parallel to the board the case will close with it on, also the case will stay closed with the screw out. that means it is almost as quick to use the adapter as it is to power it up and use luci or ssh.

Just don't drop it at the airport because it will pop open and security will have questions about "extra wires and stuff"

How do you open this thing? What screws? I just received mine, but I don't see any screws. There are pictures of it opened, but no specific instructions on how to open it up.

Behind the label on the back are two screws.

Thank you @ldpinney and @HLK for the reply.

I figured out where the screws were late last night (luckily before I nearly broker the thing).

I got my serial connection wired up and working, which is great because the image I flashed was bad.

So now I need help recovering or reflashing this via serial connection. I selected "Load system code to SDRAM via TFTP." but not positive what file I should be using? Should it be "openwrt-ramips-mt7620-mlwg2-initramfs-uImage.bin"?


 ##### The CPU freq = 580 MHZ ####
 estimate memory size =64 Mbytes

Please choose the operation:
   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   7: Load Boot Loader code then write to Flash via Serial.
   9: Load Boot Loader code then write to Flash via TFTP.

You choosed 1
                                                                              0
raspi_read: from:40028 len:6


1: System Load Linux to SDRAM via TFTP.
 Please Input new ones /or Ctrl-C to discard
        Input device IP (192.168.200.1) ==:192.168.100.23
        Input server IP (192.168.200.10) ==:192.168.100.160
        Input Linux Kernel filename (root_uImage) ==:uImage2

 netboot_common, argc= 3

 NetTxPacket = 0x83FE4F80

 KSEG1ADDR(NetTxPacket) = 0xA3FE4F80

 NetLoop,call eth_halt !

 NetLoop,call eth_init !
Trying Eth0 (10/100-M)

 Waitting for RX_DMA_BUSY status Start... done


 ETH_STATE_ACTIVE!!
TFTP from server 192.168.100.160; our IP address is 192.168.100.23
Filename 'uImage2'.

 TIMEOUT_COUNT=10,Load address: 0x80a00000
Loading: Got ARP REPLY, set server/gtwy eth addr (00:25:31:04:a8:35)
Got it
Got ARP REQUEST, return our IP
T T

Please choose the operation:
   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.

1 = load the uImage.bin to RAM ... used to test without writing to FLASH

2 = load "factory" or "sysupgrade " to RAM then write it to FLASH

King0fK0ng wrote:

Thank you @ldpinney and @HLK for the reply.

I figured out where the screws were late last night (luckily before I nearly broker the thing).

I got my serial connection wired up and working, which is great because the image I flashed was bad.

So now I need help recovering or reflashing this via serial connection. I selected "Load system code to SDRAM via TFTP." but not positive what file I should be using? Should it be "openwrt-ramips-mt7620-mlwg2-initramfs-uImage.bin"?

 ##### The CPU freq = 580 MHZ ####
 estimate memory size =64 Mbytes

Please choose the operation:
   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   7: Load Boot Loader code then write to Flash via Serial.
   9: Load Boot Loader code then write to Flash via TFTP.

You choosed 1
                                                                              0
raspi_read: from:40028 len:6


1: System Load Linux to SDRAM via TFTP.
 Please Input new ones /or Ctrl-C to discard
        Input device IP (192.168.200.1) ==:192.168.100.23
        Input server IP (192.168.200.10) ==:192.168.100.160
        Input Linux Kernel filename (root_uImage) ==:uImage2

 netboot_common, argc= 3

 NetTxPacket = 0x83FE4F80

 KSEG1ADDR(NetTxPacket) = 0xA3FE4F80

 NetLoop,call eth_halt !

 NetLoop,call eth_init !
Trying Eth0 (10/100-M)

 Waitting for RX_DMA_BUSY status Start... done


 ETH_STATE_ACTIVE!!
TFTP from server 192.168.100.160; our IP address is 192.168.100.23
Filename 'uImage2'.

 TIMEOUT_COUNT=10,Load address: 0x80a00000
Loading: Got ARP REPLY, set server/gtwy eth addr (00:25:31:04:a8:35)
Got it
Got ARP REQUEST, return our IP
T T

I figured out my issue. I rebooted my tftp server but forgot to restart it afterwards.

Everything good now. Thank you.

Just got installed via usb, after reboot got the only green and blue (internet) lights on, no wifi no lan connect. Is it end?, and i have to go to buy USB-to-TTL dongle ? May i flash it under Windows via the serial console? If so please point out where to read through. Thank you very much!

blackysky wrote:

Just got installed via usb, after reboot got the only green and blue (internet) lights on, no wifi no lan connect. Is it end?, and i have to go to buy USB-to-TTL dongle ? May i flash it under Windows via the serial console? If so please point out where to read through. Thank you very much!

What image did you flash?

Here is my contribution smile

I originally flashed via USB using the "UN-Official Pre-Built Images" from the wiki - http://wiki.openwrt.org/toh/kingston/mlwg2. However currently I'm running Chaos Calmer RC3 - http://downloads.openwrt.org/chaos_calm … pgrade.bin

UN-Official Pre-Built Images

Install OpenWrt on your MLWG2 using a USB stick or SDcard. 
This has been tested by others… 
As Always…. Use at your own Peril! … No Warranty! 
USB/SDcard Factory to OpenWrt and OpenWrt to Factory Images. 
https://drive.google.com/open?id=0B0CKglNyN0URflpRWFMyWUFQa1dsRUJldlpoZTAtNGlHSTdJY041NGd2ZmRfSDRhNkNOSkU&authuser=0 
The OpenWrt Image has NO Password set! 
It has LuCI installed the WiFi is ENABLED by default and is set to "OpenWrt".

Below are a couple of missing pictures that I think would be helpful. Feel free to add to the wiki.

Serial Connection
Screws

For recovery via serial connection, pick option 1, Load system code to SDRAM via TFTP. Use the file, "openwrt-ramips-mt7620-mlwg2-initramfs-uImage.bin". Place file on your tftp server and rename it uImage. Not sure if this file is available from CC RC3 or other means, but I believe I built my own. After booting up with the initramfs image, you should be able to reflash CC RC3.

 ##### The CPU freq = 580 MHZ ####
 estimate memory size =64 Mbytes

Please choose the operation:
   1: Load system code to SDRAM via TFTP.
   2: Load system code then write to Flash via TFTP.
   3: Boot system code via Flash (default).
   4: Entr boot command line interface.
   7: Load Boot Loader code then write to Flash via Serial.
   9: Load Boot Loader code then write to Flash via TFTP.

You choosed 1
King0fK0ng wrote:
blackysky wrote:

Just got installed via usb, after reboot got the only green and blue (internet) lights on, no wifi no lan connect. Is it end?, and i have to go to buy USB-to-TTL dongle ? May i flash it under Windows via the serial console? If so please point out where to read through. Thank you very much!

What image did you flash?

Just downloaded from main page from gdrive, i.e. "openwrt-ramips-mt7620n-mlwg2-squashfs-sysupgrade.bin".
I did install via usb both KernelA-B as written in the txt file. It even boot once i saw all settings and then look internet and after reboot get this ...

(Last edited by blackysky on 18 Aug 2015, 23:32)