public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Paresh Bhagat <p-bhagat@ti.com>
To: Bryan Brattlof <bb@ti.com>
Cc: Nishanth Menon <nm@ti.com>, <trini@konsulko.com>,
	<u-boot@lists.denx.de>,  <praneeth@ti.com>, <vigneshr@ti.com>,
	<khasim@ti.com>, <afd@ti.com>
Subject: Re: [PATCH] doc: board: ti: Add AM62D documentation
Date: Sat, 17 Jan 2026 08:00:56 +0530	[thread overview]
Message-ID: <b71dc5d4-e751-47df-8d3f-ad86b32c77c0@ti.com> (raw)
In-Reply-To: <20260108133154.5hitufe7wnsyaraa@bryanbrattlof.com>

Hi Bryan,

On 08/01/26 19:01, Bryan Brattlof wrote:
> On January  8, 2026 thus sayeth Paresh Bhagat:
>> Hi Nishanth,
>>
>>
>> On 06/01/26 00:29, Nishanth Menon wrote:
>>> On 00:05-20260106, Paresh Bhagat wrote:
>>>> Add info of boot flow and build steps for AM62Dx EVM.
>>> [...]
>>>> +  **OpenOCD support since**: August 2023 (git master)
>>>> +
>>>> +  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>`_.
>>>> +
>>>> +.. include::  k3.rst
>>>> +    :start-after: .. k3_rst_include_start_openocd_connect_XDS110
>>>> +    :end-before: .. k3_rst_include_end_openocd_connect_XDS110
>>>> +
>>>> +To start OpenOCD and connect to the board
>>>> +
>>>> +.. prompt:: bash
>>>> +
>>>> +  openocd -f board/ti_am62a7evm.cfg
>>> * Are you sure this is the location[1] ?
>>> * is am62a7 correct for am62d ?
>>
>> Yes, since they have same core architecture and count (also verified
>> locally).
> What version of openocd are you using? You might need to update some
> packages on your host.


My bad. New versions (~0.12) have slightly different path and filename. 
Will update the same in v2.


>
> ~Bryan

      reply	other threads:[~2026-01-17  2:31 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-05 18:35 [PATCH] doc: board: ti: Add AM62D documentation Paresh Bhagat
2026-01-05 18:59 ` Nishanth Menon
2026-01-08 10:46   ` Paresh Bhagat
2026-01-08 13:31     ` Bryan Brattlof
2026-01-17  2:30       ` Paresh Bhagat [this message]

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=b71dc5d4-e751-47df-8d3f-ad86b32c77c0@ti.com \
    --to=p-bhagat@ti.com \
    --cc=afd@ti.com \
    --cc=bb@ti.com \
    --cc=khasim@ti.com \
    --cc=nm@ti.com \
    --cc=praneeth@ti.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --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