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.

CC2640R2F: Unable to issue commands over btool

Part Number: CC2640R2F
Other Parts Discussed in Thread: CCSTUDIO, UNIFLASH

Hi Team,

I have flashed the host_test image on the CC2640R2 and the chip is connected over XDS200 JTAG debugger to windows machine.

I am able to flash, erase and read registers using the flash programmer tool. I am also able to control the chip using CCStudio.

However, with using btool I am unable to issue commands like GAP Init. The device does not respond to the commands.

I have two evaluation boards and on one board, the image successuly runs and responds to commands. However, on the board,

the btool timeouts.

What could be the problem, how to check if its related to firmware or hardware ?

Best Regards,

Django

  • Hello Django,

    Can you answer a few questions to help us get a bit more information with regards to the issue? What version of the SDK are you using? Are you running more than one instance of BTool at a time? Did you use the .bat file located within the BTool folder to launch Btool? I recommend unplugging all Launchpads from your PC, shutting off all instances of BTool, plugging in the unresponsive LaunchPad, flashing the host_test hex onto the LaunchPad, resetting the board, and then starting Btool. Ensure that you have Btool pointing at the right COM port. Let me know if the above steps help.

    Sincerely,

    Jan

  • sdk used is : simplelink_cc2640r2_sdk_4_30_00_0
    I am running single instance of btool always.
    I am not running bat file, I am running the .exe file.
    I am not using launchpad, I am using evaluation board.

    I have done the steps as mentioned above and still no use, Is there a way to enable debugging in btool ?

  • Hi Django,

    Can you run the BTool program using the bat file? Also can you make sure you are following the steps shown in the BTool section of the following SLA tutorial? https://dev.ti.com/tirex/explore/node?node=ADU5RaAcoc.XpOvbOmL6cQ__pTTHBmu__LATEST 

    Let me know if this helps or not.

    Sincerely,

    Jan

  • You have connected UART in addition to JTAG, right? And BTool is configured to use the correct COM port? And UART is assigned to the appropriate pins on your HW?

  • Hi,

    I tried to run the sample application, project_zero using CCStudio and it did not work as expected. The BLE Scanner App didnt discovered the Project_zero Profile.

    Does the HOst_test and Project_zero uses the 32 KHz crystal as the clock source ? Because in this evaluation board, the 32KHZ crystal is removed.

    How to debug using CCStudio ?

    BR

    Django

  • Yes I Can flash the image, when the chip is in bootloader mode. But not able to run the image after that. Yes Btool is configured to use the correct COM port.

  • Hi Django,

    Can you try flashing simple_peripheral on your board and connecting to it through our SimpleLink Starter App on Android/IOS? I want to ensure the board is working properly.

    Regards,

    Jan

  • Hi,

    I did a debug session for simple_preipheral project using CCStudio and I dont see any SimplePheripheral being discovered by the app.

    However, on the other board (on which host_test works) , the app detects SimplePheriheral profile.

    BR

    Django

  • Hi Django,

    Just to confirm, you are not able to run any unmodified BLE example on the evaluation board successfully? If this is the case, then there may be an issue with the board. Can you try flashing the simple_peripheral firmware using Uniflash or Flash Programmer 2? Let me know if the project functions properly then.

    Regards,

    Jan

  • Hi,

    I found that the board is not 7x7 as the launchpad and its 5x5 with 32Khz crystal removed, because of that the GPIO pin initialization is failing.

    I will build the image for 5x5 without 32 Khz crystal removed setup and will update the status.

    BR

    Django

  • Hi Django,

    Thank you for the update. I will close this thread for now, if you would like to re-open this issue, then please reply to this thread and it will automatically reopen.

    Sincerely,

    Jan