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

52840 zigbee issues about "Production config is not present or invalid"

Hello Nordic Support.


it was first time i tried to set up zigbee project based on 52840 and nRF5_SDK_for_Thread_and_Zigbee_v3.0.0_d310e71. and now i got question...

firstly, i called the same api as demo shows in ble_zigbee_dynamic_door_lock_nus, excep ble part. then stack posted an error in zboss_signal_handler said "Production config is not present or invalid".

secondly, i called function bdb_start_top_level_commissioning(ZB_BDB_NETWORK_STEERING) to try to start scan network, but stack posted another error said "Failed to join network. Status: -1"

is that means i initialised zigbee stack incorrectly so that stack didn't set up in the begining? if so, please tell me what steps should i do?

Parents
  • Hi Geralt,

    Welcome to the world of Zigbee developement! The latest and greatest SDK for Thread and Zigbee is version 3.2.0 so I recommend you download it instead of v3.0.0.

    There is no production config stored in NVRAM in the example so that's why you will get the "Production config is not present or invalid" warning message. It has nothing to do with the initialization of the Zigbee stack.

    The "Failed to join network. Status: -1" means that the device has not joined any network. You should check if there is a network to join. The coordinator needs to open the network for joining, use 'bdb start' command after setting the coordinator role with 'bdb role zc' in the CLI example. Take a look at the documentation for the Door lock example.

    Best regards,

    Marjeris

Reply
  • Hi Geralt,

    Welcome to the world of Zigbee developement! The latest and greatest SDK for Thread and Zigbee is version 3.2.0 so I recommend you download it instead of v3.0.0.

    There is no production config stored in NVRAM in the example so that's why you will get the "Production config is not present or invalid" warning message. It has nothing to do with the initialization of the Zigbee stack.

    The "Failed to join network. Status: -1" means that the device has not joined any network. You should check if there is a network to join. The coordinator needs to open the network for joining, use 'bdb start' command after setting the coordinator role with 'bdb role zc' in the CLI example. Take a look at the documentation for the Door lock example.

    Best regards,

    Marjeris

Children
No Data
Related