Fix spelling of ARM Cortex
It's Cortex-Xn, not Cortex Xn or cortex xn or cortex-xn or CORTEX-Xn or CortexXn. Further it's Cortex-M0+, not M0plus. Cf. http://www.arm.com/products/processors/index.php Consistently write it the official way, so that it stops propagating. Originally spotted in the documentation, it mainly affects code comments but also Atmel SAM3/SAM4/SAMV, NiietCM4 and SiM3x flash driver output. Found via: git grep -i "Cortex " git grep -i "Cortex-" | grep -v "Cortex-" | grep -v ".cpu" git grep -i "CortexM" Change-Id: Ic7b6ca85253e027f6f0f751c628d1a2a391fe914 Signed-off-by: Andreas Färber <afaerber@suse.de> Reviewed-on: http://openocd.zylin.com/3483 Tested-by: jenkins Reviewed-by: Marc Schink <openocd-dev@marcschink.de> Reviewed-by: Andreas Fritiofson <andreas.fritiofson@gmail.com>
This commit is contained in:
committed by
Freddie Chopin
parent
f630fac2e7
commit
0c8ec7c826
@@ -226,7 +226,7 @@ static int ChibiOS_update_stacking(struct rtos *rtos)
|
||||
/* Sometimes the stacking can not be determined only by looking at the
|
||||
* target name but only a runtime.
|
||||
*
|
||||
* For example, this is the case for cortex-m4 targets and ChibiOS which
|
||||
* For example, this is the case for Cortex-M4 targets and ChibiOS which
|
||||
* only stack the FPU registers if it is enabled during ChibiOS build.
|
||||
*
|
||||
* Terminating which stacking is used is target depending.
|
||||
@@ -248,7 +248,7 @@ static int ChibiOS_update_stacking(struct rtos *rtos)
|
||||
struct ChibiOS_params *param;
|
||||
param = (struct ChibiOS_params *) rtos->rtos_specific_params;
|
||||
|
||||
/* Check for armv7m with *enabled* FPU, i.e. a Cortex M4 */
|
||||
/* Check for armv7m with *enabled* FPU, i.e. a Cortex-M4 */
|
||||
struct armv7m_common *armv7m_target = target_to_armv7m(rtos->target);
|
||||
if (is_armv7m(armv7m_target)) {
|
||||
if (armv7m_target->fp_feature == FPv4_SP) {
|
||||
|
||||
@@ -430,7 +430,7 @@ static int FreeRTOS_get_thread_reg_list(struct rtos *rtos, int64_t thread_id, ch
|
||||
thread_id + param->thread_stack_offset,
|
||||
stack_ptr);
|
||||
|
||||
/* Check for armv7m with *enabled* FPU, i.e. a Cortex M4F */
|
||||
/* Check for armv7m with *enabled* FPU, i.e. a Cortex-M4F */
|
||||
int cm4_fpu_enabled = 0;
|
||||
struct armv7m_common *armv7m_target = target_to_armv7m(rtos->target);
|
||||
if (is_armv7m(armv7m_target)) {
|
||||
|
||||
@@ -109,7 +109,7 @@ static int mqx_valid_address_check(
|
||||
enum mqx_arch arch_type = ((struct mqx_params *)rtos->rtos_specific_params)->target_arch;
|
||||
const char * targetname = ((struct mqx_params *)rtos->rtos_specific_params)->target_name;
|
||||
|
||||
/* Cortex M address range */
|
||||
/* Cortex-M address range */
|
||||
if (arch_type == mqx_arch_cortexm) {
|
||||
if (
|
||||
/* code and sram area */
|
||||
|
||||
@@ -182,7 +182,7 @@ int64_t rtos_generic_stack_align8(struct target *target,
|
||||
stacking, stack_ptr, 8);
|
||||
}
|
||||
|
||||
/* The Cortex M3 will indicate that an alignment adjustment
|
||||
/* The Cortex-M3 will indicate that an alignment adjustment
|
||||
* has been done on the stack by setting bit 9 of the stacked xPSR
|
||||
* register. In this case, we can just add an extra 4 bytes to get
|
||||
* to the program stack. Note that some places in the ARM documentation
|
||||
|
||||
Reference in New Issue
Block a user