joseangel wrote:I would recommend not getting into firmware development with no console connection and, if possibe, jtag interface ready to debrick your router.
Thanks for your advise joseangel.
I thought that TFTP-based flashing was part of something more basic than the main firmware, intergrated into the bootloader perhaps, because I had read the following from the openwrt installation guide:
Although you can install the firmware through more traditional means (via webpage), we recommend that you use TFTP for your first install. This is NOT a requirement, simply a damned good idea; if anything goes wrong you can just TFTP the old firmware back.
But from your post now I think that's not the case. What a shame. I've also seen the following remark on White Russian RC3 announcement:
If you use tftp or anything else, you will brick your router
which seems to agree with your remarks and contradict the first quote. Well, I'll get a serial cable then. I'll borrow one from wotk that I use for developing firmware for an ATA (Analog Telephone Adapter, to ethernet) which has a serial connector that looks like the one in my router. I hope is the same
I haven't used a JTAG before though, but for the looks of it (after a quick googleing) is not cheap, so I'll have to stick with serial.
joseangel wrote:On my ADSL2MUE I used the dd command from the shell of the official firmware to get exact copies of all mtd partitions so I could fix my mistakes easily. I succesfully used those binaries to recover from ADAM2/PSPBoot using the FTP upload to MTD way of firmware upgrade. To initially get those MTD ghost copies of official firmware transferred into my linux desktop computer I used scp command.
Thanks for mentioning dd. I'd have thought something more complicated was required and wasted time looking for it!
cesc