Please note: We are aware of an issue affecting replies on the Arm Community forums, which may not be loading as expected.

We apologize for any inconvenience and appreciate your patience while we investigate and work to resolve the issue.

Thank you for your understanding.

  • State Accepted Answer
  • Locked Locked
  • Replies 3 replies
  • Subscribers 349 subscribers
  • Views 3384 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Migration from Cortex M4 to Cortex R5F

AakashKedia22

Hi Champs,

I intend to migrate from Cortex M4 to Cortex R5F. As I understand both the CPUs seem very similar in a lot of aspects MPU, instruction set and yet is very different from the other. I am using ARM-CLANG as a compiler so I am not worried about the instruction set.

I would like to know which are the major points where I would have to change my software like interrupt handling, startup (maybe ?), systick handling.. Can I get an overview with this information ?

Best Regards,
Aakash

Parents
  • +1

    Migrating from Cortex-M4 to Cortex-R5F would require you to make some changes to your software. Here's an overview of some of the major points:

    Interrupt Handling: Cortex-R5F has a different interrupt controller compared to Cortex-M4. You would need to update your code to handle interrupts in a different way.

    Startup: Cortex-R5F has a different memory map compared to Cortex-M4. Therefore, you would need to update your startup code to correctly initialize the new memory map.

    Systick Handling: Cortex-R5F has a different Systick timer compared to Cortex-M4. You would need to update your code to handle the new Systick timer.

    Cache and Memory Protection: Cortex-R5F has an MPU (Memory Protection Unit) and cache memory which are not present in Cortex-M4. You would need to modify your code to take advantage of these features.

    Floating-Point Unit: Cortex-R5F has a dedicated floating-point unit (FPU), while Cortex-M4 has a separate FPU or none at all. If your code uses floating-point operations, you would need to modify it to take advantage of the Cortex-R5F FPU.

    These are some of the major differences that you would need to consider when migrating from Cortex-M4 to Cortex-R5F.

Reply
  • +1

    Migrating from Cortex-M4 to Cortex-R5F would require you to make some changes to your software. Here's an overview of some of the major points:

    Interrupt Handling: Cortex-R5F has a different interrupt controller compared to Cortex-M4. You would need to update your code to handle interrupts in a different way.

    Startup: Cortex-R5F has a different memory map compared to Cortex-M4. Therefore, you would need to update your startup code to correctly initialize the new memory map.

    Systick Handling: Cortex-R5F has a different Systick timer compared to Cortex-M4. You would need to update your code to handle the new Systick timer.

    Cache and Memory Protection: Cortex-R5F has an MPU (Memory Protection Unit) and cache memory which are not present in Cortex-M4. You would need to modify your code to take advantage of these features.

    Floating-Point Unit: Cortex-R5F has a dedicated floating-point unit (FPU), while Cortex-M4 has a separate FPU or none at all. If your code uses floating-point operations, you would need to modify it to take advantage of the Cortex-R5F FPU.

    These are some of the major differences that you would need to consider when migrating from Cortex-M4 to Cortex-R5F.

Children
No data