# PyOCD and MCU-Link

NXP recommends using the commercially supported tools and programmers for S32K3 automotive processors as noted on the [nxp.com product webpages.](https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools-/mcu-link-debug-probe:MCU-LINK)<br>

## Opensource tools

In order to make the MR-CANHUBK344 more accessible, several opensource tools have been enabled. Do not expect the same level of performance as commercial tools. The opensource and low cost hardware programmer/debugger [*MCU-link* ](https://www.nxp.com/design/software/development-software/mcuxpresso-software-and-tools-/mcu-link-debug-probe:MCU-LINK)is able to run the software *PyOCD* software. This combination has been made to work with S32K344. This is a very low cost DIY option for hobbyists and students. Please be sure to read the documentation well in order to be successful. Support will generally not be available on NXP community when using these tools.

{% hint style="warning" %}
These tools are considered unsupported by NXP engineers for use with S32K344 processors.
{% endhint %}

## Py-OCD

Basic support for the S32K344 has been included in PyOCD.&#x20;

[Following pages provide additional detail on using PyOCD and MCU-LINK-MR together.](/mr-canhubk344/getting-started/programming-with-opensource-tools/programming-with-zephyr-west.md#zephyr-west-mcu-link-mr-using-pyocd)\
\
Please follow the documentation for this opensource project at the link below:\
<https://github.com/pyocd/pyOCD/tree/v0.36.0>&#x20;

{% embed url="<https://github.com/pyocd/pyOCD/tree/v0.36.0>" %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://nxp.gitbook.io/mr-canhubk344/getting-started/programming-with-opensource-tools/pyocd-and-mcu-link.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.