ST10F276 View Datasheet(PDF) - STMicroelectronics
Part Name
Description
MFG CO.
'ST10F276' PDF : 229 Pages View PDF
Bootstrap loader
ST10F276
Figure 8. Memory configuration after reset
16 Mbytes
16 Mbytes
16 Mbytes
Note:
5.2.6
access to
external
bus
1 disabled
int.
RAM
0
access to
int. FLASH
enabled
access to
external
bus
1 enabled
int.
RAM
0
access to
int. FLASH
enabled
Depends on
reset config.
(EA, P0)
1
int.
RAM
0
Depends on
reset config.
BSL mode active
EA pin
Code fetch from
internal FLASH area
Data fetch from
internal FLASH area
Yes (P0L.4 = ‘0’)
High
Test-FLASH access
User IFLASH access
Yes (P0L.4 = ‘0’)
Low
Test-FLASH access
User IFLASH access
No (P0L.4 = ‘1’)
According to application
User IFLASH access
User IFLASH access
As long as ST10F276 is in BSL, the user’s software should not try to execute code from the
internal IFlash, as the fetches are redirected to the Test-Flash.
Loading the start-up code
After the serial link initialization sequence (see following chapters), the BSL enters a loop to
receive 32 bytes (boot via UART) or 128 bytes (boot via CAN).
These bytes are stored sequentially into ST10F276 Dual-Port RAM from location 00’FA40h.
To execute the loaded code, the BSL then jumps to location 00’FA40h. The bootstrap
sequence running from the Test-Flash is now terminated; however, the microcontroller
remains in BSL mode.
Most probably, the initially loaded routine, being the first level user code, will load additional
code and data. This first level user code may use the pre-initialized interface (UART or CAN)
to receive data and a second level of code, and store it in arbitrary user-defined locations.
This second level of code may be
● the final application code
● another, more sophisticated, loader routine that adds a transmission protocol to
enhance the integrity of the loaded code or data
● a code sequence to change the system configuration and enable the bus interface to
store the received data into external memory
In all cases, the ST10F276 still runs in BSL mode, that is, with the watchdog timer disabled
and limited access to the internal IFLASH area.
52/229
Share Link: 
