Id Codes And Locking Mechanism; Mcu Device Id Code; Boundary Scan Tap - ST STM32F412 Reference Manual

Debug support (DBG)
30.6

ID codes and locking mechanism

There are several ID codes inside the MCUs. ST strongly recommends tools designers to
lock their debuggers using the MCU DEVICE ID code located in the external PPB memory
map at address 0xE0042000.
30.6.1

MCU device ID code

The MCUs integrate an MCU ID code. This ID identifies the ST MCU part-number and the
die revision. It is part of the DBG_MCU component and is mapped on the external PPB bus
(see Section 30.16 on page
5 pins) or the SW debug port (two pins) or by the user software. It is even accessible while
the MCU is under system reset.
Only the DEV_ID(11:0) should be used for identification by the debugger/programmer tools.
DBGMCU_IDCODE
Address: 0xE004 2000
Only 32-bits access supported. Read-only.
31 30 29 28
r r r
15 14 13 12
Res. Res. Res. Res.
Bits 31:16 REV_ID(15:0): Revision identifier
Bits 15:12 Reserved, must be kept at reset value.
Bits 11:0 DEV_ID(11:0): Device identifier
30.6.2

Boundary scan TAP

JTAG ID code
The TAP of the BSC (boundary scan) integrates a JTAG ID code equal to: 0x0645 8041
30.6.3 Cortex
The TAP of the Arm
®
Arm default one and has not been modified. This code is only accessible by the JTAG
Debug Port.
This code is 0x4BA0 0477 (corresponds to Cortex
Reference Arm®
1130/1163
1142). This code is accessible using the JTAG debug port (4 to
27 26 25
r r r r
11 10 9
r r r
This field indicates the revision of the device:
0x1001 = Revision Z
0x2000 = Revision B
0x3000 = Revision C / Revision 1
The device ID is 0x441
®
-M4 with FPU TAP
® ®
Cortex -M4 with FPU integrates a JTAG ID code. This ID code is the
documentation).
24 23 22
REV_ID
r r r
8 7 6
DEV_ID
r r r
®
-M4 with FPU r0p1, see
RM0402 Rev 6
21 20 19 18
r r r r
5 4 3 2
r r r r
RM0402
17 16
r r
1 0
r r
Section 30.2: