U-Boot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Bryan Brattlof <bb@ti.com>
To: Andrew Davis <afd@ti.com>
Cc: <u-boot@lists.u-boot-project.org>, Peng Fan <peng.fan@nxp.com>,
	Tom Rini <trini@konsulko.com>,
	Dan Carpenter <dan.carpenter@linaro.org>,
	Anshul Dalal <anshuld@ti.com>, Simon Glass <sjg@chromium.org>,
	Alper Nebi Yasak <alpernebiyasak@gmail.com>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Aristo Chen <aristo.chen@canonical.com>,
	Udit Kumar <u-kumar1@ti.com>,
	"Daniel Golle" <daniel@makrotopia.org>,
	Johan Jonker <jbx6244@gmail.com>,
	"Vignesh Raghavendra" <vigneshr@ti.com>,
	Paresh Bhagat <p-bhagat@ti.com>, Swamil Jain <s-jain1@ti.com>,
	Neha Malcom Francis <n-francis@ti.com>,
	Shiva Tripathi <s-tripathi1@ti.com>,
	Apurva Nandan <a-nandan@ti.com>, Chintan Vankar <c-vankar@ti.com>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	"Marek Vasut" <marek.vasut+renesas@mailbox.org>,
	Siddharth Vadapalli <s-vadapalli@ti.com>,
	Hrushikesh Salunke <h-salunke@ti.com>,
	Manorit Chawdhry <m-chawdhry@ti.com>
Subject: Re: [PATCH v3 10/11] doc: board: ti: correct path to tcl scripts
Date: Tue, 4 Aug 2026 14:08:22 -0500	[thread overview]
Message-ID: <20260804190822.75opogfv25ugtpky@bryanbrattlof.com> (raw)
In-Reply-To: <032b1ec4-9175-496c-b3b4-f46e06bd3065@ti.com>

On August  4, 2026 thus sayeth Andrew Davis:
> On 8/3/26 7:09 PM, Bryan Brattlof wrote:
> > OpenOCD has moved where it has placed the tcl scripts for TI's reference
> > boards. Update their paths to the new locations.
> > 
> > Tested-by: Anshul Dalal <anshuld@ti.com>
> > Signed-off-by: Bryan Brattlof <bb@ti.com>
> > ---
> > Changes in v3:
> > - Kept warning about which versions of OpenOCD have the tcl scripts
> > - Link to v2: https://lore.kernel.org/r/20260721-am62lx-v2-0-33ff580c267d@ti.com
> > ---
> >   doc/board/ti/am6254atl_sk.rst |  2 +-
> >   doc/board/ti/am62ax_sk.rst    |  2 +-
> >   doc/board/ti/am62dx_evm.rst   | 11 ++++++-----
> >   doc/board/ti/am62px_sk.rst    | 12 +++++-------
> >   doc/board/ti/am62x_sk.rst     |  2 +-
> >   doc/board/ti/am64x_evm.rst    | 24 ++++++++++++++++++++++++
> >   doc/board/ti/am65x_evm.rst    |  2 +-
> >   doc/board/ti/j7200_evm.rst    |  2 +-
> >   doc/board/ti/j721e_evm.rst    |  2 +-
> >   doc/board/ti/j722s_evm.rst    |  2 +-
> >   doc/board/ti/j784s4_evm.rst   |  2 +-
> >   11 files changed, 43 insertions(+), 20 deletions(-)
> > 
> > diff --git a/doc/board/ti/am6254atl_sk.rst b/doc/board/ti/am6254atl_sk.rst
> > index 18a3520b39c7..0df058aee157 100644
> > --- a/doc/board/ti/am6254atl_sk.rst
> > +++ b/doc/board/ti/am6254atl_sk.rst
> > @@ -305,4 +305,4 @@ To start OpenOCD and connect to the board
> >   .. prompt:: bash $
> > -  openocd -f board/ti_am625evm.cfg
> > +   openocd -f board/ti/am625evm.cfg
> > diff --git a/doc/board/ti/am62ax_sk.rst b/doc/board/ti/am62ax_sk.rst
> > index 3453ed339e7f..b04bfc991ea0 100644
> > --- a/doc/board/ti/am62ax_sk.rst
> > +++ b/doc/board/ti/am62ax_sk.rst
> > @@ -435,4 +435,4 @@ To start OpenOCD and connect to the board
> >   .. prompt:: bash
> > -  openocd -f board/ti_am62a7evm.cfg
> > +   openocd -f board/ti/am62a7evm.cfg
> > diff --git a/doc/board/ti/am62dx_evm.rst b/doc/board/ti/am62dx_evm.rst
> > index 0d12e3ec1476..88071b3e69d9 100644
> > --- a/doc/board/ti/am62dx_evm.rst
> > +++ b/doc/board/ti/am62dx_evm.rst
> > @@ -237,10 +237,6 @@ detailed setup information.
> >   .. warning::
> > -  **AM62A**: OpenOCD support since August 2023 (git master)
> > -
> > -  **AM62D**: Uses AM62A configuration (compatible due to same core architecture)
> > -
> >     Until the next stable release of OpenOCD is available in your development
> >     environment's distribution, it might be necessary to build OpenOCD `from the
> >     source <https://github.com/openocd-org/openocd>`_.
> > @@ -253,4 +249,9 @@ To start OpenOCD and connect to the board
> >   .. prompt:: bash
> > -  openocd -f board/ti/am62a7evm.cfg
> > +   openocd -f board/ti/am62a7evm.cfg
> > +
> > +.. note::
> > +
> > +   The AM62D-EVM uses the same tcl configuration as the AM62A-SK due to
> > +   same core architecture.
> > diff --git a/doc/board/ti/am62px_sk.rst b/doc/board/ti/am62px_sk.rst
> > index 44dae4afc870..9d8b5ebf38fb 100644
> > --- a/doc/board/ti/am62px_sk.rst
> > +++ b/doc/board/ti/am62px_sk.rst
> > @@ -331,13 +331,11 @@ detailed setup information.
> >   .. warning::
> > -  **OpenOCD support after**: v0.12.0
> > +   **OpenOCD support after**: v0.12.0
> > -  While support for the entire K3 generation including the am62xxx
> > -  extended family was added before v0.12.0, the tcl scripts for the
> > -  am62px have been accepted and will be available in the next release of
> > -  OpenOCD. It may be necessary to build OpenOCD from source depending on
> > -  the version your distribution has packaged.
> > +   Until the next stable release of OpenOCD is available in your development
> > +   environment's distribution, it might be necissary to build OpenOCD `from the
> 
> s/necissary/necessary
> 

