S32K388 Hardware Specs Verification — RAM/ROM/Cache Sizes, Bus Connections, Power, NVIC & Watchdog

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

S32K388 Hardware Specs Verification — RAM/ROM/Cache Sizes, Bus Connections, Power, NVIC & Watchdog

261 Views
xlele
Contributor I

I am documenting the S32K388 hardware architecture for our project and have compiled the specifications below based on the Reference Manual (RM). However, I haves32k388.png uncertainties that I need to verify with the community. I would appreciate confirmation or pointers to the exact RM chapters.

0 Kudos
Reply
1 Reply

218 Views
davidtosenovjan
NXP TechSupport
NXP TechSupport

The provided table is mostly correct in terms of memory sizes (8 MB PFLASH, 128 KB DFLASH, ~1.125 MB SRAM including ~384 KB TCM, and 16 KB I/D cache per core).

However, some points need clarification:

- Flash does not operate at a fixed “250 MHz”. Its performance depends on wait states and controller configuration, not a simple frequency.
- Access to Flash and SRAM is through the system interconnect (AXBS crossbar), while TCM is directly connected to the core and runs at core frequency.
- The “64-bit XBAR” description is an oversimplification; the architecture uses a multi-layer crossbar with multiple masters and ports.
- The stated 12-cycle interrupt latency corresponds to the theoretical Cortex-M7 minimum. Actual latency is higher depending on system conditions.
- There is no EWM module on S32K3 devices; the primary watchdog is SWT.

For performance analysis, it is important to distinguish between TCM (deterministic, core-coupled), SRAM (via interconnect), and Flash (via controller with latency).

0 Kudos
Reply
%3CLINGO-SUB%20id%3D%22lingo-sub-2377218%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3ES32K388%20Hardware%20Specs%20Verification%20%E2%80%94%20RAM%2FROM%2FCache%20Sizes%2C%20Bus%20Connections%2C%20Power%2C%20NVIC%20%26amp%3B%20Watchdog%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2377218%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3E%3CSPAN%3EI%20am%20documenting%20the%20S32K388%20hardware%20architecture%20for%20our%20project%20and%20have%20compiled%20the%20specifications%20below%20based%20on%20the%20Reference%20Manual%20(RM).%20However%2C%20I%20have%3CSPAN%20class%3D%22lia-inline-image-display-wrapper%20lia-image-align-inline%22%20image-alt%3D%22s32k388.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3Cspan%20class%3D%22lia-inline-image-display-wrapper%22%20image-alt%3D%22s32k388.png%22%20style%3D%22width%3A%20999px%3B%22%3E%3Cimg%20src%3D%22https%3A%2F%2Fcommunity.nxp.com%2Ft5%2Fimage%2Fserverpage%2Fimage-id%2F387982iE0DF4890F027CDC2%2Fimage-size%2Flarge%3Fv%3Dv2%26amp%3Bpx%3D999%22%20role%3D%22button%22%20title%3D%22s32k388.png%22%20alt%3D%22s32k388.png%22%20%2F%3E%3C%2Fspan%3E%3C%2FSPAN%3E%20uncertainties%20that%20I%20need%20to%20verify%20with%20the%20community.%20I%20would%20appreciate%20confirmation%20or%20pointers%20to%20the%20exact%20RM%20chapters.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-2377661%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%20translate%3D%22no%22%3ERe%3A%20S32K388%20Hardware%20Specs%20Verification%20%E2%80%94%20RAM%2FROM%2FCache%20Sizes%2C%20Bus%20Connections%2C%20Power%2C%20NVIC%20%26amp%3B%20Wa%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-2377661%22%20slang%3D%22en-US%22%20mode%3D%22CREATE%22%3E%3CP%3EThe%20provided%20table%20is%20mostly%20correct%20in%20terms%20of%20memory%20sizes%20(8%20MB%20PFLASH%2C%20128%20KB%20DFLASH%2C%20~1.125%20MB%20SRAM%20including%20~384%20KB%20TCM%2C%20and%2016%20KB%20I%2FD%20cache%20per%20core).%3C%2FP%3E%0A%3CP%3EHowever%2C%20some%20points%20need%20clarification%3A%3C%2FP%3E%0A%3CP%3E-%20Flash%20does%20not%20operate%20at%20a%20fixed%20%E2%80%9C250%20MHz%E2%80%9D.%20Its%20performance%20depends%20on%20wait%20states%20and%20controller%20configuration%2C%20not%20a%20simple%20frequency.%3CBR%20%2F%3E-%20Access%20to%20Flash%20and%20SRAM%20is%20through%20the%20system%20interconnect%20(AXBS%20crossbar)%2C%20while%20TCM%20is%20directly%20connected%20to%20the%20core%20and%20runs%20at%20core%20frequency.%3CBR%20%2F%3E-%20The%20%E2%80%9C64-bit%20XBAR%E2%80%9D%20description%20is%20an%20oversimplification%3B%20the%20architecture%20uses%20a%20multi-layer%20crossbar%20with%20multiple%20masters%20and%20ports.%3CBR%20%2F%3E-%20The%20stated%2012-cycle%20interrupt%20latency%20corresponds%20to%20the%20theoretical%20Cortex-M7%20minimum.%20Actual%20latency%20is%20higher%20depending%20on%20system%20conditions.%3CBR%20%2F%3E-%20There%20is%20no%20EWM%20module%20on%20S32K3%20devices%3B%20the%20primary%20watchdog%20is%20SWT.%3C%2FP%3E%0A%3CP%3EFor%20performance%20analysis%2C%20it%20is%20important%20to%20distinguish%20between%20TCM%20(deterministic%2C%20core-coupled)%2C%20SRAM%20(via%20interconnect)%2C%20and%20Flash%20(via%20controller%20with%20latency).%3C%2FP%3E%3C%2FLINGO-BODY%3E