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-F280049C: Board Error, how to fix?

Part Number: LAUNCHXL-F280049C

I just bought a Launchxl-F280049c last week, and I am trying to run an example program to send data to a raspberry pi computer. Here is my connections:

Launchxl: Pin44 SCIATX to Raspberry pi's Pin10 

Launchxl: Pin43 SCIARX to Raspberry pi's Pin8

Launchxl: Pin62 GND to Raspberry pi's Pin6. 

I used example project: sci_ex4_echoback

Here is the error (I didnot use FTDI cable):

Inline image

I am new to Ti C2000, Please give me some advice on how to use this board, and how to fix this problem. 

Thanks. 

  • Hi Yubin,

    Welcome to C2000!

    This error is coming from the JTAG and means that the CCS cannot establish a connection with the debugger chip. The example is designed to support both the F280049c controlCARD and the F280049c LaunchPad (which you have). controlCARD uses XDS100v2, and the LaunchPad uses XDS110. So currently the code is configured for connecting with controlCARD, you can switch to LaunchPad by expanding the targetConfigs folder, locating the _LaunchPad.ccxml file, right click and Set as Active Target Configuration

    Then you should be able to connect with the board. If there is any issue, you can also double click the .ccxml file, go to Advanced at the bottom then press the Test Connection... button. It can give you error code which you can let me know

    Regards,

    Peter

  • Thanks Peter. 

    I activate this ccxml and the program works. 

    Now I want to see data in my raspberry pi. My understanding is I have to remove the jumper for xds debug probe, so the data can go to the gpio piins. 

    But I don't want to remove the jumpers because I have other tests. 

    I read online that I can use SCIBRX and SCIBTX, this way I don't need to remove jumpers, as they are not connected to xds debug probe. 

    is this correct. 

    Thanks. 

  • Hi Yubin,

    There are two sets of SCI switches on the board that can reroute the SCI signal from the XDS to the boosterpack signals for your use. In the user guide the specific description is available. So it is not necessary to remove the jumpers


    Regards,

    Peter

  • When I run the example: sci_ex4_echoback, I can see the xds debug output/results in putty. but when I use a LogicProbe to test pin44 (GPIO29), I got no readings. 

    I did some searches on internet, and got many different results. 

    Could you please tell me how to reroute the output to GPIO29, not my xds debug output. 

    Thanks. 

  • I guess the sci_ex4_echoback is designed to use xds debug as output, not phsical pins. 

    I guess I need to write a new program to test. 

  • Hi Yubin,

    It is possible to reroute the GPIO29 signal going from the XDS to the boosterpack headers. To do this, you can simply put the S6 switch on the board in the 1 position. In other words, you the switch which is labeled 28/29 ROUTE, you can put it in the direction of the BP label (this stands for boosterpack).

    Then you can attach a probe to the J5.44 pin to see the output of the SCI

    Regards,

    Peter

  • Hi Peter:

        I will try your method later (I really don't want to change the phsical setting, as this may cause trouble later). 

    Becasue I want the output to go to an external raspberry pi's uart, and use minicom in RPI to view the output, and current results go to xds (or the RX of xds), so maybe I can change the setting of physical pin GPIO28(RX) to make it the same as xds' Rx. 

    I did a search and find following for code change :

    EALLOW; 

    GpioCtrlRegs.GPAMUX2.bit.GPIO28 = 1

    GpioCtrlRegs.GPADIR.bit.GPIO28 = 1;

    GpioCtrlRegs.GPAPUD.bit.GPIO28 = 0;

    EDIS;

    Before I do it, I want hear your opinion. Is this correct?

    Thanks. 

  • Thanks Peter. 

    by setting the S6, I was able to view the result in Raspberry Pi.