This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Adding Proxy GATT server to UART & mesh example

Hi,

Recently I came across this example which gives mesh & uart in single application. now i'm trying to add GATT proxy to it so that i can do provisioning via nrf mesh mobile app. I added GATT proxy but when i try to build it i'm facing the below issues.



can you tell me what was the issue and how can i fix it?

Parents
  • Hi. 

    I can see there is a lot of "undefined reference to x" errors. 
    Are you sure that you have included all the necessary files and headers to your project? 

    The ticket you referred to is using an older version of the nRF5 SDK for Mesh. In the new version of the nRF5 SDK for Mesh we already have a combined Mesh/UART example
    This coexist-example doesn't have proxy support either, but you can look at how this is done in the light switch examples. 

    Best regards, 
    Joakim

  • Sure, I'll check whether all files are included or not. If I get any update i'll reply here.

    Thanks for the reply by the way.

  • No problem. Happy to help! 

    Let me know if you have any further questions. 

    Also, make sure that the all the paths to the header files is also included in the "User include directories". 

Reply Children
  • Yeah i'll include in "User include directories" and build it again. I have one more doubt in UART Co-exist application to test it there are few steps one of them says

    Program the Light Switch example devices as described in the Light switch example, with the following exception:

    Replace the light switch client with examples/ble_peripheral/ble_app_uart_coexist/pca10040/s132/ses/Output/Release/Exe/ble_app_uart_pca10040_s132.hex.

    so how to replace the light switch client hex file, can you elaborate that for me, please

     

  • nithinkumarhere said:
    so how to replace the light switch client hex file, can you elaborate that for me, please

     Sure.
    "Program the Light Switch example devices as described..."
    If you were to test the light switch (LS) examples, you would need 3 devices.
    One for the LS server, one for the LS client and one for the LS provisioner (optionally the nRF Mesh app).

    However, when testing the co-exist example you would follow the same procedure; Flash one device with the LS server, one device with the static provisioner, but for the LS client you replace the light switch client with the co-exist example.

    Does that clear things up a bit?
    Note that the co-exist example doesn't have proxy support, so you can't use the nRF Mesh app, but you would need to use the static provisioner example. 

    Br, 
    Joakim

  • Very Much appreciated Jaakim! thanks for explaining clearly. Just now I checked the user includes everything is perfect but still facing the build problems as mentioned earlier.

    Any other advice?

  • There have been some issues with trailing whitespaces in the user include directories. You can double check that. 

    Also, make sure that you can actually find the functions in the included files. As the example in the referred post is from an older SDK, there could be some function mismatching if you are using functionality from a newer SDK. 

    Br, 
    Joakim

  • Okay Sure! Thanks for sharing that. I'll check that once again Thumbsup tone2