nRF52833: Zigbee Light Switch sample not building

Hello, 

I am attempting to build the Zigbee Light Switch sample on my nRF52833 DK, but the sample is generating an error every time I am attempting to build it. I have tried various combinations of settings in the build configurations but there always seems to be some error. I am attaching a file showing the terminal output (using the integrated terminal in the nRF for VSCode extension) while building and a screenshot of my build configuration in VSCode. 

I would greatly appreciate some help in this matter, thank you!

Parents
  • Hi, 

    Thank you to checking! 

    nandinee said:
    I am using the nRF Connect for VS Code extension with the nRF Connect SDK v2.4.0 

    Good to know!

    nandinee said:
    No, I did not change anything in the prj,conf of the project. 
    1. I did not change anything in the nrf52833dk-nrf52833.conf file either, and I just checked and saw that CONFIG_CRYPTO is set to 'y'.

    Hmm, interesting. Are you able to compile any other zigbee samples? How about any other non-zigbee samples, for instance the hello world sample?

    I do also see that the path used in the build log is '"c:\Users\nandi\Desktop\nrfProject\light_switch\build_1", do you know if this is outside of where you've installed the SDK?  The issue might be path related so could you try to compile a sample from the SDK? Use the "Open existing application", navigate to the Zigbee sample located in <ncs install location\v.2.4.0\nrf\samples\zigbee\zigbee_light_switch and build for nrf52833dk_nrf52833 or through commandline, whichever you prefer

    nandinee said:
    I believe I am working with a pristine SDK, but what is the method to confirm this? I am a beginner and still unclear on the exact meaning of these terminologies. 

    No worries, I understand how that could cause some confusion. When I refer to a "pristine SDK" I mean that if you have changed any configuration files or dependencies that samples depend on. By trying to build anything in a pristine sdk it excludes if the errors you've encountered is caused by changes or not

    This is not necessary the best solution, but one suggestion is to use a similar setup as mine 

    I have every version that I need to use installed in one location. Every v.x.x.x is one instance of the SDK that I have kept relatively pristine. 

    In my_projects I have the different projects that I have created by using "create new application from existing sample" and setting the Application location to a respective folder in my_projects.

    This way I can keep the samples as pristine as possible and modify them as I need outside of the SDK

    Let me know if you building within the SDK solves the issue or if you have any other questions throughout the process

    Kind regards,
    Andreas

Reply
  • Hi, 

    Thank you to checking! 

    nandinee said:
    I am using the nRF Connect for VS Code extension with the nRF Connect SDK v2.4.0 

    Good to know!

    nandinee said:
    No, I did not change anything in the prj,conf of the project. 
    1. I did not change anything in the nrf52833dk-nrf52833.conf file either, and I just checked and saw that CONFIG_CRYPTO is set to 'y'.

    Hmm, interesting. Are you able to compile any other zigbee samples? How about any other non-zigbee samples, for instance the hello world sample?

    I do also see that the path used in the build log is '"c:\Users\nandi\Desktop\nrfProject\light_switch\build_1", do you know if this is outside of where you've installed the SDK?  The issue might be path related so could you try to compile a sample from the SDK? Use the "Open existing application", navigate to the Zigbee sample located in <ncs install location\v.2.4.0\nrf\samples\zigbee\zigbee_light_switch and build for nrf52833dk_nrf52833 or through commandline, whichever you prefer

    nandinee said:
    I believe I am working with a pristine SDK, but what is the method to confirm this? I am a beginner and still unclear on the exact meaning of these terminologies. 

    No worries, I understand how that could cause some confusion. When I refer to a "pristine SDK" I mean that if you have changed any configuration files or dependencies that samples depend on. By trying to build anything in a pristine sdk it excludes if the errors you've encountered is caused by changes or not

    This is not necessary the best solution, but one suggestion is to use a similar setup as mine 

    I have every version that I need to use installed in one location. Every v.x.x.x is one instance of the SDK that I have kept relatively pristine. 

    In my_projects I have the different projects that I have created by using "create new application from existing sample" and setting the Application location to a respective folder in my_projects.

    This way I can keep the samples as pristine as possible and modify them as I need outside of the SDK

    Let me know if you building within the SDK solves the issue or if you have any other questions throughout the process

    Kind regards,
    Andreas

Children
No Data
Related