TMS320F280023C: Loading TMS320F280023C board using XDS110 in LAUNCHXL-F280025C

Hi,

Are you using 2-pin cJTAG mode in target configuration file?

Thanks & Regards,

Santosh

Yes, it is "cJTAG"

1. I am using the LAUNCHXL-F280025C board inserting jumpers in TCK and TMS position in J101, I can load code to the F280025C uC using "cJTAG" mode.

2. When I connected my TMS320F280023C target board, I am taking out these two jumpers and connecting these two TMS and TCK signals to the TMS320F280023C target board, also powering the TMS320F280023C from 3.3V and GND from the LAUNCHXL-F280025C. I just changed the target device to TMS320F280023C in the same target configuration file.

and got this error: "Error connecting to the target, Error -2131"

Siba,

If debugging your custom board, remove the jumpers from J101. You are probably doing it already as per your post.

Are you connecting your custom board to J102 (TMS, TCK)?

Also make sure you have 2.2k pull-up on TMS line.

Thanks & Regards,

Santosh

TCK and TMS pins are common in XDS100 side for both J101 and J102, 

1. Do you think the absence of 2.2 pull up on TMS line is creating this problem ??

2. What does this error code 2131 mean ?

3. Do I need to pull up GPIO32 and GPIO24 ? I did it already, just asking whether it is necessary ?

Regards,

SIBAPRASAD

Siba,

Yes, it is recommended to have 2.2 pull up on TMS line. 

Please take a look at this page which explains all the error codes

#3, it is recommended to use 'Wait Boot' mode, that will mean no pull-up on GPIO24, GPIO32.

Thanks & Regards,

Santosh

which page you are referring to look for error code ?

Do I need to pull GPIO24, GPIO32 up to load the code ? Can you refer a document what boot I need to set and in which circumstances ?

Please do NOT be in a hurry to answer to my questions, be explicit and go in details, 

SIBAPRASAD CHAKRABARTI said:

which page you are referring to look for error code ?

https://software-dl.ti.com/ccs/esd/documents/ccs_debugging_jtag_connectivity_issues.html

Please take a look at the datasheet. 

The best way to start with 'Wait Boot' mode. This will make sure it is not running any code.