Renesas HS6400FDIW3S Uživatelský manuál Strana 27

  • Stažení
  • Přidat do mých příruček
  • Tisk
  • Strana
    / 94
  • Tabulka s obsahem
  • KNIHY
  • Hodnocené. / 5. Na základě hodnocení zákazníků
Zobrazit stránku 26
14
3.1.4 What are“Protocol A”, “Protocol B” and “Protocol C” Kernels?
“Protocol A” - For some 0.8µm, 0.6µm and 0.35µm flash devices using FDT 1.5 style kernels.
These are legacy kernels that are not supported and not included in the FDT installer.
Protocol A kernels are not available in the Japanese versions of FDT. Protocol A kernels
support use of the UPB but not the FDM. The kernel needs to be rebuilt for different crystal
frequencies in Boot and User Modes, and for changing the PMODE pin if using the UPB.
Please refer to the documentation supplied with the kernels for additional information.
“Protocol B” – For 0.35µm devices. These support the FDM but not the UPB.
Boot Mode - The kernel (made up of the Boot Mode Micro Kernel, Boot Mode Main Kernel,
and the Write and Erase modules) is held on the PC and downloaded as required. The Boot
Mode kernel does not need to be rebuilt for different crystal frequencies; this information is
stored in the FDT project and downloaded at runtime and initial communication is achieved
by the autobaud (where FDT sends 0x00 data until the device synchronises with it).
User Mode – The User Mode Test Program and User Mode Micro-Kernel need to be already
programmed and executing on the device. The initial Bit Rate Register value is held in the
‘gentest.h’ file and is compiled into the User Mode Test Program; this allows the kernel
initialise the serial communications interface to 9600 baud. If the clock frequency changes
from the default supplied value, the initial Bit Rate Register setting in ‘gentest.h’ [normally
MA_BRR_SCI or MA_BRR_SCI1] will need to be modified and the kernel recompiled. The
User Mode Main Kernel and the Write and Erase modules are held on the PC and
downloaded as required.
“Protocol C” – For devices with embedded kernels (Currently 0.18µm). These support the FDM but
not the UPB.
Boot Mode – A configuration file is stored on the PC which provides FDT with details about
the device, but the kernel (including the Write and Erase modules) resides internally on the
device. There is no need to rebuild anything for different clock frequencies in Boot Mode;
this information is stored in the FDT project and downloaded at runtime and initial
communication is achieved by the autobaud (where FDT sends 0x00 data until the device
synchronises with it).
User Mode – Some boards are supplied with a User Mode kernel. Similarly to the Protocol B
User Mode kernels, User Mode Kernel needs to be already programmed and executing on the
device. The initial Bit Rate Register value is held in the ‘gentest.h’ file and is compiled into
the User Mode Test Program; this allows the kernel initialise the serial communications
interface to 9600 baud. If the clock frequency changes from the default supplied value, the
initial Bit Rate Register setting in ‘gentest.h’ [normally MA_BRR_SCI or MA_BRR_SCI1]
will need to be modified and the kernel recompiled. The main difference to the Protocol B
User Mode Kernels is that the Write and Erase modules are held internally on the device.
3.1.5 What are the fcf and fdm files, can I edit them?
Stored alongside the other kernel files, the .fcf (Flash Configuration File) and .fdm (Flash
Development Module) files hold details about the device and kernel. Each supported device in each
kernel directory has its own .fcf and .fdm file. Information such as the RAM size, Flash size, Erase
Block Register details, default baud rate and default crystal frequency is stored in the fcf file and
details about the allowed pin settings for the FDM is stored in the FDM file. Each of these files is
protected with a checksum, so editing will render them invalid and FDT will detect this. Upon
Zobrazit stránku 26
1 2 ... 22 23 24 25 26 27 28 29 30 31 32 ... 93 94

Komentáře k této Příručce

Žádné komentáře