Renesas HS6400FDIW3S Manual do Utilizador Página 26

  • Descarregar
  • Adicionar aos meus manuais
  • Imprimir
  • Página
    / 94
  • Índice
  • MARCADORES
  • Avaliado. / 5. Com base em avaliações de clientes
Vista de página 25
13
Chapter 3 Basic Operation
3.1 Background Information
3.1.1
What are the User and User Boot Areas?
The normal area of (internal) flash for Renesas devices, for user programs is known as the
User Area
.
This is where the code is stored which gets executed when the device is reset into User Mode. The
User area
can normally be programmed from a Boot Mode or User Mode connection.
On some devices there is an additional area of flash known as the
User Boot Area
. This is where the
code is stored which gets executed when the device is reset into
User Boot Mode
. The User Boot
Area tends to be much smaller than the User Area and is typically used for storing an alternative boot
stub, for setting up communication via some other communications medium / protocol. Normally, the
User Area and the User Boot Area both start at the same address – this is possible because only one is
ever mapped into the memory map at one time. It is only possible to program the User Boot Area from
Boot Mode - not from User Mode.
3.1.2
What is the difference between Boot Mode and User Mode?
The Renesas Flash devices have different modes of operation which are controlled by the state of the
mode pins when the device is brought out of reset. Most devices have an asynchronous serial Boot
Mode and a User/User Program Mode.
Generally, (asynchronous serial)
Boot Mode
connections, start with an autobaud – sending
synchronisation data packets to setup initial communications at a given baud rate. Additionally, for
most devices, the entire flash will be erased as part of the connection process, thus preventing any
Intellectual Property held on the device from being read from Boot Mode.
For a
User Mode
connection, the device must already be programmed with some code which talks to
FDT and allows programming. Most kernels are supplied with a User Mode micro kernel and test
program (*usually called “uGenU.mot” and xxxxtest.mot”). These files provide a
demonstration of User Mode programming and must be programmed into the device and be executing
before FDT tries to connect in User Mode. User Mode does not normally force an erase of the flash
during the connection process and does not autobaud to setup initial communications. The
demonstration User Mode test programs have the required Bit Rate Register value compiled into them
for setting up initial communications at 9600 baud; hence User Mode kernels need to be rebuilt for
different clock frequencies.
*Note that where the files are to be used as part of an embedded monitor, the User Mode kernel files may be also output as
binary files (.cde) without the reset vector populated. Some kernels use only a single file for the User Mode test program (e.g.
Protocol C kernels).
3.1.3
What is the difference between User Mode and User Program Mode?
Some devices use an additional mode pin to protect the flash from being written or erased by mistake;
this pin is normally known as the “Flash Write Enable” pin (FWE) if it has to be logic high to allow
programming, or the “Flash Write Protect” pin (FWP) if it has to be logic low to allow programming.
For these devices, this pin distinguishes “User Mode” from “User Program Mode”. An FDT User
Mode connection expects the device to be in User Program Mode at the point of programming and
erasing, and if using the FDM, can reset the device into User Mode to execute the programmed code
on disconnection.
Vista de página 25
1 2 ... 21 22 23 24 25 26 27 28 29 30 31 ... 93 94

Comentários a estes Manuais

Sem comentários