English
Migrating ARM7 Code to a Cortex-M3 MCU (Part 2)
In Part 1 in this series, I dealt with the myriad of details relating to exception vector table formating, startup code/stack configuration, remapping RAM functions, and hardware interrupt configuration that a programmer must be concerned with porting code from an existing ARM7 to the Cortex-M3 core. Now in this second part, the tutorial continues with a discussion of software interrupts, fault handling, the SWP command, instruction time, assembly language, and optimizations.
|
E-mail This Article | 
|
|
Printer-Friendly Page |
|
||||||
Related Articles
- Migrating ARM7 code to a Cortex-M3 MCU
- Improving ASIP code generation and back-end compilation: Part 2
- A designer's guide to a new industrial control paradigm
- Beefing up the Cortex-M3-based MCU to Handle 480 Mbps High-speed USB
- Paving the way for the next generation audio codec for True Wireless Stereo (TWS) applications - PART 2 : Increasing play time
New Articles
- How NoC architecture solves MCU design challenges
- Automating Hardware-Software Consistency in Complex SoCs
- Beyond Limits: Unleashing the 10.7 Gbps LPDDR5X Subsystem
- How to Design Secure SoCs: Essential Security Features for Digital Designers
- System level on-chip monitoring and analytics with Tessent Embedded Analytics