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-F28069M: Unable to Load Example Echo Code in CCSv620

Part Number: LAUNCHXL-F28069M
Other Parts Discussed in Thread: CONTROLSUITE, C2000WARE

Hi team,

I've been going through the following video:

https://www.bing.com/videos/search?q=f28069m&&view=detail&mid=DCCB67A17E740EA78082DCCB67A17E740EA78082&&FORM=VRDGAR&ru=%2Fvideos%2Fsearch%3Fq%3Df28069m%26FORM%3DHDRSC3

And am experiencing some problems.

Hardware Settings

JP1: Closed

JP2: Closed

JP3: Closed

JP4: Closed

JP5: Closed

JP6: Closed

JP7: Closed

Boot 1, 2 & 3: ON

CCS v6.2.0

Compiler TI 6.2.3

Import from: C:\ti\controlSUITE\device_support\f2806x\v151\F2806x_examples_ccsv5\sci_echoback

When I go to debug, I get:

Error connecting to the target:

(Error -2131 @ 0x0)

Unable to access device register. Reset the device, and retry the operation. If error persists, confirm configuration, power-cycle the board, and/or try more reliable JTAG settings (e.g. lower TCLK).

(Emulation package 6.0.407.3)

I try setting up a target configuration and Test Conection button gives:

[Start: Texas Instruments XDS100v2 USB Debug Probe_0]

Execute the command:

%ccs_base%/common/uscif/dbgjtag -f %boarddatafile% -rv -o -F inform,logfile=yes -S pathlength -S integrity

[Result]

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

C:\Users\richa\AppData\Local\TEXASI~1\CCS\

    ti\1\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 'jioserdesusb.dll'.

The library build date was 'Jul 27 2016'.

The library build time was '18:31:37'.

The library package version is '6.0.407.3'.

The library component version is '35.35.0.0'.

The controller does not use a programmable FPGA.

The controller has a version number of '4' (0x00000004).

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 FTDI FT2232 with USB interface.

The link from controller to target is direct (without cable).

The software is configured for FTDI FT2232 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).

-----[The log-file for the JTAG TCLK output generated from the PLL]----------

There is no hardware for programming the JTAG TCLK frequency.

-----[Measure the source and frequency of the final JTAG TCLKR input]--------

There is no hardware for measuring the JTAG TCLK frequency.

-----[Perform the standard path-length test on the JTAG IR and DR]-----------

This path-length test uses blocks of 64 32-bit words.

The test for the JTAG IR instruction path-length succeeded.

The JTAG IR instruction path-length is 38 bits.

The test for the JTAG DR bypass path-length succeeded.

The JTAG DR bypass path-length is 1 bits.

-----[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 XDS100v2 USB Debug Probe_0]

I think I might be imprting from a CCS v5 model which might not be ideal.

I'm also getting warnings:

Description Resource Path Location Type

Build-variable 'XDAIS_CG_ROOT' cannot be resolved. The project may not build as expected. Example_2806xSci_Echoback  properties Problems

Description Resource Path Location Type

Invalid project path: Include path not found (\packages\ti\xdais). Example_2806xSci_Echoback  pathentry Path Entry Problem

When debugging I also get:

<terminated>F28069M_XDS100v2.ccxml [Code Composer Studio - Device Debugging] 

Example_2806xSci_Echoback [Code Composer Studio - Device Debugging] 

 Texas Instruments XDS100v2 USB Debug Probe/C28xx (Suspended - SW Breakpoint) 

  main() at Example_2806xSci_Echoback.c:67 0x008521  

  _args_main() at args_main.c:91 0x008675  

  c_int00() at boot28.inc:223 0x0085DE  (_c_int00 does not contain frame information) 

 Texas Instruments XDS100v2 USB Debug Probe/CLA_0 (Disconnected : Unknown) 

Any thoughts on how to resolve these issues would be great, thanks.

Best Regards

