len0rd/FreeRTOS-Kernel
1
0
Fork 0
mirror of https://github.com/FreeRTOS/FreeRTOS-Kernel.git synced 2025-09-12 00:57:44 -04:00
Code Issues Projects Releases Packages Wiki Activity

Update readme.txt in each Renesas RX folder regarding to Notes *1 and *2 (both are RX100 port)

Browse source
This commit is contained in:
NoMaY (a user of Japan.RenesasRulz.com) 2020-08-31 21:57:23 +09:00
parent 72d0ec4f00
commit 847340f31e
13 changed files with 78 additions and 39 deletions
Download patch file Download diff file Expand all files Collapse all files

9
portable/GCC/RX100/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/GCC/RX600/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/GCC/RX600v2/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/GCC/RX700v3_DPFPU/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/IAR/RX100/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/IAR/RX600/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/IAR/RX700v3_DPFPU/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/IAR/RXv2/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/Renesas/RX100/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/Renesas/RX200/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/Renesas/RX600/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/Renesas/RX600v2/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.

9
portable/Renesas/RX700v3_DPFPU/readme.txt
View file

@ -43,10 +43,13 @@ Notes:
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is not used, please define configSETUP_TICK_INTERRUPT() (in FreeRTOSConfig.h) and provide
the configuration function.
the configuration function. Please be aware that port.c is hard coded to use CMT0 though it seems to be
configured to use any CMTn according to the definition of configTICK_VECTOR (in FreeRTOSConfig.h).
*1: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration.
*2: If the application writer wants to use their own tick interrupt configuration when tickless idle
functionality is used, please modify port.c for the configuration. Please be aware that port.c is
hard coded to use CMT0 though it seems to be configured to use any CMTn according to the definition of
configTICK_VECTOR (in FreeRTOSConfig.h).
*3: RX100 ports are also available.