• State Resolved
  • Locked Locked
  • Replies 4 replies
  • Subscribers 55 subscribers
  • Views 770 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.

ZNP does not start up when more than three endpoints are configured.

vincent hartman
Intellectual 750 points

Other Parts Discussed in Thread: Z-STACK, CC2530, MSP430F2274

When the End Device has a fourth End Point configured, the stack does not successfully start. The interesting part is that the AF_REGISTER appears to be successful for all four endpoints.  From the Mini Kit code comments it appears that up to 10 Endpoints can be configured for the standard ZNP image shipped with "swrc211a".

I will query the exact ZNP software build version, but for now, can you give me an indication if it is possible to configure multiple (more than three) endpoints on the t ZNP software build?

The stack does start successfully with three endpoints only.

  • 0
    TI__Genius 12415 points

    Hi Vincent,

    I just tried setting up multiple ZNPs with 5 endpoints and I see no problem, I can send and receive packets without any trouble. I tested this using Coordinator Router and End Device configurations on the ZNP and I am using Z-Stack Home 1.2.2.

    I have attached 2 hex images for the CC2530 mini kit built using HA 1.2.2 one with tc linkkey join and another one without it, let me know if these images work for you.

    CC2530-MK HA122.zip

  • 0 in reply to Hector_r
    Intellectual 750 points

    I will have to debug my application, it appears that the stack is restarted at a timer expiry in my Application which causes a message to be broadcast. It is in somewhere there that the stack restarts. Will provide feeback by tonight.

    Some feedback on the firmware images:
    With Pro-Secure_HA122.hex loaded my normal messaging from endpoints to coordinator does work.

    The Pro-Secure_HA122.hex causes all three devices I loaded to have the same MAC address. I then connect the FlashProgrammer and query the MAC - whe2e.ti.com/.../431792 then does display the correct (original) MAC.

    The LinkKeyJoin_HA122.hex allows normal messaging between endpoints and coordinator. I am keeping it loaded for now.

  • 0 in reply to vincent hartman
    Intellectual 750 points
    Thanks for the checking on your side. I am going to Verify this one based on the fact that it appears my problem lies elsewhere (in the application code).
  • 0 in reply to Hector_r
    Intellectual 750 points

    Hi, I have managed to improve but not fix the multiple endpoint issues I have on the Mini Kit.

    The symptoms currently are  that

    With 4 endpoints defined, the ZNP starts, the applications processor can do interrupt routines everything works fine ito  Zigbee messaging, bindings etc.

    With 5 endpoints defined, the ZNP starts successfully, Zigbee messaging, bindings etc work fine - but, as soon as the applications processor does an interrupt routine (I have interrupt handlers setup for port2 of the MSP430F2274), the application restarts. This restart may be initiated by the ZNP, but I am not sure of that. What I can confirm is that when the ZNP is not started, the application processor handles all it's interrupts correctly.

    I did a serial port msp430-gdb trace:

    The application processor going into the WDT immediately after an IO interrupt was received. I am debugging under msp430-gdb over USB, please look at the trace below.

    Breakpoint 1, PORT2_ISR () at ../HAL/hal_cc2530znp_target_board.c:131
    131 irSwitch2();
    (gdb) step
    _reset_vector__ () at ../../gcc-4.6.3/gcc/config/msp430/crt0.S:105
    105 mov.b &__WDTCTL, r5
    (gdb) step
    106 bis #0x5a08, r5
    (gdb) step
    107 mov r5, &__wdt_clear_value

    The peculiar part is that, once the app restarted, it appears that the interrupt handler function completes. The next interrupt will then cause a repeat of this.

    With 6 endpoints defined, the application continuously restarts at the configuration of the first endpoint.

    I would appreciate your comments.