• State Resolved
  • Locked Locked
  • Replies 20 replies
  • Answers 1 answer
  • Subscribers 58 subscribers
  • Views 3650 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.

CC2530EM: Z-tool is not detecting my cc2530 module.

Yadhukrishnan V M72
Expert 1875 points

Part Number: CC2530EM
Other Parts Discussed in Thread: CC2530, Z-STACK, , CC2531

Hi,

I am trying to work with TI cc2530 EM with smartrf05 EB. I updated the firmware using the smartRF flash programmer with the hex file, "C:\Texas Instruments\Z-Stack 3.0.1\Projects\zstack\ZNP\CC253x\bin\CC2530SB.hex". I have connected the mopdule in the smartrf05 EB and I connected the USB to serial cable to the PC and EB. Then I opened the Z-tool and clicked the scan for devices but it is showing no devices found. The baud rate is set to 38400 in settings, please help me to interface this Z-tool and EB module. Tell me if I am doing anything wrong?

  • 0
    TI__Mastermind 36415 points
    Yadhukrishnan,

    Have you tried using SmartRF Studio? This tool is free to download and it will be able to detect the SmartRF05 + CC2530EM board and it it does not then you have a driver issue on your system.

    Regards,
    /TA
  • 0
    TI__Expert 8950 points
    Hi,

    CC2530SB.hex is not a full ZNP image, it is only the serial bootloader which is linked into the IAR build. Try the images in the folder below for ZNP images:

    C:\Texas Instruments\Z-Stack 3.0.1\Projects\zstack\ZNP\CC253x\dev\
  • 0 in reply to JasonB
    Expert 1875 points

    Hi Jason,

    Thank you for the kind reply, I did flashed the file in the folder:C:\Texas Instruments\Z-Stack 3.0.1\Projects\zstack\ZNP\CC253x\dev\CC2531ZNP-with-SBL.hex in two usb dongle and I could use ztool for these two dongles. Now I have problem with just making a coordinator-router link and send simple messages. Please help me

    Thank you.

  • 0 in reply to YiKai Chen
    Expert 1875 points
    Thank you for the reply, could I send messages between router and coordinator using that link? I want to make a coordinator-router coordinator-end device link and send messages between them, so simple!.

    Thank you.
  • 0 in reply to Yadhukrishnan V M72
    Guru 735695 points
    Yes, it's no problem to send messages between router and coordinator after you follow the steps in the link.
  • 0 in reply to YiKai Chen
    Expert 1875 points

    Hi YK,

          The link you provided is simple to understand. I used it to setup coordinator and router in 2 cc2531 dongles. I am attaching the logs of both modules of what I did on z tool. I want to send simple messages now between them. Please explain simply how to send messages between them, I don't know how to configure the parameters for AF_DATA_REQUEST or ZB_SEND_DATA_REQUEST. Please help YK.

    Thank you.

    Fullscreen cc2531 coordinator.txt Download 
    Start Time: 08/12/2017 10:22:04

<TX>10:22:29.69 COM16 SYS_RESET (0x4100)
    Type: 0x01 (SOFT RESET) (0x1)

<RX>10:22:32.21 COM16 SYS_RESET_RESPONSE (0x4180)
    Reason: 0x00
    TransportRev: 0x02
    Product: 0x00
    MajorRel: 0x02
    MinorRel: 0x07
    HwRev: 0x01

<TX>10:22:47.06 COM16 SYS_OSAL_NV_WRITE (0x2109)
    Id: 0x0003
    Offset: 0x00
    Len: 0x01
    Value: . (0x03)

<RX>10:22:47.1 COM16 SYS_OSAL_NV_WRITE_SRSP (0x6109)
    Status: SUCCESS (0x0)

<TX>10:23:01.66 COM16 SYS_RESET (0x4100)
    Type: 0x01 (SOFT RESET) (0x1)

<RX>10:23:03.46 COM16 SYS_RESET_RESPONSE (0x4180)
    Reason: 0x00
    TransportRev: 0x02
    Product: 0x00
    MajorRel: 0x02
    MinorRel: 0x07
    HwRev: 0x01

<TX>10:23:18.55 COM16 SYS_OSAL_NV_WRITE (0x2109)
    Id: 0x0087
    Offset: 0x00
    Len: 0x01
    Value: . (0x00)

<RX>10:23:18.58 COM16 SYS_OSAL_NV_WRITE_SRSP (0x6109)
    Status: SUCCESS (0x0)

<TX>10:23:40.51 COM16 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: FALSE (0x0)
    Channel: NONE (0x0)

<RX>10:23:40.52 COM16 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

<TX>10:23:47.42 COM16 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: TRUE (0x1)
    Channel: CHNL_0x00002000 (0x2000)

<RX>10:23:47.43 COM16 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

<TX>10:23:56.98 COM16 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x04) Network Formation (0x4)

<RX>10:23:58.52 COM16 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

<RX>10:23:58.52 COM16 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 8 (0x8)

<RX>10:23:58.52 COM16 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 1 (0x1)
    Commissioning Mode: 0x02 (Formation) (0x2)
    Commissioning Mode: 0x04 (Network Formation) (0x4)

