anyway what you mean by "-3 version"??
also, i can't understand now what happen in serial when you power up!
Sorry, -3 = 3 versions back, which is the only file I can find on the tplink site that is without boot.
That was the one I used, thinking that since openwrt wants the image-only file, and the tp-link fw comes
in two versions (which the tplink code must accept) it would be safer to flash something where the bootloader
was NOT updated / modified (if it is in newer fw), and then update with the tplink, and let it do whatever it wanted
with the combined image.
The latest two versions are WITH boot, and if I strip the boot, I can see the header again, for the image in the first 20+ bytes.
0001 0000 T P - LINK .........
So the newer two versions seem to be just the image + boot concatenated. One question is WHY they supply the boot again,
has the bootloader changed, (bugfix, size of image, prevent loading of alien fw) ??
I guess there must be some documentation of the header somewhere...
About power up: When I did the (crude) serial interface I used a transistor for output. It was drivven by 10 k ohm from the TX pin.
This prevented the router from booting, i.e. I could not see any activity on the oscilloscope. I had to increase that value to 39k before
I got anything on the terminal. I first verified activity with the scope, then built the output IF to see what was happening, and got nothing.
So, I had to experiment with the values to get ANY output, and it does not have to do with drive capability, since with 10 k there is only
(3.3 -0.6 V)/10 k = 270 uA flowing. With this value there is NO activity on TX, with 39 k, abt 70 uA activity starts immediately. It seems the router
"senses" pin level before starting output, maybe checking it is not "shorted", or could be dual purpose pin.
And, minicom gave lots of little diamods with a ? in them, until Linux kernel boot messages. I first figured baud rate was wrong...
(Last edited by gulweb on 23 Nov 2012, 13:13)