Nice

> Otherwise everything else looks good,
> 
> Acked-by: Andrew Davis <afd@ti.com>

~Bryan

  reply	other threads:[~2026-08-04 19:08 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-04  0:09 [PATCH v3 00/11] arm: mach-k3: introduce basic support for the AM62L Bryan Brattlof
2026-08-04  0:09 ` [PATCH v3 01/11] firmware: scmi: switch to dev_ofnode during bind Bryan Brattlof
2026-08-04  0:09 ` [PATCH v3 02/11] tools: binman: extend ti_secure_rom to handle op-tee Bryan Brattlof
2026-08-04  0:09 ` [PATCH v3 03/11] soc: add data to identify the am62lx Bryan Brattlof
2026-08-04  0:09 ` [PATCH v3 04/11] boot/Kconfig: disable fit post processing for AM62L Bryan Brattlof
2026-08-04  0:09 ` [PATCH v3 05/11] arm: mach-k3: Add initial am62lx SoC support Bryan Brattlof
2026-08-04 11:12   ` Anshul Dalal
2026-08-04  0:09 ` [PATCH v3 06/11] board: ti: am62lx: add initial board files Bryan Brattlof
2026-08-04 11:14   ` Anshul Dalal
2026-08-04  0:09 ` [PATCH v3 07/11] arm: dts: k3-am62lx: Add binman support Bryan Brattlof
2026-08-04 11:20   ` Anshul Dalal
2026-08-04  0:09 ` [PATCH v3 08/11] configs: am62lx_evm: add initial defconfig Bryan Brattlof
2026-08-04 11:56   ` Anshul Dalal
2026-08-04 19:10     ` Bryan Brattlof
2026-08-04  0:09 ` [PATCH v3 09/11] doc: ti: k3: fix pygments warning parsing device-tree Bryan Brattlof
2026-08-04  0:09 ` [PATCH v3 10/11] doc: board: ti: correct path to tcl scripts Bryan Brattlof
2026-08-04 11:57   ` Anshul Dalal
2026-08-04 14:49   ` Andrew Davis
2026-08-04 19:08     ` Bryan Brattlof [this message]
2026-08-04  0:09 ` [PATCH v3 11/11] doc: board: ti: am62lx_evm: add initial docs for the AM62L-EVM Bryan Brattlof
2026-08-04 11:29   ` Anshul Dalal

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20260804190822.75opogfv25ugtpky@bryanbrattlof.com \
    --to=bb@ti.com \
    --cc=a-nandan@ti.com \
    --cc=afd@ti.com \
    --cc=alpernebiyasak@gmail.com \
    --cc=anshuld@ti.com \
    --cc=aristo.chen@canonical.com \
    --cc=c-vankar@ti.com \
    --cc=dan.carpenter@linaro.org \
    --cc=daniel@makrotopia.org \
    --cc=francesco.dolcini@toradex.com \
    --cc=h-salunke@ti.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jbx6244@gmail.com \
    --cc=m-chawdhry@ti.com \
    --cc=marek.vasut+renesas@mailbox.org \
    --cc=n-francis@ti.com \
    --cc=p-bhagat@ti.com \
    --cc=peng.fan@nxp.com \
    --cc=s-jain1@ti.com \
    --cc=s-tripathi1@ti.com \
    --cc=s-vadapalli@ti.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.u-boot-project.org \
    --cc=u-kumar1@ti.com \
    --cc=vigneshr@ti.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox