• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 51 subscribers
  • Views 522 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.

CC2540 channel map

Guy Wagner81
Prodigy 30 points
Other Parts Discussed in Thread: CC2540

Hello

I have a prototype of a wearable interface that includes cc2540. I am using it to demonstrate my product to investors, but when there is WIFI around  it interferes and the devices throughput drops so low that it ruins the demo ( and my companies possible future cash flow ...) 

from the spec I Understand that I can change the connection rf channel with the command LL_CHANNEL_MAP_REQ (opcode 0x01), but it doesn't seem to do any thing when I send it from the HCI commands tab in btool. also L2CAP_info_req doesn't provide any valuable data about the currently used channel, and the GAP_Establish_Link_Request doesn't send any data about the channels to be used.  

I relay need some guidance here so it wont happen again when I demonstrate my product 

Thanks

- Guy Wagner

  • 0
    TI__Guru** 105180 points
    Hi Guy,

    Did you take a corresponding BLE sniffer trace to see if the new request is getting sent with the new map? The initial channel map is sent in the connect request.

    Best wishes
  • 0 in reply to JXS
    Prodigy 30 points

    Hi Jxs
    I just looked at the BTool Log output when pressing establish and any other command.
    I only have one dongle, and it is used for btool, so I as far as I know I cant use it for sniffing at the same time.

    when I scan and connect from btool, the map is sent by the dongle or by the server side? can I configure btool to send a different channel map?

    Thanks for the quick reply

    This is the log output at link establish , I see no information regarding the map

    1] : <Tx> - 12:43:10.891
    -Type : 0x01 (Command)
    -Opcode : 0xFE09 (GAP_EstablishLinkRequest)
    -Data Length : 0x09 (9) byte(s)
    HighDutyCycle : 0x00 (Disable)
    WhiteList : 0x00 (Disable)
    AddrTypePeer : 0x00 (Public)
    PeerAddr : 2C:67:D2:72:39:D0
    Dump(Tx):
    01 09 FE 09 00 00 00 2C 67 D2 72 39 D0
    ------------------------------------------------------------------------------------------------------------------------
    [2] : <Rx> - 12:43:10.908
    -Type : 0x04 (Event)
    -EventCode : 0xFF (HCI_LE_ExtEvent)
    -Data Length : 0x06 (6) bytes(s)
    Event : 0x067F (GAP_HCI_ExtentionCommandStatus)
    Status : 0x00 (Success)
    OpCode : 0xFE09 (GAP_EstablishLinkRequest)
    DataLength : 0x00 (0)
    Dump(Rx):
    04 FF 06 7F 06 00 09 FE 00
    ------------------------------------------------------------------------------------------------------------------------
    [3] : <Info> - 12:43:11.011
    Device Connected
    Handle = 0x0000
    Addr Type = 0x00 (Public)
    BDAddr = D0:39:72:D2:67:2C
    ------------------------------------------------------------------------------------------------------------------------
    [4] : <Rx> - 12:43:11.008
    -Type : 0x04 (Event)
    -EventCode : 0xFF (HCI_LE_ExtEvent)
    -Data Length : 0x13 (19) bytes(s)
    Event : 0x0605 (GAP_EstablishLink)
    Status : 0x00 (Success)
    DevAddrType : 0x00 (Public)
    DevAddr : D0:39:72:D2:67:2C
    ConnHandle : 0x0000 (0)
    ConnInterval : 0x0050 (80)
    ConnLatency : 0x0000 (0)
    ConnTimeout : 0x07D0 (2000)
    ClockAccuracy : 0x00 (0)
    Dump(Rx):
    04 FF 13 05 06 00 00 2C 67 D2 72 39 D0 00 00 50
    00 00 00 D0 07 00