Searched refs:map (Results 1 – 8 of 8) sorted by relevance
14 system functionality. The struct created to map the alternate functions is27 - `map`: Define the macro that will be used to generate code for an specific34 - `pins` (required): The pin map itself57 map: PIC32CX_PINMUX128 is used to generate file names and map peripherals.140 datasheet. Any variation with exception must map all pins to allow users access207 map: SAM_PINMUX
294 const struct mec_nvic_map *map = gr->nmap; in enable_nvic_directs() local297 NVIC_EnableIRQ(map[m].nvic_direct); in enable_nvic_directs()
14 * You can find details on the PolarFireSoC Memory map in the mpfs-memory-hierarchy.md71 * So the memory map will look like once apportion in startup code:
15 * You can find details on the PolarFireSoC Memory map in the mpfs-memory-hierarchy.md83 * So the memory map will look like once apportion in startup code:
16 * You can find details on the PolarFireSoC Memory map in the mpfs-memory-hierarchy.md74 * So the memory map will look like once apportion in startup code:
15 * You can find details on the PolarFireSoC Memory map in the mpfs-memory-hierarchy.md82 * So the memory map will look like once apportion in startup code:
30 * You can find details on the PolarFireSoC Memory map in the mpfs-memory-hierarchy.md
20 * You can find details on the PolarFireSoC Memory map in the mpfs-memory-hierarchy.md
