• State Resolved
  • Locked Locked
  • Replies 8 replies
  • Answers 1 answer
  • Subscribers 52 subscribers
  • Views 526 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.

LAUNCHXL-CC2640R2: Project Zero Initiation Page Does Not Show "Sources" section

Al Wang
Prodigy 60 points

Part Number: LAUNCHXL-CC2640R2
Other Parts Discussed in Thread: UNIFLASH

Hello, 

I have 2 questions.

(1) At step 2 of Getting Started Demo (https://dev.ti.com/tirex/explore/node?node=AJ7jWuST9RweXKhWHqlyWg__FUz-xrs__LATEST), I could not find the so called "Sources" section" in CC Studio after loading the Project Zero, or in BTool. 

(2). Also I go following error messages for COM4 port even after reset the Lauchxl board: 

[3] : <Error> - 02:31:59.841
Message Response Timeout
Name = HCI_Reset
OpCode = 0x0C03
Tx Time = 02:31:57.820
--------------------------------------------------------------------
[4] : <Warning> - 02:31:59.862
Device Reset Timeout
Device May Not Function Properly

Could you please help me? Thank you very much and have a great weekend!

Al

  • 0
    Guru 735705 points

    Try to refer to CC2640R2 SimpleLink Academy at dev.ti.com/.../node

  • 0 in reply to YiKai Chen
    Prodigy 60 points

    Hello, YiKai,

    Thank you for your response. I did start the BLE Fundamental Training. But I ran into the same problem with BTool initiation in Task 2 of the training page (https://dev.ti.com/tirex/explore/node?node=ADoEZBrWKWqhpyfpKc8WDw__krol.2c__LATEST). The following message timeout and reset timeout errors are still prompted regardless of me pushing the reset button on the Launchpad before or after Ok'ing the Serial Port Setting for COM4 port. The port COM4 had been confirmed by Device Manager to be the right port, by the way.  Also, the Serial Port Setting was also default: 115200 speed, 8-bit, no parity, no flow control, etc.

    [1] : <Info> - 10:05:41.119
    Port opened at 11/29/2021 10:05:41 AM
    --------------------------------------------------------------------
    [2] : <Tx> - 10:05:41.518
    -Type : 0x01 (Command)
    -OpCode : 0x0C03 (HCI_Reset)
    -Data Length : 0x00 (0) byte(s)
    Dump(Tx):
    0000:01 03 0C 00 ....
    --------------------------------------------------------------------
    [3] : <Error> - 10:05:43.539
    Message Response Timeout
    Name = HCI_Reset
    OpCode = 0x0C03
    Tx Time = 10:05:41.518
    --------------------------------------------------------------------
    [4] : <Warning> - 10:05:43.561
    Device Reset Timeout
    Device May Not Function Properly
    --------------------------------------------------------------------

    Do you have any idea what could have caused this? Thank you very much!

    Albert

  • 0 in reply to Al Wang
    TI__Guru** 101570 points

    Hi Albert,

    Could you please confirm the host_test hexfile is flashed on the device?

    Please try again to flash the device. Once the device is flashed, close the tool used for flashing (i.e. Uniflash or FlashProgrammer or CCS). Then unplug the device. Plug the device, open BTool, select the proper COM port. If it does not work, try to select the other port.

    Best regards,

  • 0 in reply to Clément
    Prodigy 60 points

    Hi, Clement, 

    Thank you for your quick response! This may be a novice question. How do you flash the device in CCS? Do you have to terminate the debug mode (step 2) before flashing the device in step 3? Thank you so much!

    Best Regards,

    Albert

  • 0 in reply to Al Wang
    TI__Guru** 101570 points

    Hi Albert,

    With CCS, clicking the "debug" button automatically flash the device for you. FYI, while in debug mode, you can trigger device flashing by modifying the code and rebuilding it.

    Once the device is flashed, make sure to terminate the debug session, to close CCS, unplug the device, rep-plug the device, open BTool.

    Regards,

  • 0 in reply to Clément
    Prodigy 60 points

    Hi Clement,

    Thank you for the info. I had now initiated without errors, and successfully scanned in BTool after Host_Test device flashing/unplugging/plugging. But the list of Slave BDA (2C:00:16:2B:00:5A, for example) does not seem to match the device (GAP) address (0C:61:CF:47:63:53), obtained from PuTTy terminal (COM4) while flash the device with Project Zero. Besides, selecting/filling either of the addresses in Salve BDA area did not seem to establish connection successfully, with following messages:

    [when selecting 2C:00:16:2B:00:5A from the dropdown]: Please note that status is "bleincorrectmode."

    [21] : <Rx> - 12:51:00.654
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (HCI_LE_ExtEvent)
    -Data Length : 0x14 (20) bytes(s)
    Event : 0x0605 (1541) (GAP_EstablishLink)
    Status : 0x12 (18) (bleIncorrectMode)                         
    DevAddrType : 0x02 (2) (ADDRTYPE_PUBLIC_ID)
    DevAddr : 2C:00:16:2B:00:5A
    ConnHandle : 0x0000 (0)
    ConnRole : 0x00 (0) (
    ProfileRoles Bit Mask Is Not Set)
    ConnInterval : 0x0000 (0)
    ConnLatency : 0x0000 (0)
    ConnTimeout : 0x0000 (0)
    ClockAccuracy : 0x00 (0)

    Please note that status is "bleincorrectmode." Does this mean BLE is in correct mode or incorrect mode?

    [when filling the device address 0C:61:CF:47:63:53 in the Slave BDA area]: 

    [26] : <Rx> - 12:54:02.938
    -Type : 0x04 (Event)
    -EventCode : 0x00FF (HCI_LE_ExtEvent)
    -Data Length : 0x14 (20) bytes(s)
    Event : 0x0605 (1541) (GAP_EstablishLink)
    Status : 0x09 (9) (NV_ITEM_UNINIT)
    DevAddrType : 0x02 (2) (ADDRTYPE_PUBLIC_ID)
    DevAddr : 0C:61:CF:47:63:53
    ConnHandle : 0x0000 (0)
    ConnRole : 0x00 (0) (
    ProfileRoles Bit Mask Is Not Set)
    ConnInterval : 0x0000 (0)
    ConnLatency : 0x0000 (0)
    ConnTimeout : 0x0000 (0)
    ClockAccuracy : 0x00 (0)

    Please note the status is "NV_ITEM_UNINIT". It mean it's un-initiated the 

    Furthermore, the COM4 port in the PuTTy terminal turned "inactive" or "unable to connect", after BTool is activated for scanning or connection establishing. So it would not show any "connected" status as depicted in training step 2. 

    What could be the problems?  Thank you so much for your kind help! Have a great weekend!

    Albert

  • 0 in reply to Al Wang
    Prodigy 60 points

    Hi, Clement,

    I had tried to switch to COM1 port for the probe, it didnot work either.

    Albert

  • +1 in reply to Al Wang
    TI__Guru** 101570 points

    Hi Albert,

    There is no way you connect simultaneously a serial terminal (like Putty) and BTool.

    With that being said, the discussion here does not match anymore the initial topic. This makes difficult to have the proper experts to comment. As a consequence, I am going to close this thread.

    Please feel free to open new thread(s) with the questions still opened.

    Best regards,