Reading values from peripheral registers

During debugging the EmbSys Registers view can read and display the actual values from the peripheral registers of the connected device. The data can be read from the registers of the RO (read-only) and WR (read-write) types. Only one register can be read at each debug action like a step, a resume, a stop, or a breakpoint.

To start reading a register, double-click the register name in the EmbSys Registers view. The registers selected for reading are marked with the “blue arrow” sign and with the register names displayed in green font.

To read the entire group of registers, double-click the group name. Similarly, double-click a register or a group of registers to stop reading their values.

Note: Be careful when selecting a register group with a large number of registers for reading as it might slow down the debugging. Also, you may encounter a problem with an abrupt disconnect occurring at the attempt of the client to access the selected group of registers. If this be the case, try to close the EmbSys Registers view and start a new debug session without this view.

When the Hex and Bin fields are updated with the actual values of the registers, these values are displayed in red font.

The “not read” message displayed in the Hex field means that the register value cannot be read. Make sure that the EmbSys Registers view uses the context of the project you are debugging. Learn more in topic Switching to a different context.

If the “not read” issue occurs in the right context, it can indicate a register not initialized properly. To learn more, refer to the respective hardware manual. The manuals are available in folder <S32 Design Studio installation path>/S32DS/help/resources/hardware.