Hi all,
regarding nprove.in:
I had the same problem, but on
http://main.lv/writeup/building_openwrt … 8196c.html
there is a note about that and a link to
http://git.advem.lv/
So to my "problem":
I was able (by replacing several URLs and other small stuff I don't remember) to get "everything" from there compiled.
And I have a serial connection to my Edimax 6200NL, so I can get access to the Bootloader.
(Sadly the original running system doesn't start a shell for the console when it is running...)
My current situation might be specific to my device, but I think it is a more general thing:
Currently I have stopped to try things, because I did not understand what would happen next!
I think TFTP to the device will work, but when I would do so: What file will I upload to the device?
The uImage of the kernel? I expect something else generated during the compile, but what?
Maybe it is explained somewhere, but then I did miss that piece of information...
I can't imagine I can upload the whole system, or will the tftp write directly to the flash memory?
So would I be able (for testing/repair?) to upload the original firmware that way?
If it is a complete firmware:
Do I have to provide an address or something to get the device boot my image?
There are specific offsets in the "original" firmware images, at least I found three parts and
their offsets in the original firmware files with binwalk...
Maybe it is even much simpler than tftp:
Currently I still have the original web interface, and I could use that firmware update:
But I never told the compiling process anything about my specific hardware:
I still expect I have missed one important thing.
Maybe "tomate" can light me up a bit, as he (she?) has successfully used the same deivce?
Thanks,
Baerle (also from Germany)