📄 redboot.cdl
字号:
description " This option controls whether or not RedBoot will make sure that memory being used by the \"load\" command is in fact in user RAM. Leaving the option enabled makes for a safer environment, but this check may not be valid on all platforms, thus the ability to disable it. ** Disable this only with great care **" } cdl_component CYGPKG_REDBOOT_FLASH { display "Allow RedBoot to support FLASH programming" flavor bool default_value 1 active_if CYGHWR_IO_FLASH_DEVICE description " If this option is enabled then RedBoot will provide commands to manage images in FLASH memory. These images can be loaded into memory for execution or executed in place." compile -library=libextras.a flash.c cdl_option CYGOPT_REDBOOT_FIS { display "RedBoot Flash Image System support" default_value 1 doc ref/flash-image-system.html description " This option enables the Flash Image System commands and support within RedBoot. If disabled, simple Flash access commands such as \"fis write\" will still exist. This option would be disabled for targets that need simple FLASH manipulation, but do not have the need or space for complete image management." } cdl_option CYGDAT_REDBOOT_FIS_MAX_FREE_CHUNKS { display "Max number of chunks of free space to manage" flavor booldata default_value 32 description " If this option is defined then \"fis free\" will rely on the FIS directory to determine what space is free within the FLASH. This option controls the maximum number of free segment which can be handled (typically this number is small). If this option is not enabled, the the archaic behaviour of actually scanning the FLASH for erased sectors (unreliable) will be used to determine what's free and what's not." } cdl_component CYGPKG_REDBOOT_FIS_CONTENTS { display "Flash Image System default directory contents" active_if CYGOPT_REDBOOT_FIS calculated 1 cdl_option CYGNUM_REDBOOT_FIS_DIRECTORY_BLOCK { display "Flash block containing the Directory" flavor data default_value (-1) description " Which block of flash should hold the directory information. Positive numbers are absolute block numbers. Negative block numbers count backwards from the last block. eg 2 means block 2, -2 means the last but one block." } cdl_option CYGOPT_REDBOOT_FIS_RESERVED_BASE { display "Pseudo-file to describe reserved area" active_if { 0 != CYGNUM_REDBOOT_FLASH_RESERVED_BASE } default_value 1 description " If an area of FLASH is reserved, it is informative to have a fis entry describing it. This option controls creation of such an entry by default in the fis init command." } cdl_option CYGOPT_REDBOOT_FIS_REDBOOT { display "File to describe RedBoot boot image" default_value 1 description " Normally a ROM-startup RedBoot image is first in the FLASH, and the system boots using that image. This option controls creation of an entry describing it in the fis init command. It might be disabled if a platform has an immutable boot image of its own, where we use a POST-startup RedBoot instead, which performs less board initialization." } cdl_component CYGOPT_REDBOOT_FIS_REDBOOT_POST { display "File to describe RedBoot POST-compatible image" default_value !CYGOPT_REDBOOT_FIS_REDBOOT description " This option controls creation of an entry describing a POST-startup RedBoot image in the fis init command. Not all platforms support POST-startup. A platform might have both for testing purposes, where the eventual user would substitute their own POST code for the initial ROM-startup RedBoot, and then jump to the POST-compatible RedBoot immediately following." cdl_option CYGNUM_REDBOOT_FIS_REDBOOT_POST_OFFSET { display "Offset of POST image from FLASH start" flavor booldata default_value 0 requires { CYGNUM_REDBOOT_FIS_REDBOOT_POST_OFFSET >= \ CYGBLD_REDBOOT_FLASH_BOOT_OFFSET } description " This option specifies the offset for a POST image from the start of FLASH. If unset, then the fis entry describing the POST image will be placed where convenient." } } cdl_option CYGOPT_REDBOOT_FIS_REDBOOT_BACKUP { display "File to describe RedBoot backup image" default_value 0 description " This option controls creation of an entry describing a backup RedBoot image in the fis init command. Conventionally a RAM-startup RedBoot image is kept under this name for use in updating the ROM-based RedBoot that boots the board." } cdl_option CYGOPT_REDBOOT_FIS_DIRECTORY_ARM_SIB_ID { display "Include ARM SIB ID in FIS" default_value 0 description " If set, this option will cause the last 5 words of the FIS to include the special ID needed for the flash to be recognized as a reserved area for RedBoot by an ARM BootRom monitor." } cdl_option CYGNUM_REDBOOT_FIS_DIRECTORY_ENTRY_SIZE { display "Size of FIS directory entry" flavor data default_value 256 description " The FIS directory is limited to one single flash sector. If your flash has tiny sectors, you may wish to reduce this value in order to get more slots in the FIS directory." } cdl_option CYGNUM_REDBOOT_FIS_DIRECTORY_ENTRY_COUNT { display "Number of FIS directory entries" flavor data default_value 8 description " The FIS directory normally occupies a single flash sector. Adjusting this value can allow for more than one flash sector to be used, which is useful if your sectors are very small." } cdl_option CYGBLD_REDBOOT_MIN_IMAGE_SIZE { display "Minimum image size" flavor data default_value 0x20000 description " This option controls the minimum length of images kept by the FIS. In particular, it should be large enough to hold the RedBoot primary image itself, as well as be a natural multiple of the FLASH erase block size." } cdl_option CYGBLD_REDBOOT_FLASH_BOOT_OFFSET { display "Offset from start of FLASH to RedBoot boot image" flavor data default_value CYGNUM_REDBOOT_FLASH_RESERVED_BASE requires { CYGNUM_REDBOOT_FLASH_RESERVED_BASE <= \ CYGBLD_REDBOOT_FLASH_BOOT_OFFSET } description " This option controls where the RedBoot boot image is located relative to the start of FLASH." } cdl_option CYGNUM_REDBOOT_FLASH_RESERVED_BASE { display "Size of reserved area at start of FLASH" flavor data default_value 0 description " This option reserves an area at the start of FLASH where RedBoot will never interfere; it is expected that this area contains (non-RedBoot-based) POST code or some other boot monitor that executes before RedBoot." } } cdl_option CYGSEM_REDBOOT_FLASH_LOCK_SPECIAL { display "Keep all RedBoot FLASH data blocks locked." flavor bool default_value 1 active_if { CYGHWR_IO_FLASH_BLOCK_LOCKING != 0 } description " When this option is enabled, RedBoot will keep configuration data and the FIS directory blocks implicitly locked. While this is somewhat safer, it does add overhead during updates." } cdl_option CYGSEM_REDBOOT_FIS_CRC_CHECK { display "Use CRC checksums on FIS images." flavor bool default_value 1 description " When this option is enabled, RedBoot will use CRC checksums when reading and writing flash images." } cdl_interface CYGINT_REDBOOT_ARM_FLASH_SIB_SUPPORTED { display "ARM FLASH drivers support SIB flash block structure" active_if CYGPKG_HAL_ARM description "This interface is implemented by a flash driver to indicate that it supports the ARM SIB flash block structure" } cdl_option CYGHWR_REDBOOT_ARM_FLASH_SIB { display "Use ARM SIB flash block structure" flavor bool active_if CYGINT_REDBOOT_ARM_FLASH_SIB_SUPPORTED default_value 1 description " This option is used to interpret ARM Flash System information blocks." } } cdl_component CYGSEM_REDBOOT_FLASH_CONFIG { display "Keep RedBoot configuration data in FLASH" flavor bool default_value { CYGPKG_IO_FLASH != 0 } compile fconfig.c description " When this option is enabled, RedBoot will keep configuration data in a separate block of FLASH memory. This data will include such items as the node IP address or startup scripts." cdl_option CYGNUM_REDBOOT_FLASH_CONFIG_SIZE { display "Length of configuration data in FLASH" flavor data default_value 4096 description " This option is used to control the amount of memory and FLASH to be used for configuration options (persistent storage)." } cdl_option CYGHWR_REDBOOT_FLASH_CONFIG_MEDIA { display "Style of media used for persistent data storage" flavor data legal_values { "FLASH" "EEPROM" } default_value { "FLASH" }# requires { ((CYGHWR_REDBOOT_FLASH_CONFIG_MEDIA == "FLASH") && CYGOPT_REDBOOT_FIS) ||# ((CYGHWR_REDBOOT_FLASH_CONFIG_MEDIA == "EEPROM") && !CYGOPT_REDBOOT_FIS) } description " Persistent data storage can either be held in 'norma' FLASH or some other device (represented by the 'EEPROM' choice). The different styles utilize different access methods." } cdl_option CYGSEM_REDBOOT_FLASH_COMBINED_FIS_AND_CONFIG { display "Merged config data and FIS directory" flavor bool active_if { CYGOPT_REDBOOT_FIS && (CYGHWR_REDBOOT_FLASH_CONFIG_MEDIA == "FLASH") } default_value 1 description " If this option is set, then the FIS directory and FLASH
⌨️ 快捷键说明
复制代码
Ctrl + C
搜索代码
Ctrl + F
全屏模式
F11
切换主题
Ctrl + Shift + D
显示快捷键
?
增大字号
Ctrl + =
减小字号
Ctrl + -