F28035 XCP Connection Error

Hello,

I try to deploy a simple model to my Texas Insturments Experimenter's Kit powered by an F28035 MCU, but during Monitor & Tune in R2022a, I fail to connect to it.

What happens is that the code gets build and deployed to the MCU, but then the connection fails with:

| External Mode Open Protocol Connect command failed

| Caused by: Could not connect to target application: XCP internal error: timeout expired, in response to XCP CONNECT command

| Component:Simulink | Category:Block diagram error

The model that I use is:

The hardware configuration is:

The External Mode is setup as:

Finally, the SCI_A that should be used by XCP is configured as:

Isn't XCP connection achieved via the XDS100v2 probe, or what is wrong?

Thanks,

Robin

Answer 1

[Nathan Hardenberg]

I had this Problem with the Piccolo F280049C Launchpad and had to change the COM-Port (which is COM4 in your case):

Model Settings > Hardware Implementation > Target hardware resources > External mode > Serial port (...)

In Device-Manager check for the COM-Port with "User UART". For me by default the other COM-Port (Auxiliary Data Port) was selected. After the change "Monitor & Tune" worked as expected. Maybe this can also help you, even if it is not the same board/processor

[Robin Molnar]

Hi Nathan,

Thanks for the reply.

Unfortunately, I don't have the User-UART location in any COM ports. What I do have is the Auxiliary Port, as below.

Not sure what I can do.

Thanks,

Robin

[Nathan Hardenberg]

In this case I sadly don't really know. One thing you could try is to reduce the baudrate to a more standard 115200 bits/sec. But this is just a guess

[Robin Molnar]

For those facing the same problem, I have solved it by creating a secondary serial connection to the device (COM 3), as counter-intuitive as that may be, because the serial connection of the XDS100 (COM 5) probe could not be used for XCP, at least not for the Experimenter's Kit.

For the F28069M LaunchPad, XCP seems to work via XDS, so I don't know.

[ali]

hi @Robin Molnar;

Can you explain your solution with detailed and post a schematic of what you configured?

I have same problem with my custom board and I could not connect for xcp debugging yet.

[Robin Molnar]

Hi @ali,

I can't post a schematic riht now, but what I can do is to present you the resulting system.

So, overall, the result is like photographed below:

What this means is:

1. The Experimenter's Board is connected to the PC via 2 means: the USB XDS Debug Porbe, on the right, and via the RS-232 transciever.
2. I am not sure whether by default the transciever is on, I forgot, but to make sure the transciever is on, you could put SW1 in the ON position.
3. J9 should be shorted (I didn't have a jumper, so I've used a cable).

SW1 on the board:

To connect to the PC, I have used the minimal RS-232 configuration:

• Board's TX connected to RX (pin 2) on the DB9 connector (thus, the TX of the board will be connected to the RX of the USB COM Port adapter).
• Board's RX is connected to TX (pin 3) on the DB9 conector. Thus, the RX of the board will be connected to the TX pin of the USB COM Port adapter).
• GND will be connected to the GND (pin 5) of the DB9 connector, like below:

Power on the system, you should see 2 COM ports: 1 for the XDS Debug Probe and 1 for the board.

In Simulink:

1. Set the target as XDS Probe port. (Am I remembering this correctly?)
2. Set the External Mode to the External Mode port to the RS-232 port of the board, and not of the XDS Probe.

What will happen is:

1. Simulink will connect to the target via the XDS probe.
2. Simulink will do External Mode communication via the newly made RS-232 connection.

I hope this helps, having went through some academic burnout, there are some things I no longer remember.

Robin

[ali]

thank you man, it work completely and I connect to borad in external mode.

[Robin Molnar]

You are most welcome, @ali!