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.

CC2541: BLE Beacon FCC Testing

Part Number: CC2541
Other Parts Discussed in Thread: CC-DEBUGGER

We are submitting a CC2541 BLE Beacon product for FCC testing.

Our current code transmits an Eddystone TLM broadcast 1X per minute.

The lab has asked that we  "need to have the chipset set for constant transmission"

Can we please get some guidance here on setting up the Beacon transmitter in a mode that they are requesting?

Thanks in advance

Daniel

  • Hi Daniel,

    Please have a look at the wiki:
    - processors.wiki.ti.com/.../How_to_Certify_your_Bluetooth_product
    - processors.wiki.ti.com/.../FCC_ETSI_Test

    There are some APIs you can call in your application to set the device into continuous transmit/receive on various frequencies. Specifically HCI_EXT_ModemTestTxCmd in this case.

    Best regards,
    Aslak
  • Asiak, Thanks for the note. I received this comment back from the Bureau Veritas test lab:

    "Advertisement beacons cannot be used for regulatory testing. The test mode needed is continuous transmission of modulated signal via internally generated pseudorandom packets. We have seen GUI interface tools from TI that allows that fairly easily. "

    If it exists, can you point me to the TI GUI Interface tool that is referred to?

    I trust that since that our product is a non-connecting advertising beacon, we only have to be concerned with and test Channels 37, 38 and 39. Is that correct?

    Thanks
  • Hi Daniel,

    I'm not sure if you followed the links, but the API I described does start a continuous tone as requested.

    I don't know about which frequencies you need to test, the test house would probably know. But I'd imagine you are right.

    As for GUI, there's www.ti.com/.../SMARTRFTM-STUDIO

    Best regards,
    Aslak
  • Asiak:

    Thanks. We already had SmartRF installed and did verify. Two questions about it.

    1. We connect our Beacon to SmartRF though CC-Debugger and put it in the mode we want. I trust it will stay in that mode when we disconnect CC-Debugger so the lab can do their chamber tests. Correct?

    2. Confused about our code that is already programmed into the CC2541. Won't that interfere with the SmartRF mode? Is there a special "dumb" firmware we should program the CC2541 with before testing so that SmartRF mode will stick?

    Thanks

    Dan
  • Have it worked out. Thanks for the assistance