2014-04-22 01:34:05 +02:00
|
|
|
#
|
|
|
|
|
# For a description of the syntax of this configuration file,
|
2015-06-28 16:08:57 +02:00
|
|
|
# see the file kconfig-language.txt in the NuttX tools repository.
|
2014-04-22 01:34:05 +02:00
|
|
|
#
|
|
|
|
|
|
|
|
|
|
if ARCH_BOARD_SAM4S_XPLAINED_PRO
|
2014-04-22 18:38:08 +02:00
|
|
|
|
|
|
|
|
config SAM4S_XPLAINED_PRO_CDCACM_DEVMINOR
|
|
|
|
|
int "CDC/ACM Device Minor"
|
|
|
|
|
default 0
|
|
|
|
|
depends on SAM34_UDP && USBDEV && CDCACM
|
|
|
|
|
|
2014-04-30 22:47:30 +02:00
|
|
|
config SAM4S_XPLAINED_PRO_SCHED_TIMER_DEVPATH
|
2019-10-06 05:39:12 +02:00
|
|
|
string "Scheduler Timer Device Path"
|
2014-05-05 22:38:29 +02:00
|
|
|
default "/dev/rtt0"
|
2014-04-30 22:47:30 +02:00
|
|
|
depends on TIMER && SYSTEMTICK_EXTCLK
|
|
|
|
|
|
2014-04-30 22:11:53 +02:00
|
|
|
config SAM4S_XPLAINED_PRO_CPULOAD_TIMER_DEVPATH
|
2019-10-06 05:39:12 +02:00
|
|
|
string "CPU Load Timer Device Path"
|
2014-05-05 22:38:29 +02:00
|
|
|
default "/dev/tc0"
|
2023-10-26 15:03:16 +02:00
|
|
|
depends on TIMER && SCHED_CPULOAD_EXTCLK
|
2014-04-30 22:11:53 +02:00
|
|
|
|
2020-12-02 16:03:31 +01:00
|
|
|
config SAM34_NAND_BLOCKMOUNT
|
|
|
|
|
bool "NAND FLASH auto-mount"
|
|
|
|
|
default n
|
|
|
|
|
depends on NSH_ARCHINIT && SAM34_EXTNAND
|
|
|
|
|
---help---
|
|
|
|
|
Automatically initialize the NAND FLASH driver when NSH starts.
|
|
|
|
|
|
|
|
|
|
choice
|
|
|
|
|
prompt "NAND FLASH configuration"
|
|
|
|
|
default SAM34_NAND_NXFFS
|
|
|
|
|
depends on SAM34_NAND_BLOCKMOUNT
|
|
|
|
|
|
|
|
|
|
config SAM34_NAND_FTL
|
|
|
|
|
bool "Create NAND FLASH block driver"
|
|
|
|
|
depends on MTD && MTD_NAND
|
|
|
|
|
---help---
|
|
|
|
|
Create the MTD driver for the NAND and "wrap" the NAND as a standard
|
|
|
|
|
block driver that could then, for example, be mounted using FAT or
|
|
|
|
|
any other file system. Any file system may be used, but there will
|
|
|
|
|
be no wear-leveling.
|
|
|
|
|
|
|
|
|
|
NOTE: This options is not currently recommended. There is not now
|
|
|
|
|
NuttX file system that can handle the NAND back blocks or performs
|
|
|
|
|
wear-leveling other than NXFFS and NXFFS does not use a block driver
|
|
|
|
|
but, rather, operates directly upon the NAND MTD device.
|
|
|
|
|
|
|
|
|
|
config SAM34_NAND_NXFFS
|
|
|
|
|
bool "Create NAND FLASH NXFFS file system"
|
|
|
|
|
depends on MTD && MTD_NAND && FS_NXFFS && NXFFS_NAND
|
|
|
|
|
---help---
|
|
|
|
|
Create the MTD driver for the NAND and mount the NAND device as
|
|
|
|
|
a wear-leveling, NuttX FLASH file system (NXFFS). The downside of
|
|
|
|
|
NXFFS is that it can be very slow.
|
|
|
|
|
|
|
|
|
|
NOTE: NXFFS is recommended because (1) it can handle the NAND back
|
|
|
|
|
blocks and (1) performs wear-leveling.
|
|
|
|
|
|
|
|
|
|
endchoice # NAND FLASH configuration
|
|
|
|
|
|
2014-04-22 01:34:05 +02:00
|
|
|
endif
|
