777L @ 09/18/2014, 12:25
IMHO, you need to find a way to unpack - package the firmware. Here is an article about adsl 831 - there a person just wrote a compiler-decompiler
http://robocraft.ru/blog/electronics/410.html. I lack the knowledge to do this.
You won’t believe - now I have exactly this device on the table and I’m smoking this article exactly (while I’m reading about what JTAG is in the context of my bricked F660).
But I smoke it in a different direction:
- there CFE is almost the same
- from it I [almost] did what I wanted to do with the F660: I took the kernel from OpenWRT and loaded it on the ZTE831 [via tftp / with console cable]. Which, of course, is not supported, it knows such a percent (BCM6338), but at first it swore at the Unknown Board.
Ha, shchaz. His CFE can change the ID board to some prefedined list, it seems to put something out there with digits and buoys SV, and since we have Linux open source ;-) (and I was too lazy to assemble the toolchain and then honestly rebuild the kernel) patched the linux kernel binar from OpenWRT (after reading in the source what they generally are and which line is more convenient to patch ;-))
- and the kernel booted! Of course, it swore at the file system and the breakdown of mtd blocks and hung, respectively, as expected.
How would I do this on the F660 - happiness would be almost achievable, but the CFE Boot prevents it from slipping kernel parameters. Neither register in env, nor even temporary. For then [well, back then] I would load the kernel with tftp, and I would palm / dev / sda into it, that is, a USB flash drive.
In short, the default command line must be written to the kernel during assembly. Since 831 I had to drag the whole OpenWRT tree, now it compiles, first let it spawn a couple, and then I will generate a custom kernel. In the context of the F660, I’ll at least get a hand on this.