MCXE316 Configuration Tool

[brucebowling]

I am using the MCXE316 device (48-pin Cortex M7) and using the Configuration tool, however I am experiencing issues with it, both the MCUExpresso version and the standalone version:

A) The MCUXpresso version always tells me that this device is not supported, and to check my internet connection. I have downloaded the latest SDK (21.12.00 built 03-21-2026) and the same issue - cannot open the pin, clock, or TEE. I can use this tool for the MCXE31B variant but not the MCXE316 smaller chip.

B) I have better luck with the standalone tool (CFG), this tool I can properly set pins and the clock domain, and it will create output code. However when I try to run the TEE (Trusted Execution Environment) the tool says there is no data for the MCXE316 variant. I want to set up the MPU for a default configuration.

Also, all of the demos for the MCXE family are for the MCXE31B device, nothing for the MCXE316 version - pretty sure the MPU settings are different due to memory size, etc .

So, my 3 questions:

1) Is the MCXE316 the same as the MCXE31B in regards to the MPU capability? Not seeing a definitive answer to this but I may be missing something within the reference manual.

2) Does the MCXE316 device, out of reset, put the MPU in some sort of default state where the chip is usable but regions are not protected as would be with a customized initialization?

3) Can you provide a default MPU initialization for the MCXE316 device, or give me ideas on why the tool does not operate for the TEE mode? 

Thank you for the assistance!

[brucebowling]

Thank you for the response, I will read up on the various sections of the user manual regarding the setup.

I did verify that on reset the MPU is disabled, and this is further backed up on the Excel spreadsheet provided within the reference manual, under the "memories" tab - it indicates that all memory sections are non-cacheable at reset which makes sense in that each section needs to be defined as cacheable, bufferable, etc.

Within the FRDM-MCXE31B examples source files, inside the directory "board" there is a file board.c that contains the function BOARD_ConfigMPU() that is the MPU setup for the MCXE31B variant. I plan on using this to adapt from the 31B to the 316 variants, which hopefully is not that difficult.  

[carlos_o]

Hi @brucebowling 

Thanks for your post!

1. There are not documented differences of the MPU between the MCXE31 family 

2. ARM stays that the MPU is disabled after reset, please refer to ARM Documentation. Armv8-M Memory Model and Memory Protection User Guide

3. There is not a Driver or example available for the MPU of the MCXE31x, the MRC of the XRDC module is basically a system-level MPU which sits at the crossbar switch (AXBS), and it allows isolation of the individual masters (cores, DMA, ...) and the slaves on the bus (both memories and peripherals).

The MRC applicability's for each device are listed at the chapter 18.1.2 MRC configuration of the Reference Manual. 

You could refer to the XRDC example for the FRDM-MCXE31B

Regarding your point A: The Config Tools updates is by default disable in MCUXpresso IDE, if you want to enable it, go to Windows -> Preferences -> Install/Update -> Available Software Sites, mark the MCUXpresso Config Tools click Apply and Close.

Next go to Help -> Check for Updates

With this you will updates Config Tools to the newest version for MCXUXpresso IDE and you were able to use it for the MCXE316. 

Please note that TEE is disabled for all MCXE31x family devices at Config Tools, so you would need to implement your own solution.