• State TI Thinks Resolved
  • Locked Locked
  • Replies 7 replies
  • Answers 2 answers
  • Subscribers 51 subscribers
  • Views 244 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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: VSENSE Jumper setting when connecting external custom board

John Wright
Expert 1390 points
Part Number: CC2640R2F

I'm attaching an external custom board to the CC2640R2 Development Kit.

How to I set the VSENSE jumper?

Thanks,

John

  • 0
    TI__Guru**** 208977 points

    Hi John,

    Please see the Advanced Use of the LaunchPad Hardware section of the Meet the CC2640R2 LaunchPad for BLE! module.  

    If the target board is powered externally, the VSENSE jumper must removed. Alternatively, the target can be powered by the LaunchPad through the debug header (connecting the Vsense pin to the LaunchPad 3.3 V supply), in this case the VSENSE jumper must be placed in the XDS110 Power position (the default position).

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Expert 1390 points

    Thanks Ryan,

    I'm reasonably sure this resolved the VSENSE issue. The LED next to the XDS100 chip is no longer red (it's green).

    However, I now have a different issue.

    When I bring up the Flash Programmer 2 utility, it fails to connect to the custom target CC2640R2F chip.

    I click on the CC2640R2F (under the XDS110, XDS-L50001OJ device), then right-click, then left click on Connect and it says 

    >Initiate access to target: XDS-L50001OJ.
    >Create XBAL object failed: Debug interface is locked.
    >Failed to create device object.

    Regards,

    John

  • 0 in reply to John Wright
    TI__Guru**** 208977 points

    This could indicate a hardware interface problem.  How long are the wires connecting to the custom target, and what connections do you make between it and the XDS110?  Has this CC2640R2F been programmed previously?  Have you been able to communicate with this custom target in the past?

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Expert 1390 points

    Thanks Ryan,

    I've had some success. I'll tell you about it after answering your questions.

    The wires connecting the custom target to the LAUNCHXL CC2640R2 P4 connector are 110mm (~4.25") long.

        (the JTAG_TCK wire is a larger gauge (28) than the JTAG_TMS wire (30); I suppose this could create different delays...not sure)

    Cable connections are as follows:

    Custom Board P1          Emulation Cable    LAUNCHXL CC2640R2 Evaluation Board P4
    Pin 1 - JTAG_TCK         White                      Pin 1 - TCK
    Pin 2 - VDD_3_3            Red                        Pin 17 - 3V3
    Pin 3 - JTAG_TMS         Yellow                     Pin 9 - TMS
    Pin 4 - nReset                Green                     Pin 11 - RESET
    Pin 5 - n/c
    Pin 6 - GND                    Black                      Pin 21 - GND

    - The CC2640RF2 on the custom board has never been programmed previously.

    - Have you been able to communicate with this custom target in the past?

          A prior version of the custom target had a CC2640F128RHB and that board successfully communicated with the SmartRF06 Evaluation Board.

          The current custom board is almost identical except the TI chip has been replaced with a CC2640R2FRHBT part.

    Here are my successes:

    - I disconnected the custom board cable from P4 and re-installed all jumpers on P4. I also installed VSENSE jumper to pins 1 and 2 (selecting XDS110 PWR).

    - I then brought up Flash Programmer 2. I then clicked on 'Connect' and this succeeded.

    - I then pulled all the jumpers off P4 and re-attached the custom board cable.

    - Without clicking on 'Disconnect' I performed a CC26xx/CC13xx Forced Mass Erase

        I got the following result:

          > Start Flash Erase ...

         > Erase finished successfully.

         > Reset Target ...

         > Reset of Target successful.

         > Initiate access to target: XDS-L50001OJ

    And the Status Bar at the bottom was green and said 'Success!'

    Then I do a 'Disconnect' with the following result:

    >Reset target ...
    >Reset of target successful.

    Then I do a 'Connect' with the following result:

    >Initiate access to target: XDS-L50001OJ.
    >Reset target ...
    >Reset of target successful.
    >Initiate access to target: XDS-L50001OJ.

    Then I do a 'Disconnect' with the following result:

    >Reset target ...
    >Reset of target successful.

    Note - this is with the VSENSE Jumper still set to XDS110 PWR

    Then I remove the VSENSE jumper entirely: not installed!

    Then I do a 'Connect' with the following result:

    >Initiate access to target: XDS-L50001OJ.
    >Create XBAL object failed: Debug interface is locked.
    >Failed to create device object.

    I then re-install the VSENSE jumper to pins 1-2 (selecting XDS110 PWR)

    Then I do a 'Connect' with the following result:

    >Initiate access to target: XDS-L50001OJ.

    Then I do a 'Disconnect' with the following result:

    >Reset target ...
    >Reset of target successful.

    So, connecting to the custom target only works with the VSENSE jumper set to pin2 1-2 (selecting XDS110 PWR)

    This would be OK except for 1 thing. My custom board supports 2 different voltages.

       It powers up at 2.1V. It runs at 2.1V most of the time, until it needs to operate at 3.3V to run the sensors or LEDs, at which point to transitions to 3.3V.

           When sensor operations are completed it then transitions back to 2.1V.

    This all works flawlessly on a prior version of the board using the CC2640128RHB chip.

     

    Is there another way to setup the VSENSE?

    Or, am I NOT connecting the custom board cable correctly?

     

    Here's another piece of information:

    When I power up my custom board without connecting the cable to the LAUNCHXL board, it powers up at 2.1V. Then, as soon as I connect the cable to the LAUNCHXL board the voltage on my board rises from 2.1V to 3.3V. It seems like my board begins receiving power from the LAUNCHXL board when the cable is connected.

    This seems to indicate the cable is not connected correctly!

    Regards,

    John

  • 0 in reply to John Wright
    TI__Guru**** 208977 points

    Please review the LAUNCHXL-CC2640R2 Design Files.  P10/VSENSE should only concern the voltage source for the level shifters.  When powering the wireless MCU from the XDS supply, connect jumper between pins 1 and 2.  When powering the wireless MCU from the external supply, connect jumper between pins 2 and 3.  I assume you are using the XDS110 as the power supply and that you meant "Pin 7 - TCK" for the LAUNCHXL CC2640R2 Evaluation Board side of the connection.  The cables are much longer than recommended (<10 cm) for a stable JTAG connection so I recommend that you find a way to shorten this distance.

    Regards,
    Ryan

  • 0 in reply to Ryan Brown1
    Expert 1390 points

    Thanks Ryan,

    I found the problem.

    There are issues with the VSENSE circuit on the LAUNCHXL board when configured for external power.

    Point 1) You asked me previously (or stated as an assumption that I was deriving power for the external MCU from the LAUNCHXL). I am NOT powering the external MCU from the LAUNCHXL. I am using an external power source which drives the external MCU VCC (and all the logic on the external board).

    Point 2) P4 pin 17 is connected to XDS_VCC. So, the voltage source on the cable to the external MCU cannot be connected to pin 17 when the external MCU is externally powered. This would cause a short between the external power supply and XDS_VCC.

    Point 3) P4 pin 18 is connected to WMCU_VDD. So, the voltage source on the cable to the external MCU cannot be connected to pin 18 when the external MCU is externally powered. This might work, however, the MCU and a lot of other logic located on the LAUNCHXL is also powered by the external source, which causes extreme power draw.

    Work-around: Disconnect the VCC wire from P4 Pin 17 (or P4 pin 18). Pull the wire out of the female connector housing. Connect the wire directly to pin 2 of the VSENSE jumper.

    I verified this. It works as it should. The level shifters do their job and the external board can be powered with 2.1V or 3.3V.

    Regards,

    John

  • 0 in reply to John Wright
    Expert 1390 points

    Ryan,

    I guess I'm OK with the design of the LAUNCHXL Board.

    I decided to re-insert the power wire back into the female connector, however, it's in the pin 18 slot instead of pin 17.

    I can deal with the fact that the MCU and the sensor logic is powered by the external power cable when running an external board.

    This means accurate power measurements cannot be done with the external board connected to the LAUNCHXL, but I guess that's OK and it makes sense.

    Here are my final cable connections:

    Custom Board P1    Emulation Cable    LAUNCHXL CC2640R2 Evaluation Board P4
    Pin 1 - JTAG_TCK   White                     Pin 7 - TCK
    Pin 2 - VDD_3_3     Red                        Pin 18 - 3V3
    Pin 3 - JTAG_TMS  Yellow                     Pin 9 - TMS
    Pin 4 - nReset         Green                     Pin 11 - RESET
    Pin 5 - n/c
    Pin 6 - GND             Black                      Pin 21 - GND

    And here's the VSENSE jumper setting:

    Pin 2 - 3

    Thanks for your help,

    John