• State Resolved
  • Locked Locked
  • Replies 99 replies
  • Answers 3 answers
  • Subscribers 56 subscribers
  • Views 5988 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

LAUNCHXL-CC2650: Documentation and Examples Zigbee

Angel Rodriguez43
Intellectual 595 points
Part Number: LAUNCHXL-CC2650
Other Parts Discussed in Thread: CC2531, CC2650, SYSBIOS, TIMAC, Z-STACK, , CC2531EMK, CC2538, CC2530, CC2560

Hi,

I just bought 5 LauchXL-CC2650 and 1 CC2531 dongle.

This project is for academic purpose, I want to connect the 5 cc2650 board using zigbee and the cc2531 as a sniffer to see all the packages that they are sending.

I look for zigbee examples but with all the information around I'm lost. I don't have much time and I was wondering if you could point me to the right direction.

I just want to send packages to each other, is there any example that it does that. If it exist where can I find it and how can I used it.

I download the z stack home automation 1.2.2 and the IAR, but can I used the limited size licence or do I need the other one?

Thank you

  • 0
    Guru 735455 points
    CC2650 doesn’t have enough RAM/Flash to run Zigbee Coordinator or Router in SOC mode so you have to run CC2650 as ZNP mode to act as coordinator to form Zigbee network. For ZNP, you will need an extra MCU to run ZAP or you can use PC with ZTool to act as ZAP. You can refer to sunmaysky.blogspot.co.uk/.../setup-zigbee-ha-coordinator-with-ti.html to know how to use ZTool to setup a coordinator.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    Thank you for the replay,
    To use it as ZNP does I need any special configuration on IAR? Also do I need the full licence of with the trial the size is not a problem?

    Thank you and Regards
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    No special configuration is required on IAR. You need full IAR license to build ZNP example but you can use trial version for evaluation first.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    Hi Yk chen,

    When I try to compile and Run the ZPN I get this error.
    Could you help me?

    Regards!

    Error while running "c:\ti\xdctools_3_30_06_67_core/xs" --xdcpath="C:\ti\tirtos_simplelink_2_11_01_09\packages;C:\ti\tirtos_simplelink_2_11_01_09\
    products\bios_6_41_02_41\packages;C:\ti\tirtos_simplelink_2_11_01_09\products\cc26xxware_2_20_06_14829\inc;C:\ti\tirtos_simplelink_2_11_01_09\
    products\cc26xxware_2_20_06_14829\driverlib;C:\ti\tirtos_simplelink_2_11_01_09\products\cc26xxware_2_20_06_14829" iar.tools.configuro -c "C:\Program
    Files (x86)\IAR Systems\Embedded Workbench 8.0\arm" --cc "C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.0\arm\bin\iccarm.exe"
    --device "CC2650F128" --compileOptions "dummy.c -D ewarm -D FLASH_ROM_BUILD -D USE_ICALL -D HEAPMGR_SIZE=6500 -D
    FEATURE_MAC_SECURITY -D FEATURE_GREEN_POWER -D FEATURE_ENHANCED_BEACON -D
    ICALL_HOOK_ABORT_FUNC=halAssertHandler -D CC26XX -D xdc_runtime_Log_DISABLE_ALL -D xdc_runtime_Assert_DISABLE_ALL -D
    MODULE_CC26XX_7X7 -D xMODULE_CC26XX_5X5 -D xMODULE_CC26XX_4X4 -D ZDO_API_ADVANCED -D HAL_ASSERT_SPIN -D NEAR_FUNC= -D
    DATA= -D FEATURE_SYSTEM_STATS -D ZDNWKMGR_MIN_TRANSMISSIONS=0 -D SECURE=1 -D TC_LINKKEY_JOIN -D
    DSECMGR_TC_DEVICE_MAX=16 -D HOLD_AUTO_START -D ROM_SBL -D FEATURE_NVEXID -D NPI -D NPI_SREQRSP -D NPI_USE_UART -D
    NPI_UART_BR=115200 --diag_suppress pa050 -o C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx\
    EndDevice-Pro_Secure_Link_Key_Join\Obj --debug --endian=little --cpu=Cortex-M3 -f C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\
    ZNP\CC26xx\znp.cfg -f C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx\..\..\Tools\CC26xx\znp_f8wConfig.cfg -f C:\ti\simplelink\
    zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx\..\..\Tools\CC26xx\f8wEndev.cfg -f C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\
    zstack\ZNP\CC26xx/configPkg/compiler.opt.defs --aeabi -e --fpu=None --dlib_config \"C:\Program Files (x86)\IAR Systems\Embedded Workbench 8.0\
    arm\INC\c\DLib_Config_Normal.h\" --preinclude C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../tools/CC26xx_Tracer/dbg.h -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx\ -I C:\ti\simplelink\
    zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/StackTask\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/AppTask\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Projects/zstack/common/CC26xx/SmartRF06\ -I
    C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/npi\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\
    Projects\zstack\ZNP\CC26xx/../../../../Components/mt\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/mt/icall\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/stack/icall\ -I C:\ti\
    simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/stack/icall/client\ -I C:\ti\simplelink\
    zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/applib/heap\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\
    zstack\ZNP\CC26xx/../../../../Components/hal/include\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/hal/target/_common/cc26xx\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/hal/target/CC2650/rom\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/hal/target/CC2650TIRTOS\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/osal/include\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/services/sdata\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/services/saddr\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/services/nv\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/services/nv/cc26xx\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/services/aes\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/icall/include\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/mac/include\
    -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/mac/include/cc26xx\ -I C:\ti\simplelink\
    zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/mac/high_level\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\
    Projects\zstack\ZNP\CC26xx/../../../../Components/mac/low_level/cc26xx\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/mac/low_level/cc26xx/ROM_Support\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/mac/low_level/cc26xx/CM0_Patch\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/stack/icall\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/stack/zdo\ -I C:\
    ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/stack/af\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\
    Projects\zstack\ZNP\CC26xx/../../../../Components/stack/nwk\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/stack/sec\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/stack/sys\ -I C:\
    ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/stack/sapi\ -I C:\ti\simplelink\
    zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../../../Components/zmac\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\
    ZNP\CC26xx/../../../../Components/zmac/f8w\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Components/mac/include\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\
    CC26xx/../../../../Projects/zstack/ZNP/Source\ -I C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/../../common/CC26xx\ -I C:\ti\
    tirtos_simplelink_2_11_01_09\products\cc26xxware_2_20_06_14829/\ -I C:\ti\tirtos_simplelink_2_11_01_09\products\cc26xxware_2_20_06_14829/inc\ -I C:\ti\
    tirtos_simplelink_2_11_01_09\products\cc26xxware_2_20_06_14829/driverlib\ -Ohz" --linkOptions "-o C:\ti\simplelink\zstack_home_1_02_02a_44539\
    Projects\zstack\ZNP\CC26xx\EndDevice-Pro_Secure_Link_Key_Join\Exe\znp_enddev_pro_secure_linkkeyjoin.out --config_def CC2650=1 --config_def
    USE_SYSBIOS_IN_ROM=1 --config_def FLASH_ROM_BUILD=1 --map C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx\
    EndDevice-Pro_Secure_Link_Key_Join\List\znp_enddev_pro_secure_linkkeyjoin.map --config C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\
    zstack\ZNP\CC26xx\cc26xx_app_stack_combined.icf -f C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx/configPkg/linker.cmd
    --keep __vector_table --semihosting C:\ti\tirtos_simplelink_2_11_01_09\products\cc26xxware_2_20_06_14829/driverlib/bin/iar/driverlib.lib C:\ti\simplelink\
    zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx\..\..\Libraries\CC26xx\bin\EndDevice.a C:\ti\simplelink\zstack_home_1_02_02a_44539\
    Projects\zstack\ZNP\CC26xx\..\..\..\..\Projects\common\TIMAC_ROM_Release\03282014\timac_rom_PATCH.symbols --entry __iar_program_start --vfe
    --text_out locale" --profile release --projFile "C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\ZNP\CC26xx\znp.ewp"
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    Which IAR version do you use?
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    Iar Embedded workbench for ARM 8.22.2.15996
    Iar Embedded workbench share components 8.0.15.5379
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    The CC2650 examples of Z-Stack home 1.2.2a is built by IAR EWARM 7.40 so I suggest you to use the same version.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    Thank you, I will try then with that version.
    I have another question in this link: sunmaysky.blogspot.mx/.../setup-zigbee-ha-coordinator-with-ti.html
    The .hex where can I get it and how do I downloaded to the cc2531

    Regards
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    Don’t you use LAUNCHXL-CC2650? If so, you should download ZNP to LAUNCHXL-CC2650 and use it to replace CC2531 ZNP.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    Yes, but I need the CC2531 for the coordinator right?

    Thank you
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    Actually, you can run ZNP on LAUNCHXL-CC2650 to work with ZTool to act as coordinator.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    Ok, but I also need to sniffer the packages.
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    If you have CC2531 USB dongle, you can use it with Ubiqua Protocol Analyzer to sniffer the packages.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    Great! And do I need to put any sw in it of with the factory sw that I cames it can work using the Ubiqua?
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    The sniffer hex files are located at C:\Program Files\Texas Instruments\SmartRF Tools\Packet Sniffer\bin\general\firmware if you install packet sniffer.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    I download the IAR 7.4 but now I have this error:
    "$XDCROOT$/xs" --xdcpath="$XDCPATH$" iar.tools.configuro -c "$TOOLKIT_DIR$" --cc "$COMPILER_PATH$" --device "$DEVICE$" --compileOptions $COMPILER_ARGS_ROOT_QUOTED$ --linkOptions $LINKER_ARGS_QUOTED$ --profile release --projFile "$PROJ_PATH$"
    I saw that you reply someone with the same error telling him that custom argument variables were not set correctly in IAR tools. Try to import it from project folder and build again.
    How can I do that?
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points

    Using SampleSwitch as example, you can go to IAR->Tools->Configure Custom Argument Variables to delete all content first and then import SampleSwitch.custom_argvars under C:\ti\simplelink\zstack_home_1_02_02a_44539\Projects\zstack\HomeAutomation\SampleSwitch\CC26xx

  • 0 in reply to YiKai Chen
    Intellectual 595 points
    Thank you that make it work, but now when I try to download or debug the code I have this Issue.
    Fatal error: Failed to load ftd2xx.dll
    Ensure that TI Emulation package has been installed.
    It can be found in the IAR Embedded Work bench Installation.

    I had the TI Emulation but I uninstall it when I was trying to fix the error.
    I already run the IAR installation but It didn't work. How can I re install that package?
    Thank you for all your help!
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    You can download XDS Emulation Software Package rom processors.wiki.ti.com/.../XDS_Emulation_Software_Package to install it.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    I downloaded and Install the last version but it gives me the same error.
    What should I do?
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    Can you do a screenshot to show me what happens now?
  • 0 in reply to YiKai Chen
    Intellectual 595 points

    Sure!

    here´s a picture!

    I´m using virtualbox because I have a MAC.

  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    Try to reinstall whole Z-Stack Home 1.2.2a to see if it will fix the problem.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    No, It didn't work...
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    Since you are using LaunchPad, do you select debugger to XDS110 in your IAR?
  • 0 in reply to YiKai Chen
    Intellectual 595 points

    I can only select TI XDS

  • 0 in reply to Angel Rodriguez43
    Intellectual 595 points
    Sorry I didn´t search correctly I change it to XDS110 and it appear now a legend that I have to update the firmware. Should I install and older version of TI Emulator?
    Sorry for all the question i'm now in this.
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    Just let IAR to update the FW and test it again.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    So, I should update IAR? Or how do I do the update fw?
    Thank you
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    When you try to download and debug the SW from IAR, IAR would ask you to update the FW and you just click OK to do it.
  • 0 in reply to YiKai Chen
    Intellectual 595 points

    This is the error that I get.

  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    Just click "Aceptar" and it should update the FW fro you. After it's done, you can do debug again.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    No, I click "Aceptar" and if I debug again it appears the same error.
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    Which IAR version do you use?
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    Try to go to c:\ti\ccs_base\common\uscif\xds110 and follow ReadMe.txt under the folder to update XDS FW.
  • 0 in reply to YiKai Chen
    Intellectual 595 points

    Hi YK,
    Thank you that worked... I can now program and debug.
    Is possible to used the CC2531EMK as coordinator and also to be sniffer?
    Thanks!!!!

  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    You can use CC2531EMK either as coordinator or as sniffer but you cannot make it as coordinator and sniffer at the same time.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    Ok, If I want to used as sniffer I have to install the hex files located at C:\Program Files\Texas Instruments\SmartRF Tools\Packet Sniffer\bin\general\firmware right? Or with the factory program I can do it? Also if I want to install the hex files I need a CC debug? Or is there any other way? And the last Question is to configure my computer as ZPA with Ztool I need to install in one cc2650 the znp_coordinator_pro_secure_linkkeyjoin.hex? or how can I do it? I will connect 5 CC2650.
    Thank you for all your support!
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points

    1. Yes, you have to download sniffer_fw_cc2531.hex under C:\Program Files (x86)\Texas Instruments\SmartRF Tools\Packet Sniffer\bin\general\firmware to your CC2531EMK for sniffer usage.

    2. Yes, you need CC Debugger.

    3. You should run znp_coordinator_pro_secure_linkkeyjoin.hex on one of your LAUNCHXL-CC2650 with Ztool to form Zigbee network. For other 4 LAUNCHXL-CC2650, you can run znp_enddev_pro_secure_linkkeyjoin.hex with Ztool to act as end device or znp_router_pro_secure_linkkeyjoin.hex with Ztool to act as router to join Zigbee network.

  • 0 in reply to YiKai Chen
    Intellectual 595 points
    Soo the Zstack on IAR is not necessary?
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    If you use CC2650 ZNP, there are prebuilt ZNP hex files and you don't need IAR.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    And If I want to used the Ztool to use the computer as coordinator, is possible to used the IAR code created?
    The precharge code in the cc2531 what it do?
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    1. If you use Ztool to use computer as coordinator, you don't need IAR.
    2. I don't understand what you mean "The precharge code in the cc2531 what it do?"
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    1. What other devices work as coordinators? Apart that the CC2531
    2. If I just bought the CC2531 it works with something or I need to upload a code to do anything?

    Thanks for all the support.
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    1. You can use CC2530 or CC2538 to act as coordinator too. And CC2652 can act as coordinator too.
    2. It depends on what FW you run on CC2531.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    So, I try to download the Coordinator code to the LaunchXL-CC2650 and It did, is that normal? How can I know that one end device connects to this coordinator?
  • 0 in reply to Angel Rodriguez43
    Guru 735455 points
    I couldn't understand your question. Please elaborate.
  • 0 in reply to YiKai Chen
    Intellectual 595 points
    For this answer
    3. You should run znp_coordinator_pro_secure_linkkeyjoin.hex on one of your LAUNCHXL-CC2650 with Ztool to form Zigbee network. For other 4 LAUNCHXL-CC2650, you can run znp_enddev_pro_secure_linkkeyjoin.hex with Ztool to act as end device or znp_router_pro_secure_linkkeyjoin.hex with Ztool to act as router to join Zigbee network.

    Is there any documentation?
    The other thing that I was saying is, I was able to program my cc2650 as coordinator. This means that It can work as coordinator or the program should download correctly.

    Regards