From: "Scholz, Kevin" <k-scholz@ti.com>
To: Francesco Dolcini <francesco@dolcini.it>,
"Francis, Neha" <n-francis@ti.com>
Cc: Franz Schnyder <fra.schnyder@gmail.com>,
"trini@konsulko.com" <trini@konsulko.com>,
"K, Santhosh Kumar" <s-k6@ti.com>, "Brattlof, Bryan" <bb@ti.com>,
"Chawdhry, Manorit" <m-chawdhry@ti.com>,
"u-boot@lists.denx.de" <u-boot@lists.denx.de>,
"Kumar, Udit" <u-kumar1@ti.com>,
"Gujulan Elango, Hari Prasath" <gehariprasath@ti.com>,
"Scholz, Kevin" <k-scholz@ti.com>
Subject: RE: [EXTERNAL] Re: [PATCH v2 5/7] arm: dts: k3-am69: ddr: Update to v0.12.0 of DDR config tool
Date: Thu, 20 Nov 2025 14:23:02 +0000 [thread overview]
Message-ID: <6726eb089e2f41ad9fa4a5ff3d6ceb54@ti.com> (raw)
In-Reply-To: <20251120081659.GA12514@francesco-nb>
[-- Attachment #1: Type: text/plain, Size: 3631 bytes --]
ODT is user configurable from the TDA4x (J784S4) DDR config tool. Custom boards can modify this setting as needed.
The default input settings to the TDA4x DDR config tool modified the J784S4 DDRSS3 ODT boot frequency setting in version 0.11.0 (published April 2024), and this was documented in the revision history (shown below).
You can access the J784S4 DDR config tool here to see a full list of changes across all revisions: https://dev.ti.com/sysconfig/?product=TDA4x_DRA8x_AM67x-AM69x_DDR_Config&device=J784S4_TDA4AP_TDA4VP_TDA4AH_TDA4VH_AM69x
[cid:image001.png@01DC59F6.70CE08D0]
Regards,
Kevin
From: Francesco Dolcini <francesco@dolcini.it>
Sent: Thursday, November 20, 2025 2:17 AM
To: Francis, Neha <n-francis@ti.com>; Scholz, Kevin <k-scholz@ti.com>
Cc: Franz Schnyder <fra.schnyder@gmail.com>; trini@konsulko.com; K, Santhosh Kumar <s-k6@ti.com>; Brattlof, Bryan <bb@ti.com>; Chawdhry, Manorit <m-chawdhry@ti.com>; u-boot@lists.denx.de; Kumar, Udit <u-kumar1@ti.com>; Gujulan Elango, Hari Prasath <gehariprasath@ti.com>
Subject: [EXTERNAL] Re: [PATCH v2 5/7] arm: dts: k3-am69: ddr: Update to v0.12.0 of DDR config tool
Hello Neha, Kevin On Mon, Nov 10, 2025 at 09: 55: 08AM +0530, Neha Malcom Francis wrote: > On 07/11/25 21: 14, Franz Schnyder wrote: > > On Mon, Nov 03, 2025 at 12: 40: 33PM +0530, Neha Malcom Francis wrote: > >> +#define DDRSS0_CTL_178_DATA
ZjQcmQRYFpfptBannerStart
This message was sent from outside of Texas Instruments.
Do not click links or open attachments unless you recognize the source of this email and know the content is safe.
Report Suspicious <https://us-phishalarm-ewt.proofpoint.com/EWT/v1/G3vK!uBdqXRfP1k07agZlPPNDfat-fUnIatngkgVq4IlE8toc41a-v6YUG2CtVe3J2GpfwHeX2f5391DpLqaG$>
ZjQcmQRYFpfptBannerEnd
Hello Neha, Kevin
On Mon, Nov 10, 2025 at 09:55:08AM +0530, Neha Malcom Francis wrote:
> On 07/11/25 21:14, Franz Schnyder wrote:
> > On Mon, Nov 03, 2025 at 12:40:33PM +0530, Neha Malcom Francis wrote:
> >> +#define DDRSS0_CTL_178_DATA 0x35000000
> >> +#define DDRSS0_CTL_186_DATA 0x00353500
> >> +#define DDRSS0_PI_275_DATA 0x00F30084
> >> +#define DDRSS0_PI_281_DATA 0x00F30084
> >> +#define DDRSS0_PI_287_DATA 0x00F30084
> >> +#define DDRSS0_PI_293_DATA 0x00F30084
> >> ....
> >> +#define DDRSS1_CTL_178_DATA 0x35000000
> >> +#define DDRSS1_CTL_186_DATA 0x00353500
> >> +#define DDRSS1_PI_275_DATA 0x00F30084
> >> +#define DDRSS1_PI_281_DATA 0x00F30084
> >> +#define DDRSS1_PI_287_DATA 0x00F30084
> >> +#define DDRSS1_PI_293_DATA 0x00F30084
> >> ....
> >> +#define DDRSS2_CTL_178_DATA 0x35000000
> >> +#define DDRSS2_CTL_186_DATA 0x00353500
> >> +#define DDRSS2_PI_275_DATA 0x00F30084
> >> +#define DDRSS2_PI_281_DATA 0x00F30084
> >> +#define DDRSS2_PI_287_DATA 0x00F30084
> >> +#define DDRSS2_PI_293_DATA 0x00F30084
> >> ....
> >> +#define DDRSS3_CTL_178_DATA 0x35350000
> >> +#define DDRSS3_CTL_186_DATA 0x00353535
> >> +#define DDRSS3_PI_275_DATA 0x35F30084
> >> +#define DDRSS3_PI_281_DATA 0x35F30084
> >> +#define DDRSS3_PI_287_DATA 0x35F30084
> >> +#define DDRSS3_PI_293_DATA 0x35F30084
> >
> > When I compare the updated configuration to the one for our Aquila AM69
> > board, I can observe that you have set an on-die termination at boot
> > frequency only for DRAM3. DRAM, DRAM1 and DRAM2 do not seem to have any
> > termination enabled. Is this a mistake or is it intentional?
>
> Kevin, could you explain the reasoning for this?
Any update on this?
Thanks
Francesco
[-- Attachment #2: image001.png --]
[-- Type: image/png, Size: 58685 bytes --]
next prev parent reply other threads:[~2025-11-20 15:03 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-03 7:10 [PATCH v2 0/7] ti: j7: Update to v0.12.0 of DDR config tool Neha Malcom Francis
2025-11-03 7:10 ` [PATCH v2 1/7] arm: dts: k3-j7200: ddr: " Neha Malcom Francis
2025-11-03 7:10 ` [PATCH v2 2/7] arm: dts: k3-j721s2: " Neha Malcom Francis
2025-11-03 7:10 ` [PATCH v2 3/7] arm: dts: k3-am68: " Neha Malcom Francis
2025-11-03 7:10 ` [PATCH v2 4/7] arm: dts: k3-j784s4: " Neha Malcom Francis
2025-11-03 7:10 ` [PATCH v2 5/7] arm: dts: k3-am69: " Neha Malcom Francis
2025-11-07 15:44 ` Franz Schnyder
2025-11-10 4:25 ` Neha Malcom Francis
2025-11-20 8:16 ` Francesco Dolcini
2025-11-20 14:23 ` Scholz, Kevin [this message]
2025-11-20 14:48 ` [EXTERNAL] " Francesco Dolcini
2026-04-21 10:10 ` Neha Malcom Francis
2025-11-03 7:10 ` [PATCH v2 6/7] arm: dts: k3-j742s2: " Neha Malcom Francis
2025-11-03 7:10 ` [PATCH v2 7/7] doc: ti: k3: Add section for DDR configuration Neha Malcom Francis
2025-11-03 14:35 ` Romain Naour
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=6726eb089e2f41ad9fa4a5ff3d6ceb54@ti.com \
--to=k-scholz@ti.com \
--cc=bb@ti.com \
--cc=fra.schnyder@gmail.com \
--cc=francesco@dolcini.it \
--cc=gehariprasath@ti.com \
--cc=m-chawdhry@ti.com \
--cc=n-francis@ti.com \
--cc=s-k6@ti.com \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=u-kumar1@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