OrgZephyr/zephyr
OrgZephyr
/
zephyr
mirror of https://github.com/zephyrproject-rtos/zephyr.git
1
0
Fork 0
Code Issues Releases Wiki Activity
zephyr/drivers/flash/Kconfig.cc13xx_cc26xx

14 lines
443 B
Plaintext
Raw Normal View History

drivers: flash: introduce on-chip flash driver for TI CC13xx/CC26xx This includes a basic driver for built-in flash on the Texas Intruments SimpleLink CC13xx/CC26xx SoC series. The driver makes use of driverlib HAL from TI's SDK and was tested on two LaunchXL development boards with CC1352R and CC2652R SoCs: - CC1352R1 LaunchXL - CC26x2R1 LaunchXL Tests were done using: - flash shell sample (samples/drivers/flash_shell) - littlefs filesystem sample (samples/subsys/fs/littlefs)* - MCUboot (bootloader/mcuboot/boot/zephyr)* * additional changes in DTS for the boards were required (partitions table) and are not part of this changeset (will be introduced later) Some additional information about the implementation: 1. TI's Technical Reference Manual for CC13x2 and CC26x2 points out that "An individual 64-bit word can be programmed to change bits 1 to 0" but it seems this 'alignment' requirement is handled internally by the ROM function and thus 'write-block-size' is set to 1. 2. Interrupts, VIMS and line buffers are disabled during flash content update (write or erase) and restored afterwards as recommended by TI. 3. Only RAM to flash write is supported (source of data to be written to flash can't point to flash). 4. The driver doesn't take care of flash sector protection disable as that functionality is handled by CCFG. Write or erase requests which refer to a protected area will fail. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2022-04-27 16:15:25 +08:00
# Copyright (c) 2022 Piotr Dymacz
# SPDX-License-Identifier: Apache-2.0
config SOC_FLASH_CC13XX_CC26XX
bool "TI SimpleLink CC13xx/CC26xx flash controller driver"
drivers: flash: Update drivers to use devicetree Kconfig symbol Update flash drivers to use DT_HAS_<compat>_ENABLED Kconfig symbol to expose the driver and enable it by default based on devicetree. We remove 'depend on' Kconfig for symbols that would be implied by the devicetree node existing. Signed-off-by: Kumar Gala <galak@kernel.org>
2022-07-22 14:53:16 +08:00
default y
depends on DT_HAS_TI_CC13XX_CC26XX_FLASH_CONTROLLER_ENABLED
drivers: flash: introduce on-chip flash driver for TI CC13xx/CC26xx This includes a basic driver for built-in flash on the Texas Intruments SimpleLink CC13xx/CC26xx SoC series. The driver makes use of driverlib HAL from TI's SDK and was tested on two LaunchXL development boards with CC1352R and CC2652R SoCs: - CC1352R1 LaunchXL - CC26x2R1 LaunchXL Tests were done using: - flash shell sample (samples/drivers/flash_shell) - littlefs filesystem sample (samples/subsys/fs/littlefs)* - MCUboot (bootloader/mcuboot/boot/zephyr)* * additional changes in DTS for the boards were required (partitions table) and are not part of this changeset (will be introduced later) Some additional information about the implementation: 1. TI's Technical Reference Manual for CC13x2 and CC26x2 points out that "An individual 64-bit word can be programmed to change bits 1 to 0" but it seems this 'alignment' requirement is handled internally by the ROM function and thus 'write-block-size' is set to 1. 2. Interrupts, VIMS and line buffers are disabled during flash content update (write or erase) and restored afterwards as recommended by TI. 3. Only RAM to flash write is supported (source of data to be written to flash can't point to flash). 4. The driver doesn't take care of flash sector protection disable as that functionality is handled by CCFG. Write or erase requests which refer to a protected area will fail. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2022-04-27 16:15:25 +08:00
select FLASH_HAS_PAGE_LAYOUT
select FLASH_HAS_DRIVER_ENABLED
drivers/flash: Add explict erase capability with proper values Add explicit_erase capability and set proper value to it, depending on type of a device. Select FLASH_HAS_EXPLICIT_ERASE by devices that have program-erase characteristics and FLASH_HAS_NO_EXPLICIT_ERASE, where needed. Signed-off-by: Dominik Ermel <dominik.ermel@nordicsemi.no>
2024-02-02 21:46:29 +08:00
select FLASH_HAS_EXPLICIT_ERASE
drivers: flash: introduce on-chip flash driver for TI CC13xx/CC26xx This includes a basic driver for built-in flash on the Texas Intruments SimpleLink CC13xx/CC26xx SoC series. The driver makes use of driverlib HAL from TI's SDK and was tested on two LaunchXL development boards with CC1352R and CC2652R SoCs: - CC1352R1 LaunchXL - CC26x2R1 LaunchXL Tests were done using: - flash shell sample (samples/drivers/flash_shell) - littlefs filesystem sample (samples/subsys/fs/littlefs)* - MCUboot (bootloader/mcuboot/boot/zephyr)* * additional changes in DTS for the boards were required (partitions table) and are not part of this changeset (will be introduced later) Some additional information about the implementation: 1. TI's Technical Reference Manual for CC13x2 and CC26x2 points out that "An individual 64-bit word can be programmed to change bits 1 to 0" but it seems this 'alignment' requirement is handled internally by the ROM function and thus 'write-block-size' is set to 1. 2. Interrupts, VIMS and line buffers are disabled during flash content update (write or erase) and restored afterwards as recommended by TI. 3. Only RAM to flash write is supported (source of data to be written to flash can't point to flash). 4. The driver doesn't take care of flash sector protection disable as that functionality is handled by CCFG. Write or erase requests which refer to a protected area will fail. Signed-off-by: Piotr Dymacz <pepe2k@gmail.com>
2022-04-27 16:15:25 +08:00
select MPU_ALLOW_FLASH_WRITE if ARM_MPU
help
Enables TI SimpleLink CC13xx/CC26xx flash controller driver.