Turns out the firmware from tp-link includes a boot loader that must be removed before using mtd (true for all images with "boot" in the name). Too bad I did that operation on the device and filled up the RAM. BRICK!
Anyone else using the instructions I linked above beware. You need to clip off the front of tp-link "boot" images to get the size to 3,932,160. If your bin is already this size then don't do this.
Instead, if you have unix tools on your PC you can do:
dd if=orig.bin of=tplink.bin skip=257 bs=512
Where 'orig.bin' is the tp-link "boot" image and 'tplink.bin' is what you will copy to the router for mtd'ing.
you will need a TTL (3.3V) Serial interface, not JTAG!
anyway usually with "fresh" setup and 32 MB RAM you have at least 10 MB RAM free, so enough to store 2 firmware files (on routers with 4MB flash..)
obviously if you try that more than one time without removing other fw images from /tmp you fill it..
Turns out the firmware from tp-link includes a boot loader that must be removed before using mtd (true for all images with "boot" in the name). Too bad I did that operation on the device and filled up the RAM. BRICK!
Anyone else using the instructions I linked above beware. You need to clip off the front of tp-link "boot" images to get the size to 3,932,160. If your bin is already this size then don't do this.
Instead, if you have unix tools on your PC you can do:
dd if=orig.bin of=tplink.bin skip=257 bs=512
Where 'orig.bin' is the tp-link "boot" image and 'tplink.bin' is what you will copy to the router for mtd'ing.
10 MB RAM free, so enough to store 2 firmware files (on routers with 4MB flash..)
I know what you mean but as soon as I made the second image with dd I could no longer run any commands in the shell I had open. 'ls' would respond 'Invalid command'. The web interface was still responsive but new ssh sessions would also die after login when trying to start the shell.
Oh well. Easier to send it back as defective than build a serial cable.
Turns out the firmware from tp-link includes a boot loader that must be removed before using mtd (true for all images with "boot" in the name). Too bad I did that operation on the device and filled up the RAM. BRICK!
Anyone else using the instructions I linked above beware. You need to clip off the front of tp-link "boot" images to get the size to 3,932,160. If your bin is already this size then don't do this.
Instead, if you have unix tools on your PC you can do:
dd if=orig.bin of=tplink.bin skip=257 bs=512
Where 'orig.bin' is the tp-link "boot" image and 'tplink.bin' is what you will copy to the router for mtd'ing.
Turns out the firmware from tp-link includes a boot loader that must be removed before using mtd (true for all images with "boot" in the name). Too bad I did that operation on the device and filled up the RAM. BRICK!
Anyone else using the instructions I linked above beware. You need to clip off the front of tp-link "boot" images to get the size to 3,932,160. If your bin is already this size then don't do this.
Instead, if you have unix tools on your PC you can do:
dd if=orig.bin of=tplink.bin skip=257 bs=512
Where 'orig.bin' is the tp-link "boot" image and 'tplink.bin' is what you will copy to the router for mtd'ing.
