Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
12/08/10 13:19
Read: times


 
#179998 - Hw-acceleration
Responding to: ???'s previous message
A note about multiple interrupts for same device.

The need is way less now than it was 10 years ago. With almost zero cost (chip area, power consumption, ...) most peripherials are very much accelerated. And the ARM chips don't need to bother about software compatibility with 20 year old source code.

Most UART now have FIFO for reaceive and transmit, so buffer overruns/underruns are not a problem anymore. And the high core speeds means that you can quick quickly handle an interrupt in case you need a response time when last character has been received (normally older protocols with not too high baudrates).

Many UART have hw acceleration for bus use, where they can drive a separate pin to switch on/off a transmitter or switch the transceiver between receive and transmit mode.

Many CAN have multiple transmit buffers so the program can insert a number of frames and the chip will all the time prioritize which of the pending frames that have highest priority and that should be sent as soon as the cable is ready to accept the frame.

The SPI interfaces are often more advanced SSP interfaces with support for FIFO and DMA.

Not needing compatibility with old software really helps a lot when taking advantage of advances in process technologies.

List of 12 messages in thread
TopicAuthorDate
[ARM] Default state of interrupts            01/01/70 00:00      
   Normally vectorized interrupt controller            01/01/70 00:00      
      but isn't this the case with ALL microcontrollers?            01/01/70 00:00      
         Often three layers of enable            01/01/70 00:00      
            This is the case here (LPC17xx)...            01/01/70 00:00      
               May vary a lot            01/01/70 00:00      
      Not the case anymore for Cortex-M3s.            01/01/70 00:00      
   Startup code?            01/01/70 00:00      
      not startup code, but the after-reset state            01/01/70 00:00      
         Hw-acceleration            01/01/70 00:00      
   According to the datasheet of my CM3 ...            01/01/70 00:00      
      ... but if we dig deeper to the datasheets...            01/01/70 00:00      

Back to Subject List