Arm Community
Site
Search
User
Site
Search
User
Support forums
Architectures and Processors forum
ARM9 replacing Cortex M3
Jump...
Cancel
State
Accepted Answer
+1
person also asked this
people also asked this
Locked
Locked
Replies
9 replies
Subscribers
349 subscribers
Views
9099 views
Users
0 members are here
Cortex-M3
Arm9
Cortex-M
Options
Share
More actions
Cancel
Related
How was your experience today?
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
ARM9 replacing Cortex M3
Michael von Hauff
over 12 years ago
Top replies
Simon Craske
over 12 years ago
+1
verified
Note: This was originally posted on 7th January 2009 at http://forums.arm.com Mike, What are you trying to achieve? A 72MHz Cortex-M3 should be able to move upto around 144 MBytes per second using word...
Parents
0
Jacob Bramley
over 12 years ago
Note: This was originally posted on 8th January 2009 at
http://forums.arm.com
Bear in mind that on ARM, a word is 32 bits. Therefore, 18Mwords/s equates to 72MB/s.
If your DACs are external, your biggest problem is likely to be the rate at which you can drive the physical pins on the chip. The GPIO peripherals on most MCUs are fairly slow as it takes a relatively large amount of power to drive them quickly. Of course, this depends on how you are interfacing with the DAC, but most serial protocols implemented in MCU peripherals will not be able to transfer data that fast. Typically, they require at least two bus clocks for each bit that is sent, and they tend to have additional overheads too.
If the DACs are on-chip, you may not have this problem. On-chip DACs often don't have a sufficiently high precision for some applications, but you said that you only require 8 bits so if they're fast enough they may be worth considering. Also bear in mind that many on-chip DACs can be made to run faster at the cost of some precision, so a 10-bit DAC that isn't quite fast enough may be configurable to allow it to run faster if you accept that the lowest two bits will not be correct. This is certainly the case with the ADCs on NXP's LPC devices as I've used them before, and DACs are often similar in implementation to ADCs.
Cancel
Vote up
0
Vote down
Cancel
Reply
0
Jacob Bramley
over 12 years ago
Note: This was originally posted on 8th January 2009 at
http://forums.arm.com
Bear in mind that on ARM, a word is 32 bits. Therefore, 18Mwords/s equates to 72MB/s.
If your DACs are external, your biggest problem is likely to be the rate at which you can drive the physical pins on the chip. The GPIO peripherals on most MCUs are fairly slow as it takes a relatively large amount of power to drive them quickly. Of course, this depends on how you are interfacing with the DAC, but most serial protocols implemented in MCU peripherals will not be able to transfer data that fast. Typically, they require at least two bus clocks for each bit that is sent, and they tend to have additional overheads too.
If the DACs are on-chip, you may not have this problem. On-chip DACs often don't have a sufficiently high precision for some applications, but you said that you only require 8 bits so if they're fast enough they may be worth considering. Also bear in mind that many on-chip DACs can be made to run faster at the cost of some precision, so a 10-bit DAC that isn't quite fast enough may be configurable to allow it to run faster if you accept that the lowest two bits will not be correct. This is certainly the case with the ADCs on NXP's LPC devices as I've used them before, and DACs are often similar in implementation to ADCs.
Cancel
Vote up
0
Vote down
Cancel
Children
No data