System Manager Commands

[alfredog]

I would like to have information about the System Manager Commands available in the iMX95 19x19 LPDDR5 EVK from the debug port of Cortex-M33. 
There is no information about them, "help" only provides a list but no more information for commands with parameters are given. 

For example "lmm" , no idea about the arguments that can be used

Thank you in advance for pointing to the information.  

Alfredo

[JorgeCas]

Hello,

I suggest you take a look to the imx-sm and application note AN14478.

At this moment, this is all the information that can be shared sincei.MX95 is in Pre-production yet.

Best regards.

[alfredog]

Dear Jorge,

Thank you for your prompt response.
Though I am trying to configure and evaluate the iMX95 system, the question is also relevant to other iMX9 SoCs, such as iMX94.

Following your idea of reviewing the imx-sm code, in imx-sm/sm/utilities/monitor/monitor_cmds.c, the MONITOR_Dispatch function includes the "static string const cmds[]" available.

Then for every command there is a corresponding function, e.g. MONITOR_CmdReason.
There are several commands, such as "reason" that are straightforward but many others should require to fully analyze, even the parameters to enter.
For example, "cpu.w" will call MONITOR_CmdCtrl.
I am wondering why is not available information about parameterization of all these SM functions.

cpu.r => read mode status for all SoC cores (args not used)

ctrl.w controls the RUN/SLEEP state of cores, how? which are the arguments?
it is very difficult to understand (reverse engineering) the parameterization from the given source code

and if ctrl.w changes the SoC's cores states, what is the cpu.w purpose then?

Thank you for your prompt response.
Though I am trying to configure and evaluate the iMX95 system, the question is also relevant to other iMX9 SoCs, such as iMX94.

Following your idea of reviewing the imx-sm code, in imx-sm/sm/utilities/monitor/monitor_cmds.c, the MONITOR_Dispatch function includes the "static string const cmds[]" available.

Then for every command there is a corresponding function, e.g. MONITOR_CmdReason.
There are several commands, such as "reason" that are straightforward but many others should require to fully analyze, even the parameters to enter.
For example, "cpu.w" will call MONITOR_CmdCtrl.
I am wondering why is not available information about parameterization of all these SM functions.

cpu.r => read mode status for all SoC cores (args not used)

ctrl.w controls the RUN/SLEEP state of cores, how? which are the arguments?
it is very difficult to understand (reverse engineering) the parameterization from the given source code

and if ctrl.w changes the SoC's cores states, what is the cpu.w purpose then?

As mentioned, it would be required that NXP provides more information regarding these commands to fully use the system manager command line.

Kind regards, Alfredo.

[JorgeCas]

Hello,

Did you build the documentation?

This is explained in Monitor -> Resource commands (Table).

Best regards.

[alfredog · Accepted solution]

Great, thank you.
There is the information I needed. Solved:

git clone https://github.com/nxp-imx/imx-sm

To build the full documentation, install the required tools:

$> sudo apt -y install make doxygen texlive texlive-latex-extra

Then change to the documentation directory (sm/doc) and execute the following:

$> make clean
$> make html

The output is written to the build directory (sm/doc/build/html).

The top level for the html output is the index.html file.
=> .../imx-sm/sm/doc/build/html/MONITOR.html

Thanks again for the pointing out where the information was located. Alfredo

[alfredog]

Here is attached the SM monitor commands for other users reference.