[Commotion-discuss] Help compiling for TL-WR1043N/ND v3

Nicolas North star at nikksno.io
Mon Aug 15 19:30:11 UTC 2016


Hi again Ben! 

Thank you so much for your reply 

Ok I see. However we might have a glimpse of hope with this little
suggestion I found on the TOH: 

HOW TO FLASH CHAOS CALMER (15.05) INTO THE V3 VERSION WITH THE V2
OPENWRT FACTORY FILE

Since there is another TP-Link software installed on the V3 version of
the router which does not accept the firmware file for the V2 version it
is not possible to install CC on it.
But there is a little trick to install it anyways. 

 	* 
Download the V2
version:https://downloads.openwrt.org/chaos_calmer/15.05/ar71xx/generic/openwrt-15.05-ar71xx-generic-tl-wr1043nd-v2-squashfs-factory.bin


	* 
Change with an Hex editor the version number in the header of the file
from 02 to 03 and save the file. It is located in byte 43.
 [2] 
command-line version for linux: 

 echo -e "\003" | dd seek=67 bs=1 count=1 conv=notrunc
of=firmware_file.bin
 	* 
Rename the file to "wr1043v3_tp_recovery.bin" and flash it via tftp how
described above 

Would this trick solve the issue even for the commotion firmware? If so,
how would I compile it? 

Thank you so much! Fingers crossed! :) 

Nicolas 

On 2016-08-15 20:50, Ben West wrote: 

> I've compiled OpenWRT trunk r49379 for the TL-WR1043N v3.  My
> understanding is that a trunk version is required for this device,
> i.e. can't flash it with BB or CC.
> 
> From prior experience compiling Commotion atop r3xxxx-era OpenWRT, I'd
> anticipate these specific difficulties:
> 
> - Compiling Commotion's luci packages atop recent OpenWRT trunk.  I
> think there is significant enough delta in the OpenWRT luci repo that
> current revisions won't compile cleanly with Commotion.
> - Compiling Commotion's olsr packages atop olsrd v0.9, which is now
> the version packaged with OpenWRT trunk.  Similar situation.
> - Dealing with Commotion libcyassl dependencies, since that package
> appears to be gradually phasing out in favor of libpolarssl as
> lightweight alternative to libopenssl.
> 
> Please note I can't offer availability in addressing these barriers to
> a clean compile, just sharing experience to help guide others.
> 
> On Sun, Aug 14, 2016 at 6:22 PM, Nicolas North <star at nikksno.io>
> wrote:
> 
>> Hi there!
>> 
>> I'm starting a mesh network project here in Milano, Italia, where I
>> live, and I already have 40 nodes up and running both outside and
>> inside
>> peoples' houses, with both commotion and a pure openwrt + olsrd
>> setup as
>> described on the Metamesh website. I intend to switch to a 100%
>> commotion network because of some potentially show stopping issues
>> I'm
>> encountering on Tplink routers with Metamesh's setup [I'm doing
>> something wrong I'm sure - more details below].
>> 
>> I WOULD IMMENSELY APPRECIATE ANY HELP IN GETTING COMMOTION COMPILED
>> FOR THE TP-LINK TL-WR1043N/ND V3 AND IF POSSIBLE THE TP-LINK ARCHER
>> C7 V2 [WHICH IS DUAL BAND AC SO I ONLY HAVE TWO OF THEM AS A TEST
>> FOR NOW].
>> 
>> In the past I was able to compile openwrt on a linux
>> vm with a lot of trial and error but was never able to access the
>> command line config menu for the commotion compiler. I also ran into
>> svn
>> tutorials for commotion but only ever found git repos. Also I don't
>> know
>> the specs to compile for my speficic hardware, are those available
>> on
>> the owrt toh? How can I avoid using the trunk version of openwrt if
>> there's no stable version listed for the WR1043N/ND v3? I have very
>> little experience with software compilation so
>> any help would be fantastic.
>> 
>> I've had a very lengthy back and forth conversation that started
>> here on
>> the list and then went private with Josh and Ben and Adam over at
>> Metamesh who have all been extremely nice and helpful and I thank
>> them
>> if the project is where it is today. But now I need your help in
>> ensuring this doesn't all just collapse in front of us because of
>> these
>> issues. For the record, Metamesh is amazing, Adam, has been great,
>> and
>> I'm sure their setup works, and I'm doing something wrong, but after
>> reading Josh's message about the future of commotion, I want all my
>> nodes on commotion for the future of the project.
>> 
>> ANY HELP IS OF VITAL IMPORTANTANCE FOR OUR PROJECT. ABOUT 100 PEOPLE
>> ARE
>> WAITING FOR THIS TO WORK EVERY DAY. PLEASE HELP. THANK YOU VERY
>> MUCH IN ADVANCE.
>> 
>> Nicolas
>> _______________________________________________
>> Commotion-discuss mailing list
>> Commotion-discuss at lists.chambana.net
>> https://lists.chambana.net/mailman/listinfo/commotion-discuss [1 [1]]
> 
> -- 
> 
> Ben West
> ben at gowasabi.net
> 
> Links:
> ------
> [1] https://lists.chambana.net/mailman/listinfo/commotion-discuss
 

Links:
------
[1] https://lists.chambana.net/mailman/listinfo/commotion-discuss
[2]
https://wiki.openwrt.org/_detail/media/tplink/tl-wr1043/tl-wr1043nd_version_nr_in_bin_header.jpg?id=toh%3Atp-link%3Atl-wr1043nd
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.chambana.net/pipermail/commotion-discuss/attachments/20160815/9f2f48ff/attachment-0001.html>


More information about the Commotion-discuss mailing list