HI, I have this router and I submitted this router's mach.
Have you noticed that the TPLINK-64K generates a U-Boot image for the kernel at first? The normal routine does not do that. So this firmware has two headers, first the tp-link header then the u-boot header. If the u-boot header disappear, the bootloader won't boot the firmware. Regards, Weijie 2015-10-31 21:47 GMT+08:00 Alexander Couzens <[email protected]>: > Hi Weijie, > > the old image also used mktplink. > Do you have a wdr6500? If so it would be nice if you can test the new > image. > > Best > lynxis > > old image code: > > $(eval $(call > SingleProfile,TPLINK-64K,64kraw,TLWDR6500V2,tl-wdr6500-v2,TL-WDR6500-v2,ttyS0,115200,0x65000002,1,8Mlzma)) > > define Image/Build/TPLINK-64K > -$(STAGING_DIR_HOST)/bin/mkimage \ > -A mips -O linux -T kernel -a 0x80060000 -C lzma \ > -e 0x80060000 -n 'MIPS OpenWrt Linux-$(LINUX_VERSION)' \ > -d $$(KDIR_TMP)/vmlinux-$(2).bin.lzma > $(KDIR_TMP)/vmlinux-$(2).bin.lzma.img > -$(STAGING_DIR_HOST)/bin/mktplinkfw \ > -H $(4) -W $(5) -F $(6) -N OpenWrt -m 2 -V $(REVISION) $(7) > \ > -X 0x20000 \ > -k $(KDIR_TMP)/vmlinux-$(2).bin.lzma.img \ > -r $(KDIR)/root.$(1) \ > -a $(call rootfs_align,$(1)) -j \ > -o $(call factoryname,$(1),$(2)) > -$(STAGING_DIR_HOST)/bin/mktplinkfw \ > -H $(4) -W $(5) -F $(6) -N OpenWrt -m 2 -V $(REVISION) $(7) > -s \ > -X 0x20000 \ > -k $(KDIR_TMP)/vmlinux-$(2).bin.lzma.img \ > -r $(KDIR)/root.$(1) \ > -a $(call rootfs_align,$(1)) -j \ > -o $(call sysupname,$(1),$(2)) > endef > > -- > Alexander Couzens > > mail: [email protected] > jabber: [email protected] > mobile: +4915123277221 > gpg: 390D CF78 8BF9 AA50 4F8F F1E2 C29E 9DA6 A0DF 8604 >
_______________________________________________ openwrt-devel mailing list [email protected] https://lists.openwrt.org/cgi-bin/mailman/listinfo/openwrt-devel
