mcu
/
libopencm3
mirror of https://github.com/libopencm3/libopencm3.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
1872 Commits
2 Branches
1 Tag
21 MiB
Tree: c09ebbc956
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c09ebbc956'
${ noResults }
libopencm3/lib/vf6xx/vector_chipset.c

40 lines
1.2 KiB
Raw Normal View History

vf6xx: initial add of Vybrid VF6xx support Freescale Vybrid is a familiy of ARM SoC, wheras the VF6xx models have two cores in one SoC, a Cortex-A5 and a Cortex-M4. This adds initial support for the Cortex-M4 in the libopencm3 library. By using two different ram areas (pc_ram and ps_ram) the user can put the code in a RAM area bounded to the code bus. The data can be stored in the data area. However, currently the initial values of for the variables in the data section are stored in the code section and copied to the ram section by the initialization code (like it's copied from ROM to RAM on microcontrollers).
11 years ago
/*
* This file is part of the libopencm3 project.
*
* Copyright (C) 2014 Stefan Agner <stefan@agner.ch>
*
* This library is free software: you can redistribute it and/or modify
* it under the terms of the GNU Lesser General Public License as published by
* the Free Software Foundation, either version 3 of the License, or
* (at your option) any later version.
*
* This library is distributed in the hope that it will be useful,
* but WITHOUT ANY WARRANTY; without even the implied warranty of
* MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the
* GNU Lesser General Public License for more details.
*
* You should have received a copy of the GNU Lesser General Public License
* along with this library. If not, see <http://www.gnu.org/licenses/>.
*/
#include <libopencm3/cm3/scb.h>
vf6xx: set vector table to memory Set Vector Table Offset to memory location of our vector table. Since we put the whole programm including the vector table into memory, we need to make use of the Cortex-M4 system control block Vector Table Offset Register (VTOR).
11 years ago
extern vector_table_t vector_table;
vf6xx: initial add of Vybrid VF6xx support Freescale Vybrid is a familiy of ARM SoC, wheras the VF6xx models have two cores in one SoC, a Cortex-A5 and a Cortex-M4. This adds initial support for the Cortex-M4 in the libopencm3 library. By using two different ram areas (pc_ram and ps_ram) the user can put the code in a RAM area bounded to the code bus. The data can be stored in the data area. However, currently the initial values of for the variables in the data section are stored in the code section and copied to the ram section by the initialization code (like it&#39;s copied from ROM to RAM on microcontrollers).
11 years ago
static inline void pre_main(void)
{
/*
* For Vybrid we need to set the stack pointer manually
* since the boot ROM has its own stack
*/
asm ( \
"ldr sp,=_stack;" \
);
vf6xx: set vector table to memory Set Vector Table Offset to memory location of our vector table. Since we put the whole programm including the vector table into memory, we need to make use of the Cortex-M4 system control block Vector Table Offset Register (VTOR).
11 years ago
/* Set Vector Table Offset to our memory based vector table */
SCB_VTOR = (uint32_t)&vector_table;
vf6xx: enable floating-point coprocessor
11 years ago
/* Enable access to Floating-Point coprocessor. */
SCB_CPACR |= SCB_CPACR_FULL * (SCB_CPACR_CP10 | SCB_CPACR_CP11);
vf6xx: initial add of Vybrid VF6xx support Freescale Vybrid is a familiy of ARM SoC, wheras the VF6xx models have two cores in one SoC, a Cortex-A5 and a Cortex-M4. This adds initial support for the Cortex-M4 in the libopencm3 library. By using two different ram areas (pc_ram and ps_ram) the user can put the code in a RAM area bounded to the code bus. The data can be stored in the data area. However, currently the initial values of for the variables in the data section are stored in the code section and copied to the ram section by the initialization code (like it&#39;s copied from ROM to RAM on microcontrollers).
11 years ago
}