UM-B-041
SmartBond Production Line Tool
User Manual
Revision 4.8
02-Nov-2022
CFR0012
86 of 170
© 2022 Renesas Electronics
7.2.9
Debug Settings
Figure 71: Debug Settings
describes the available options for the
Debug Settings
. Debug messages are available in all
Note:
Printing debug information may introduce system delay and thus some tests may fail due to
time out expirations. We suggest having debug information disabled in all software blocks and only
partially enable when there is a real need for it. From PLT v4.0 and onwards, this system delay has
been almost eliminated as debug print messages are printed from a lower priority queue. It is safer,
but it is still suggested to have the debug prints disabled.
Table 58: Debug Settings
Option
Description
Enable
Enable debug message prints for the selected library or UI.
Output - Console
Sends the debug messages to the
stdio
output. The PLT CLI does not support this
option. If enabled, debug messages will be redirected to the equivalent files.
Output - File
Save the debug messages to a file.
Level - Error
Enable error debug level messages. All debug print messages marked as error will be
printed.
Level - Info
Enable info debug level messages. All debug print messages marked as info will be
printed.
followed by a second 32-bit word containing the data value of the register.
These words are always in pairs.
If the Register configuration command for a specific register exists multiple
times within the CS, the booter will execute the command as many times as
the command exists resulting with the specific register having the value the
last command instructed. The SDK should also make sure that the last
value is considered as valid.
XTAL trim
0x50050408
The XTAL trim calibration value found in Section
programmed in OTP CS. The value found in the XTAL trim calibration
process will be applied to register 0x50050408.
Stop
command
0x00000000
The Stop of CS command consists of one 32-bit word (0x00000000),
designating that the configuration script has reached the end and execution
should be terminated. It should be noted that there is no limitation for the
number of entries the Stop command exists in the CS, thus the first entry is
only considered by the booter. Apart from the minimum firmware version
entries that is evaluated by the booter at all times, all other commands after
the first entry of the Stop command are discarded.