<RX>10:23:59.1 COM16 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 9 (0x9)

<RX>10:23:59.1 COM16 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x00 (Success) (0x0)
    Commissioning Mode: 0x02 (Formation) (0x2)
    Commissioning Mode: 0 (0x0)

<TX>10:24:08.35 COM16 SYS_OSAL_NV_WRITE (0x2109)
    Id: 0x008F
    Offset: 0x00
    Len: 0x01
    Value: . (0x01)

<RX>10:24:08.36 COM16 SYS_OSAL_NV_WRITE_SRSP (0x6109)
    Status: SUCCESS (0x0)

<TX>10:24:20.22 COM16 UTIL_GET_DEVICE_INFO (0x2700)

<RX>10:24:20.22 COM16 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B00010CA096
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_ZB_COORD (0x9)
    NumAssocDevices: 0x00
    AssocDevicesList

<TX>10:24:30.38 COM16 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x02) Network Steering (0x2)

<RX>10:24:30.38 COM16 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

<RX>10:24:30.4 COM16 ZDO_MGMT_PERMIT_JOIN_RSP (0x45B6)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)

<RX>10:24:30.4 COM16 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x00 (Success) (0x0)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0 (0x0)

*** WARNING ***
    Unsupported or unformatted message received.  Raw data: 
    0C 45 CA F2 22 D6 AF 22 01 00 4B 12 00 00 00 

<RX>10:25:39.54 COM16 ZDO_END_DEVICE_ANNCE_IND (0x45C1)
    SrcAddr: 0x22F2
    NwkAddr: 0x22F2
    IEEEAddr: 0x00124B000122AFD6
    Capabilities: 0x8E

<TX>10:25:46.64 COM16 UTIL_GET_DEVICE_INFO (0x2700)

<RX>10:25:46.65 COM16 UTIL_GET_DEVICE_INFO_RESPONSE (0x6700)
    Status: SUCCESS (0x0)
    IEEEAddr: 0x00124B00010CA096
    ShortAddress: 0x0000
    DeviceType: COORDINATOR, ROUTER, END_DEVICE (0x7)
    DeviceState: DEV_ZB_COORD (0x9)
    NumAssocDevices: 0x00
    AssocDevicesList

    Fullscreen cc2531 router.txt Download 
    Start Time: 08/12/2017 10:22:08

<TX>10:22:34.5 COM21 SYS_RESET (0x4100)
    Type: 0x01 (SOFT RESET) (0x1)

<RX>10:22:36.32 COM21 SYS_RESET_RESPONSE (0x4180)
    Reason: 0x00
    TransportRev: 0x02
    Product: 0x00
    MajorRel: 0x02
    MinorRel: 0x07
    HwRev: 0x01

<TX>10:24:45.26 COM21 SYS_OSAL_NV_WRITE (0x2109)
    Id: 0x0003
    Offset: 0x00
    Len: 0x01
    Value: . (0x03)

<RX>10:24:45.3 COM21 SYS_OSAL_NV_WRITE_SRSP (0x6109)
    Status: SUCCESS (0x0)

<TX>10:24:48.07 COM21 SYS_RESET (0x4100)
    Type: 0x01 (SOFT RESET) (0x1)

<RX>10:24:50.35 COM21 SYS_RESET_RESPONSE (0x4180)
    Reason: 0x00
    TransportRev: 0x02
    Product: 0x00
    MajorRel: 0x02
    MinorRel: 0x07
    HwRev: 0x01

<TX>10:25:01.02 COM21 SYS_OSAL_NV_WRITE (0x2109)
    Id: 0x0087
    Offset: 0x00
    Len: 0x01
    Value: . (0x01)

<RX>10:25:01.06 COM21 SYS_OSAL_NV_WRITE_SRSP (0x6109)
    Status: SUCCESS (0x0)

<TX>10:25:14.07 COM21 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: FALSE (0x0)
    Channel: NONE (0x0)

<RX>10:25:14.08 COM21 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

<TX>10:25:21.61 COM21 APP_CNF_BDB_SET_CHANNEL (0x2F08)
    isPrimary: TRUE (0x1)
    Channel: CHNL_0x00002000 (0x2000)

<RX>10:25:21.61 COM21 APP_CNF_BDB_SET_CHANNEL_SRSP (0x6F08)
    Status: SUCCESS (0x0)

<TX>10:25:35.95 COM21 APP_CNF_BDB_START_COMMISSIONING (0x2F05)
    CommissioningMode: (0x02) Network Steering (0x2)

<RX>10:25:37.55 COM21 APP_CNF_BDB_START_COMMISSIONING_SRSP (0x6F05)
    Status: SUCCESS (0x0)

<RX>10:25:37.56 COM21 ZDO_STATE_CHANGE_IND (0x45C0)
    State: INVALID_PARAMETER (0x2)

<RX>10:25:37.56 COM21 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 1 (0x1)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0x02 (Network Steering) (0x2)

<RX>10:25:37.82 COM21 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 3 (0x3)

<RX>10:25:38.34 COM21 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 5 (0x5)

