Forums - CSRmeshv2.0.1 gateway execution error on TP Link wr1043ND v3

3 posts / 0 new
Last post
CSRmeshv2.0.1 gateway execution error on TP Link wr1043ND v3
Join Date: 30 Aug 16
Posts: 6
Posted: Mon, 2016-09-19 20:22

Hi All,

I bought a TP Link wr1043ND v3 board, no more sells TPLink v2 version in market,

Compiled CSRmeshv2.0.1 gateway as guided in "CS-332701-UG-12-CSRmesh Gateway South Bound User Guided.pdf" Appendix A,B,C

opkg install csrMeshGw_1_ar71xx.ipk and executed,

root@OpenWrt:/bin# ldd ./csrMeshGw

I have Error Message like :

Errro relocating ./csrmeshGw:_uClibc_main: symbol not found

Error relocating ./csrmeshGW: pthread_yield: symbol not found


Now we are thinking it seems like there are gcc compiler version mismatch.

1. TPLink wr1043ND v3 : when booting gcc version 5.3.0 (OpenWrt GCC 5.3.0)

2. But the image in document is compiled based on Openwrt SDK gcc version 4.8


Would you give me any guides to solve this issue ?




  • Up0
  • Down0
abarak Moderator
Join Date: 7 Jun 16
Posts: 13
Posted: Wed, 2016-10-19 08:33

You need to run Barrier Braker version of OpenWrt on your TP-Link as this is the only version supported at the moment.
In the document you specified, the recommended image to take is this one:
Problem: This image is for ver2 of the TP-Link and there is no Barrier Braker image for ver3!
Solution: As the Ver2 & Ver3 are the same HW, download this image anyway and use this tip:
(This tip is for Chaos Calmer but will also work for Barrier Braker)

  • Up0
  • Down0
Join Date: 30 Aug 16
Posts: 6
Posted: Tue, 2016-11-15 00:14

Hi, Moderator,

Thank you very much for above answer, your guide is much helpful.....


then I have another issue that I installed the CSRmeshv2.01 gateway SB,

but When I installed the csrmesh-gwnb package that referred from " CS-335804-UG-9-CSRmesh_Gateway_Build_and_Installation_User_Guide", page 13.

and found out the csrservicesd, I expected to work it with default Gateway configuration,

but it do not work as I expected

So Could you help me what is most important parameter that I change the settings, or have the other guides

My Question is that What we are missing below setting. would you give me some guide ?

Our Amazon cloud  server is URL =>


=our csrservicsd configuration==when it opended by vi edit=======================================

#gateway credentials

#Mesh daemon ip/port



#life time of transaction db records in minutes. This is an internal property

# and may not required to be changed frequently.


#timeout for multiple response in seconds


# Gateway supports multple type of web socket connection.

# Connection can be non-ssl, ssl using standard

# certificates, and self signed SSL certificate.

# Following are the identifier use by the system to identify the type of connection

# 0=ws, 1=wss, 2=wss-self-signed

# default value is non-ssl based connection. Change the setting as per your current system configuration.


# Web socket remote server address. Default value is empty. Please set the correct server address as communicated.

# Address can be in standard IP or in URL format as e.g In case, if empty value  is set or this property

# is removed from this config file then in both case communication betweeen cloud and gateway gets disabled, similar

# to below #cloud_conn_enabled = false property

# Web socket remote server port.


# System path specified at the server level. This shouldn't be changed untill communicated.


# This property enable or disable web socket communication between gateway device and cloud.

# If web socket communication is required, then set this property value to true, otherwise false.

# if this property set to false then any other connection or cloud properties defined in this optional get optional.


#Periodic ping message sent to remote server in a frequency set here. Default value is 50 seconds.


#cgi scheme


#cgi server port


#cgi base path


#gateway NB log level. Debug log level will have max logs.




  • Up0
  • Down0
or Register

Opinions expressed in the content posted here are the personal opinions of the original authors, and do not necessarily reflect those of Qualcomm Incorporated or its subsidiaries (“Qualcomm”). The content is provided for informational purposes only and is not meant to be an endorsement or representation by Qualcomm or any other party. This site may also provide links or references to non-Qualcomm sites and resources. Qualcomm makes no representations, warranties, or other commitments whatsoever about any non-Qualcomm sites or third-party resources that may be referenced, accessible from, or linked to this site.