James Man

  • The "test connection" aspect of the process is working correctly so we know that the JTAG connection to the device is good.

    For the older projects you can right click on the project and pick "properties"  Go to General then products tab and remove XDIAS from the listing and recompile.

    Can you try manually loading the program/coff file by right clicking on the .ccxml and "launch target config"  Then in the new dialogue right click on the C28x core and "connect".

    Finally, Under the "Run" menu you'll want to load program you should be able to find by project.

    Let me know if this you connected.

    Best,

    Matthew

  • Thank you so much!

    I've conveyed it to the customer

    Have a good day  ^_^

    James

  • Hi Matthew,

    Many thanks for your help.

    In Products I have both C2000ware 3.4.00 and XDCtools 3.32.1.22_core checked, is that OK or do I need to select 1?

     

    Right click -> Launch Selected Configuration, under F28069M_XDS100v2.ccxml, it gives

    - Texas Instruments XDSv2 USB Debug Probe_0/C28xx (Disconnected: Unknown)

    - Texas Instruments XDSv2 USB Debug Probe_0/CLA_0 (Disconnected: Unknown)

     

    You are required to terminate existing session -> OK

     

    Run -> Load: No options available, all greyed out

     

    I opened up Tera Term and put in what I believe to be the correct settings, 9600 Baud rate, 8 bit data, 1 bit stop bit (this may be incorrect?) and didn't see anything being returned at any stage of compilation. Any further suggestions would be great, thanks.

    Best wishes,

    James

  • James,

    After they click OK to terminate the existing session, they need to right click on the

    Texas Instruments XDSv2 USB Debug Probe_0/C28xx (Disconnected: Unknown)

    and click connect.  This will either change the C28x to connected(and un-gray the run, load) or give an error in the console.  Please let me know.

    Best,

    Matthew

  • Thank you so much!

    I've conveyed it to the customer

    Have a good day  ^_^

    James

  • Hi Matthew,

    Many thanks for your help. After right clicking and pressing Connect, I receive the following error messages:

     

    For Boot Switch 1: On, On, Off

     

    Error connecting to the target:

    (Error -1135 @ 0x0)

    The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.

    (Emulation package 6.0.407.3)

     

    For Boot Switch 1: On, On, On

    No source available for “0x3ff75b”

    Best Regards

    James Man

  • Hi James,

    Matthew is out of the office for the next few days. He should be able to get back to you by Wednesday next week. 

    In the mean time would it possible for you to try 'Wait Boot Mode'? The screenshot below is from the LAUNCHXL_F28069M User Guide

    Best Regards,

    Marlyn

  • Thank you so much!

    I've conveyed it to the customer

    Have a good day  ^_^

    James

  • Hello Marlyn,

    Thanks for that. Putting in to Wait boot mode (Low, High, Low), and debugging, I get:

    Error connecting to the target:

    (Error -1135 @ 0x0)

    The debug probe reported an error. Confirm debug probe configuration and connections, reset the debug probe, and retry the operation.

    (Emulation package 6.0.407.3)

     

    Best wishes,

    James

  • James,

    Can we confirm that power jumpers JP1 and JP2 are populated.  This will power the MCU from the USB connection(debugger is powered even if these are not present).

    Best,
    Matthew

  • Hi Matthew,

    Thank you so much!

    I've conveyed it to the customer

    Have a good day  ^_^

    James

  • Hi Matthew,

     

    I can confirm jumpers JP1 & JP2 are in place (note JP3 - 7 are also in place)

     

    Interestingly, by removing JP2 twice over the course of a few seconds, just at the moment of debugging, I don't get the target not connected error but it looks like it might have compiled and I get:

    Example_2806xSci_Echoback[Code Composer Studio - Device Debugging]

    Texas Instruments XDS100v2 USB Debug Probe/C28xx(Suspended - SW Breakpoint)

      main() at Example_2806xSci_Echoback.c67 0x008521

      _args_main() at args_main.c:91 0x008675

      c_int00() at boot28.inc:223 0x0085DE (_c_int00 does not contain frame information)

      Texas Instruments XDS100v2 USB Debug Probe/CLA_0 (Disconnected : Unknown)

     

    It still doesn’t seem to have given the helloworld message in TeraTerm while Tera Term is running on what I believe to be the correct settings and COM port.

     

    Best wishes,

    James

  • James,

    Please try and remove JP7 (leave JP6 jumpered) and see if the UART will connect.

    Best,
    Matthew

  • Hi Matthew,

    Thank you so much!

    I've conveyed it to the customer

    Have a good day  ^_^

    James

  • Hi Matthew,

     

    Thanks for that.

     

    I remove JP7, and the board is recognised in both device manager under serial COM port and is recognised by Tera Term. When I debug in CCS v6.22, it seems to compile OK.

     

    I push play button and no helloworld message in Tera Term.

     

    I get the following warnings:

     

     

    Description         Resource             Path       Location               Type

    Build-variable 'XDAIS_CG_ROOT' cannot be resolved. The project may not build as expected.                Example_2806xSci_Echoback                     properties           Problems

     

    Description         Resource             Path       Location               Type

    Invalid project path: Include path not found (\packages\ti\xdais).              Example_2806xSci_Echoback                     pathentry            Path Entry Problem

     

    Right click on project -> Properties -> Products tab, I don't see the XDAIS as I thought I might have (I have unchecked in the past when seeing  similar error). I see C2000Ware 3.4.0.00 and XDCtools 3.32.1.22_core all checked.

     

    Best wishes,

    James

  • James,

    Even with the warning I think the code should compile, generate a .out file in the /debug directory.  Can you confirm if this is true?

    Can we go back to the first few replies I sent for this thread, and customer confirm that they can manually connect to the device using right click of CCXML Launch Selected Target Config.  For this I don't want to load any code, just make sure they can connect to the MCU through JTAG.

    Another thing to try would be to get the C2000Ware package and find the same example in that install, this would have the most up to date includes, etc.

    Best,
    Matthew

  • Hi Matthew,

    Thank you so much!

    I've conveyed it to the customer

    Have a good day  ^_^

    James