<RX>10:25:39.52 COM21 ZDO_STATE_CHANGE_IND (0x45C0)
    State: 7 (0x7)

<RX>10:25:39.57 COM21 ZDO_NODE_DESC_RSP (0x4582)
    SrcAddr: 0x0000
    Status: ZDP_SUCCESS (0x0)
    NwkAddr: 0x0000
    LogicalType_ComplexDescAvailable_UserDescAvailable: 0x00
    APSFlags_FrequencyBand: 0x40
    MACCapabilityFlags: ALTER_PAN_COORD, DEVICE_TYPE, POWER_SOURCE, RECEIVER_ON_WHEN_IDLE, ALLOCATE_ADDRESS (0x8F)
    ManufacturerCode: 0x0000
    MaxBufferSize: 0x50
    MaxInTransferSize: 0x00A0
    ServerMask: 10753 (0x2A01)
    MaxOutTransferSize: 0x00A0
    DescriptorCapabilities: 0x00

<RX>10:25:39.91 COM21 ZDO_MGMT_PERMIT_JOIN_RSP (0x45B6)
    SrcAddr: 0x22F2
    Status: ZDP_SUCCESS (0x0)

<RX>10:25:39.91 COM21 APP_CNF_BDB_COMMISSIONING_NOTIFICATION (0x4F80)
    Status: 0x00 (Success) (0x0)
    Commissioning Mode: 0x01 (Network Steering) (0x1)
    Commissioning Mode: 0 (0x0)

  • 0 in reply to Yadhukrishnan V M72
    Guru 735695 points
    You can refer to section 3.2.1.2 AF_DATA_REQUEST in Z-Stack Monitor and Test API.pdf under Z-Stack document folder.
  • 0 in reply to YiKai Chen
    Expert 1875 points
    Do I need to set AF_REGISTER before sending message?
  • 0 in reply to Yadhukrishnan V M72
    Guru 735695 points
    No, you don't have to.
  • 0 in reply to YiKai Chen
    Expert 1875 points

    Thank you for the help YK, I can now send messages now., I did configure the AF_REGISTER then only I could send messages, can you give me a message format for z tool without setting AF_REGISTER please?

  • 0 in reply to Yadhukrishnan V M72
    Guru 735695 points
    I might remember it incorrectly. What do you do with AF_REGISTER to send messages?
  • 0 in reply to YiKai Chen
    Expert 1875 points

    Hi YK,

    I am so happy because I was trying to achieve this for many many days, finally I did it!. 

    In coordinator I configured the af register as follows:

    EndPoint: 1

    AppProfId: c035 // I used this link: 

    AppDeviceId: 2 //just assigned a random number

    AppDevVer: 1 //this is also a random number I don't know what it means!!! LOL

    LatencyReq: NO_LATENCY_REQS

    AppNumInClusters: 1

    AppInClusterList: 0x0101 //used the above link 

    AppNumOutClusters:1

    AppOutClusterList: 0x0101 

    In router:

    EndPoint: 1

    AppProfId: c035 // I used this link: 

    AppDeviceId: 3 //just assigned a random number

    AppDevVer: 1 //this is also a random number I don't know what it means!!! LOL

    LatencyReq: NO_LATENCY_REQS

    AppNumInClusters: 1

    AppInClusterList: 0x0101 //used the above link 

    AppNumOutClusters:1

    AppOutClusterList: 0x0101 

    To send messages in coo:

    DstAddr: short address of the destination device.

    DstEndpoint:2

    SrcEndpoint:1

    ClusterId:0x0101

    TransId:1

    Options:0

    Radius:1

    Len:5

    Data: 10,12,13,14,15

    Thank you.

  • 0 in reply to Yadhukrishnan V M72
    Guru 735695 points
    Yes, you should register those things.
  • 0 in reply to YiKai Chen
    Expert 1875 points
    Hi YK,
    No you don't have to configure all those things in AF_REGISTER, you just need to configure the endpoints only, which means, just assign endpoint=1 for coordinator and endpoint=2 for router. Then use it in AF_DATA_REQUEST. That is , for coo you have to configure DestEndPoint as 2 and SrcEndPoint as 1 thats all.. :)
  • 0 in reply to Yadhukrishnan V M72
    Guru 735695 points
    Yes, I know this and It should be fine that you configure both endpoint of coordinator and device to the same value.
  • 0 in reply to YiKai Chen
    Expert 1875 points

    I don't think so YK, I couldn't send any messages using both endpoints of same value, Z tool displays this:

    <RX>12:05:10.34 COM16 AF_DATA_REQUEST_SRSP (0x6401)
    Status: afStatus_INVALID_PARAMETER (0x2)

  • 0 in reply to Yadhukrishnan V M72
    Guru 735695 points
    Actually, both of my coordinator and device use the same endpoint and I am sure it shall work.
  • 0 in reply to YiKai Chen
    Expert 1875 points
    May be you are right, but I couldn't send any messages by giving same endpoints in Z tool, If you have time please do that and let me know how you do it.
  • 0 in reply to Yadhukrishnan V M72
    Guru 735695 points
    Make sure your source and destination endpoint are correct.