TP-Link TL-WR703N factory default has only 4MB of flash and 32MB RAM, if you want to play with the OP is simply powerless, so I changed the 8M Flash and 64M RAM.
First, modify the firmware size
OpenWrt in the compile time will be based on each model profile to generate the firmware, if the generated firmware integrated too much software and more than 4MB it will be error, you will find that the firmware can not be generated.
Specific symptoms See my last Post start compiling and compiling openwrt.
Compilation passed, but did not find the firmware in ./openwrt/bin/ , turned up the compile output prompt, and found a similar
- [mktplinkfw] kernel length aligned to 914864
- [mktplinkfw] *** error: images are too big
- make[3]: [install] Error 255 (ignored)
Here's how to modify the default firmware size of the TP series router
Actually very simple, find the
target/linux/ar71xx/image/Makefile, search for the model you want to modify, such as 703N, find the relevant 703N parameters
Then change the
tplink-4mlzma to
tplink-8mlzma on the line, and then
- define Device/tl-wr703n-v1
- $(Device/tplink-8mlzma)
- BOARDNAME := TL-WR703N
- DEVICE_PROFILE := TLWR703
- TPLINK_HWID := 0x07030101
- CONSOLE := ttyATH0,115200
- endef
After you save the exit, you can compile the 8M firmware for tl-wr703n.
Note: Some outdated tutorials on the web say that you also need to modify
tools/firmware-utils/src/mktplinkfw.c after I test, the latest source code inside this file is not about 703N and other router parameters, you do not need to modify.
II. Unlocking u-boot Partitions
The horse has the hoof, the person has the slip, does not have to die u-boot how dares the confidence to play the OP? Here we will talk about U-boot, U-boot is the embedded Linux system boot, equivalent to the computer BIOS. The traditional u-boot is only responsible for booting the firmware, once the firmware does not start, then the entire router is brick, there is a TTL is also easy, no one can only on the programmer. But there is not dead u-boot, in fact, with the Web Brush Machine interface U-boot, MA Ma no longer have to worry about my machine into bricks, completely without the demolition machine can save bricks. Want to know their own Google, recommended Enshan hackpascal breed, and brush into U-boot tutorial , I do not discuss how to use u-boot, mainly brush into the u-boot will encounter
- could not open mtd device ：u-boot ,can't open device for writing
This is because OpenWrt is locked by default, unless it is unlocked when the firmware is compiled. U-boot
Locate
/target/linux/ar71xx/files/drivers/mtd/tplinkpart.c, search for U-boot, find
- parts[0].name = "u-boot";
- parts[0].offset = 0;
- parts[0].size = offset;
- parts[0].mask_flags = MTD_WRITEABLE;
Then remove parts[0].mask_flags = MTD_WRITEABLE; This line will be recompiled.
WARM hint: TP series Brush finished breed must change the MAC address for a valid value, otherwise wireless will hang!
III. Add Fullflash partitions
Now the bricks can be saved, but save back the data are all gone, but also start the configuration, want to think all big ah, the good habit of nurturance is to fall roar! Add Fulllash partitions so that you can back up the entire programmer firmware with the DD command, and there is no such thing as an art loss.
Same as
/target/linux/ar71xx/files/drivers/mtd/tplinkpart.c to add the following code
- parts[5].name = "fullflash";
- parts[5].offset = 0;
- parts[5].size = master->size;
As shown in the figure
After recompiling and brushing, you can see the Fullflash partition.
View partitions with
cat /proc/mtd
Effect as shown
You can then simply back up the programmer firmware through the
dd if=/dev/mtd6 of=/tmp/fullflash.bin !
5aimiku
