• State Resolved
  • Locked Locked
  • Replies 2 replies
  • Subscribers 16 subscribers
  • Views 544 views
  • Users 0 members are here
Support feedback
Options
Options
Related

This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

cc2530 simple collector failure Z-stack

dreamer
Prodigy 150 points
Other Parts Discussed in Thread: Z-STACK

Dear experts,

I'm experiencing problems using Z-stack simple application as a starting point on my development. I made a custom board  to satisfy the application requirements. I'm using an IAR workbench ve. 8.20.2 with the latest stack. When I open the project at first time it converts it to an openable version for the workbench. I made some modifications in hal_board_cfg file (LEDs, buttons etc). On debugging I realised after calling the zb_StartRequest the zb_StartConfirm was never called. I have found intresting that, the application tries to config the device as  an end_device at the factory preprocessor settings. I pushed the correct button to configure the device as a coordinator, the zb_startrequest called and the zb_startconfirm will be never called back. What could be the problem?
Thank you for advance!

other q!
How can I configure the stack to start a device independently as a coordinator or an enddevice?
 

  • 0
    Prodigy 140 points

    I have same problem. Does anyone have solution?

  • 0 in reply to ozgun gunay
    Prodigy 150 points

    I realised that, the reconfigured button state in hal_board_cfg.h was ACTIVE_LOW and the button worked the opposite ACTIVE_HIGH state, that means the mcu sensed  "pressed" state at every time. There is a button read at every zigbee stack start up, and if an appropriate button are pressed in this time, the stack will go in "hold state". Other thing is the button configuration must be configured in key hal inits functions too, it is not enough to overwrite the hal_board_cfg.h file!