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-CC2640R2: Custom Designed Board Bluetooth Connection Problem

Part Number: LAUNCHXL-CC2640R2

Hi,

I have a custom-designed board that uses 7x7 MCU just like in the launch board. My board's schematic is almost the same as the launch board. I have also an external flash on the same pin, I have a motion sensor but I connected my sensor's interrupt pins on exactly the same with button pins of launch board, same I2C pins, same SPI pins, same UART pins, etc. Because of that, I did not think to create a custom board header and source files, instead, I use CC2640R2_LAUNCH.h and c files. I did not use 32KHz crystal but I already did this configuration properly. I am sure because before getting my custom board, I developed my code on the launch board referenced by custom board schematic. Only, I think, the related difference between custom and launch board is RF pins' schematic. I used Single-ended with external bias configuration.

I got my custom boards today and I can upload my code on it (as I said, I worked on launch board before, I directly upload this code just changing the "#define CC2650EM_7ID" line with the  "#define CC2650EM_4XS" line in CC2640R2_LAUNCH.h file). My code does really basic things via Bluetooth, just sends the data that it received before on the same characteristic. 

The PROBLEM IS: I cannot connect to the board, it seams connecting on UART terminal (since I use OAD Off-Chip example basis) just after I got "timed out" and it kicks out my connection suddenly ( I think, 3. party BLE applications try to connect successively, I tried with NRF Connect and BLE Scanner applications). I know I cannot explain the problem well, because of that, I added a video.

Also, ı added my custom board's schematic (only MCU part) and its view.

This project is very important for me and my company also, please help me about that.

Thanks.

  • Hi,

    Your Schematic looks ok to me.

    Did you do any RF tests on your board?

    If not please do some basic tests (Tx power test, Freq accuracy, PER test) by using SmartRF Studio. 

    You can use CW-Unmodulated mode for Tx Power test and Frequency accuracy test. You may need to use Cap Array tuning for better Freq Accuracy. Please refer to SWRA640 for further details. The following is the link to SWRA640.

    For PER test, you can put one board in Packet in Tx mode and the board in Packet Rx mode.

    You need to interface your board to the Launchpad (by using JTAG Connector) to use SmartRF Studio. Also please remove all the Jumpers on the Launchpad from the IO connector (Middle of the LP with the lot of Jumpers).

    Why did you change "#define CC2650EM_7ID" line with the  "#define CC2650EM_4XS" line in CC2640R2_LAUNCH.h file ?

    4XS is 4*4 package and has different Pin Out to 7*7 package. It seems you are using 7*7 package. So, this may not be correct.

    Thanks,

    PM

  • PM said:

    Why did you change "#define CC2650EM_7ID" line with the  "#define CC2650EM_4XS" line in CC2640R2_LAUNCH.h file ?

    4XS is 4*4 package and has different Pin Out to 7*7 package. It seems you are using 7*7 package. So, this may not be correct.

    Just a reminder with regards to these defines at CC2640R2_LAUNCH.h

    * CC2650EM_7ID - Differential RF and internal biasing
    (default for CC2640R2 LaunchPad)
    * CC2650EM_5XD – Differential RF and external biasing
    * CC2650EM_4XS – Single-ended RF on RF-P and external biasing
    * CC2640R2DK_CXS - WCSP: Single-ended RF on RF-N and external biasing
    * (Note that the WCSP is only tested and characterized for
    * single ended configuration, and it has a WCSP-specific
    * PA table)

  • Hi,

    My custom board schematic has the whole peripheral with the launch board except RF schematic. Since the launch board's RF schematic is  Differential RF and internal biasing as you said but I designed my card as Single-ended RF on RF-P and external biasing RF schematic. Because of that, I used "CC2640R2_LAUNCHXL" defined board files but "CC2650EM_4XS" RF configurations.

    So, if I could implement correctly, this method should work I think.

    Thanks for your reply.

    Dogus

  • Hi Genius,

    I tested just like you said about replacing CC2650EM_7ID and CC2650EM_4XS. I tested with CC2650EM_7ID and still the same problem. Also, I tested with "#define CC2650EM_7ID" and making my RF schematic "#define RF_FE_MODE_AND_BIAS ( RF_FE_SINGLE_ENDED_RFP | RF_FE_EXT_BIAS )" in ble_user_conf.h and stil the same problem.

    I will also make the test you said with SmartRF studio. I will share my results here asap.

    Thanks,

    Dogus

  • Hi,

    If your RF configuration is Single-ended RF on RF-P and external biasing then you should set define CC2650EM_4XS.

    I suggest you request your PCB design for review by TI Engineer.

    -kel

  • Hi,

    Please test your board with SmartRF Studio and let me know the result. If that is OK then I will refer you to one of our Software engineer to help you with your code.

    Thanks,

    PM

  • Hi,

    I tested my card with SmartRF Studio with these configurations;

    and I tested my board with different channels (frequencies) and with different TX powers. Here are my results;

    I repeated PER test several times for each BLE Channel (both receiving and sending) and the results are average results.

    In the red part above, when I start the "Packet RX" mode at the launch board side, It receives 100 packets from other devices in my office I think because I could not press the Start button at Custom Board Packet TX mode in the meantime.

    Here are my results, if these outputs do not help you to give a clue of the problem, I am ready to do some other tests you advice or share PCB and software project directly with TI engineers.

    Thanks,

    Dogus

  • Hi,

    Your test results looks good. I don't see any issue with your results. The  Tx power is 3dB lower than LP  is because you use Single ended. This is expected result.

    The results shows that your board is OK. No issue with your hardware.

    You might have any issue with your software only. You can create a new post to request a help with your Software/code then our software team will look into it.

    Thanks,

    PM