• State Verified Answer
  • Replies 3 replies
  • Subscribers 68 subscribers
  • Views 2079 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 100925
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Data processing limits?

Elena

Hello,

I am planning to develop an application in which I need to do some image processing (probably using open CV libraries), and I would like to know if the nRF51822 processor could support that kind of data processing (the speed is not a problem, it is not a real time application). In the case I can't do the work explained, Could somebody tell me which are the data processing limits for a Cortex-M0 processor?

Thanks for your help,

Best Regards

Parents
  • 0

    According to the Cortex-M0 specs (www.arm.com/.../cortex-m0.php) you should see up to 1.21 DMIPS / MHz. The nRF51 CPU clock is 16 MHz.

    If you want to do a more detailed analysis or test case, you can use gcc-arm or the free eval version of Keil (www.keil.com/.../mdk.asp) to compile some examples and see the code size. If there are very specific procedures you have in mind, it's possible to use the Keil simulator (or debug an nRF51) and step through the assembly. There is no memory cache in the nRF51, and most instructions are single-cycle (infocenter.arm.com/.../index.jsp, so the number of instructions is a strong indicator of performance.

    Especially when dealing with floating point data it is useful to see the assembly or linker output to get a sense of complexity and performance.

Reply
  • 0

    According to the Cortex-M0 specs (www.arm.com/.../cortex-m0.php) you should see up to 1.21 DMIPS / MHz. The nRF51 CPU clock is 16 MHz.

    If you want to do a more detailed analysis or test case, you can use gcc-arm or the free eval version of Keil (www.keil.com/.../mdk.asp) to compile some examples and see the code size. If there are very specific procedures you have in mind, it's possible to use the Keil simulator (or debug an nRF51) and step through the assembly. There is no memory cache in the nRF51, and most instructions are single-cycle (infocenter.arm.com/.../index.jsp, so the number of instructions is a strong indicator of performance.

    Especially when dealing with floating point data it is useful to see the assembly or linker output to get a sense of complexity and performance.

Children
No Data
Related