• State Resolved
  • Locked Locked
  • Replies 7 replies
  • Subscribers 41 subscribers
  • Views 547 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.

CCS/CC3220S-LAUNCHXL: Is cc3220s-launchxl compatible with cc3220sf to write program?

Inseob Kim
Intellectual 545 points
Part Number: CC3220S-LAUNCHXL
Other Parts Discussed in Thread: CC3220SF, UNIFLASH, CC3220S

Tool/software: Code Composer Studio

Hi, I'm using CC3220S-LAUNCHXL and I have a custom board mounted CC3220SF.

First, I did put the CC3220S-LAUNCHXL in development mode using UniFlash ImageCreator.

And I confirmed that CC3220S-LAUNCHXL works well with targetConfigs(CC3220S, CC3220S_SWD with SOP settings) in CCS.

Then, I was connecting the wires between CC3220S-LAUNCHXL with the custom board as below:

In sequence, I was importing new project for CC3220SF in CCS and performed connection test in "targetConfigs/CC3220SF.xml".

I performed the test connection and it is succeeded, the log likes below:

[Start: Texas Instruments XDS110 USB Debug Probe]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -S integrity

[Result]


-----[Print the board config pathname(s)]------------------------------------

/Users/inseob/.ti/ccs920/0/0/BrdDat/testBoard.dat

-----[Print the reset-command software log-file]-----------------------------

This utility has selected a 100- or 510-class product.
This utility will load the adapter 'libjioxds110.dylib'.
The library build date was 'Nov 25 2019'.
The library build time was '15:02:58'.
The library package version is '8.4.0.00006'.
The library component version is '35.35.0.0'.
The controller does not use a programmable FPGA.
The controller has a version number of '5' (0x00000005).
The controller has an insertion length of '0' (0x00000000).
This utility will attempt to reset the controller.
This utility has successfully reset the controller.

-----[Print the reset-command hardware log-file]-----------------------------

The scan-path will be reset by toggling the JTAG TRST signal.
The controller is the XDS110 with USB interface.
The link from controller to target is direct (without cable).
The software is configured for XDS110 features.
The controller cannot monitor the value on the EMU[0] pin.
The controller cannot monitor the value on the EMU[1] pin.
The controller cannot control the timing on output pins.
The controller cannot control the timing on input pins.
The scan-path link-delay has been set to exactly '0' (0x0000).

-----[Perform the Integrity scan-test on the JTAG IR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG IR Integrity scan-test has succeeded.

-----[Perform the Integrity scan-test on the JTAG DR]------------------------

This test will use blocks of 64 32-bit words.
This test will be applied just once.

Do a test using 0xFFFFFFFF.
Scan tests: 1, skipped: 0, failed: 0
Do a test using 0x00000000.
Scan tests: 2, skipped: 0, failed: 0
Do a test using 0xFE03E0E2.
Scan tests: 3, skipped: 0, failed: 0
Do a test using 0x01FC1F1D.
Scan tests: 4, skipped: 0, failed: 0
Do a test using 0x5533CCAA.
Scan tests: 5, skipped: 0, failed: 0
Do a test using 0xAACC3355.
Scan tests: 6, skipped: 0, failed: 0
All of the values were scanned correctly.

The JTAG DR Integrity scan-test has succeeded.

[End: Texas Instruments XDS110 USB Debug Probe]

But, I can't debug and flash the custom board.

Something I missed? or the CC3220S-LAUNCHXL is not compatible with CC3220SF?

Best regards,
Inseob

  • 0
    Guru 80445 points

    Hi Inseob,

    Do you have switched your board with SF into development mode? Are you able to connect your board using Uniflash?

    BTW ... do you have connected reset pin from  CC3220S-LAUNCHXL to your board? Reset control is mandatory for a proper function of Uniflash GUI. Unfortunately results of JTAG test cannot detect all potential issue. For example it can be returned success in case you have connected TDI and TDO together. That means your hardware may not be even functional and JTAG test returns success.

    Jan

  • 0 in reply to Jan D
    Intellectual 545 points

    Hi Jan,

    If you say the SOP switch, yes, my custom boad has the SOP switch.

    I tried 2pin JTAG mode, and serial flash mode too however, I was not able to connect my board with Uniflash.

    I think the JTAG out port in the launchpad has the reset pin that you mentioned, isn't it?

    And is the launchpad for CC3220"S" compatible with CC3220"SF" to debug or flash with jtag and uart?

    Best regards,

    Inseob

  • 0 in reply to Inseob Kim
    Guru 39650 points

    Hi Inseob,

    First mandatory step is to be able connect using Unfilash. Without programming development mode into sFlash at your own hardware, you will not be able connect by JTAG/SWD. Because when device is not in development mode, JTAG is locked. There is no compatibility issue with your LaunchPad and CC3220SF device. Yes, JTAG out connector have reset pin. In case your board is properly designed it should not be issue. Unfortunately at your case we even not know whether your board is functional.

    • Do you use QFN chip of MOD?
    • Did you followed Layout Guidelines in case of QFN chip is used?
    • How many layer board do you use?
    • Did you revise your hardware by Design checklist?
    • Please make sure that you not have exchanged RX and TX lines of your UART.
    • Please try to use SOP mode 1-0-0 (2-1-0) during Uniflash connect attempt.
    • Please check by oscilloscope reset pin at CC3220SF. You should see there reset pulse during Uniflash connect attempt.
    • Please capture waveform at SOP2 at your LanchPad and compare with SOP2 at your board after reset.
    • Please measure voltages at internal DC-DC of your hardware (you should to have ~VDD_ANA = 1.8V, ~VDD_DIG = 1.2V).

    Jan

  • 0 in reply to Hnz
    Intellectual 545 points

    Hi Jan,

    We found mistake in the custom board and we can use only SRAM and external flash except internal flash of CC3220SF.

    I want to write a program directly to the external flash via CCS(instead of uniflash) except for the CC3220SF's internal flash.

    What approaches exist for writing programs except internal flash with CCS?

    I think, first, CC3220S_LAUNCHXL_TIRTOS.cmd needs to be modified to exclude internal flash.

    Could I get any guide to use external flash of the custom board with CCS instead of uniflash?

    Best regards,
    Inseob

  • 0 in reply to Inseob Kim
    Guru 39650 points

    Hi Inseob,

    CCS cannot write into external flash because external flash is not part of MCU address space.

    Every-time you write/read into/from sFlash it is done via code which is running at NWP or MCU.

    Jan

  • 0 in reply to Hnz
    Intellectual 545 points

    Hi, Jan

    Thank you for your reply.

    Ok I understood about external flash.

    Can you give me a guide how to modify the CC3220SF_LAUNCHXL_TIRTOS.cmd to exclude internal flash for debugging and development?

    Best regards,

    Inseob

  • 0 in reply to Inseob Kim
    Guru 39650 points

    Hi Inseob,

    In case of you want to execute code from RAM, you can use linker file for a CC3220S devices.

    Jan