Flash Range Specific Calibration Method
The calibration method Flash Range Specific which is selectable in the Calibration Handles combo box on the Memory Layout Editor tab.Flash Range Specific Calibration Method
The memory for the corresponding controllers is organized in clusters. Each cluster contains local FLASH (Data) memory together with local RAM which can be used for overlay. But each local RAM area can only be used to overlay FLASH memory of the same cluster!
The controllers also provide a small amount of global overlay RAM which can be used Cluster-independently. An MC tool (like INCA) can use the given memory to create calibration handles for Data Flash overlay with respect to the cluster constraints.
In the Calibration Handles editor on the Memory Layout Editor tab the Global Overlay and the Cluster Overlays can be configured as follows:
Global Overlay
There can only be one Global Overlay section with the following parameters:- Start Index: The start index for calibration handles created from that overlay memory
- Count: The maximum amount of calibration handles
- Min. Handle Size: The minimum size of each calibration handle
- Max. Handle Size: The maximum size of each calibration handle
Cluster Overlay
There can be several Cluster Overlay sections with the following parameters:- Start Index: The start index for calibration handles created from that overlay memory
- Count: The maximum amount of calibration handles
- Group Size: The amount of handles per sube block
- Overlay Size: The size of each calibration handle
- Emu Page spacing: The handle alignment
Conversion to the Flash Range Specific (fixed)
When using an XETK or FETK with a 3rd party tool, wich does not support the Flash Range Specific calibration method, the Global Overlay and the Cluster Overlays need to be transformed into fixed calibration handles. The XCT supports that conversion with respect to the Cluster constraints. The XCT first tries to overlay data regions with Cluster Overlay regions if possible (as Cluster Overlay is faster than Global Overlay). Then, if there are Data regions left, that are not yet covered, the XCT uses the Global Overlay to cover them (if there is enough Global Overlay memory).
Once the conversion has been performed in the XCT the Calibration Method Flash Range Specific (fixed) can be selected. The user can switch between Flash Range Specific and Flash Range Specific (fixed). The definitions in the Flash Range Specific method are the basis for the Flash Range Specific (fixed). I. e. if the data in the Flash Range Specific section gets mofified, the Flash Range Specific (fixed) might become invalid.
The XCT only allows to download the Flash Range Specific (fixed) configuration to a device in order to set this device up for 3rd party usage. An A2L export of that configuration is not possible, here the Flash Range Specific is used
Supporting Controllers
| Controller Name | Supported by |
|---|---|
| EMU58NE84_Rev1 | BR_XETK-S2.0, FETK-S2.0, FETK-S2.1, XETK-S21.0B, XETK-S31.0C, |
| RH850_E1xFCC1_Rev1 | XETK-S22.0, XETK-S22.0D, |
| RH850_E1xFCC2_Rev1 | FETK-T3.0A, XETK-S22.0, XETK-S22.0D, |
| RH850_E2xFCC1_Rev1 | FETK-T3.0A, XETK-S22.0, XETK-S22.0D, |
| RH850_E2xFCC2_Rev1 | FETK-T3.0A, XETK-S22.0, XETK-S22.0D, |
| RH850_E2x_Rev1 | FETK-T3.0A, XETK-S22.0, XETK-S22.0D, |
| RH850_P1M_Rev1 | XETK-S22.0, XETK-S22.0D, |
| RH850_P1xC_Rev1 | FETK-T3.0A, XETK-S22.0, XETK-S22.0D, |
| RH850_U2AEVA_Rev1 | FETK-T3.0A, XETK-S22.0, XETK-S22.0D, |
| RH850_U2B10FCC_Rev1 | |
| RH850_U2B20FCC_Rev1 | |
| RH850_U2B24FCC_Rev1 | FETK-T3.0A, XETK-S22.0, XETK-S22.0D, |
| RH850_U2B6FCC_Rev1 | |
| SPC58NE84_Rev1 | BR_XETK-S2.0, FETK-S2.0, FETK-S2.1, XETK-S21.0B, XETK-S31.0C, |
| SPC58xG_Rev1 | BR_XETK-S2.0, FETK-S2.0, FETK-S2.1, XETK-S21.0B, XETK-S31.0C, |
| SR6X7_A | BR_XETK-S4.0A.0B, BR_XETK-S4.0A.0B-M, FETK-S4.0A, FETK-T4.0B, |
| SR6xED_A | BR_XETK-S4.0A.0, BR_XETK-S4.0A.0A, FETK-S4.0A, |
| V850_PJ4_Rev1 | XETK-S22.0, XETK-S22.0D, |