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

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
03/19/10 15:17
Read: times


 
#174324 - Seperate display processor
Responding to: ???'s previous message
The display is graphical, and has to respond to the slave states, the keypad, and the master state.

Sorry, that should have read 'the state of the master'.

If the current master processor needs to make a lot of filtering and decisions of the key presses and measurements before being able to decide what should be drawn, then there can be a reason to separate that functionality from the functionality of actually performing the draw primitives on the display

Yes, that is the case

Divide and conquer works best if both sides of the split has a significant size.
So the question then is if there will be a significant amount of work/code/state storage left for the original master to handle, if the display management is moved to a new processor.


Yes, the master has a lot to do without the display. There are > 10 inputs to scan, and decisions made on the input conditions. Then also the RS485 network.
Some of the inputs are rotary encoders, which go to interrupts. For instance, on forward movement, weedkiller has to be sprayed, except where planting is to be done.
The master is busy.
The display is a 128 x 64 Graphics LCD with ST7565 controller.
Fonts must be looked up, etc.
Thank you
Johan Smit

List of 25 messages in thread
TopicAuthorDate
Seperate display processor            01/01/70 00:00      
   Is the display the master?            01/01/70 00:00      
      Bottlenecks?            01/01/70 00:00      
         I disagree            01/01/70 00:00      
            Both            01/01/70 00:00      
               not necessarily            01/01/70 00:00      
                  Special cases are special. General cases quite common.            01/01/70 00:00      
                     making the specific general            01/01/70 00:00      
                        well, specialisation means loss of generalisation :p            01/01/70 00:00      
                           what is this            01/01/70 00:00      
                              And if it doesnt?            01/01/70 00:00      
                                 Seperate display processor            01/01/70 00:00      
                                    never seen a better reason            01/01/70 00:00      
                                       To Per            01/01/70 00:00      
                                          Did you read the first post in the thread?            01/01/70 00:00      
                                             an example, please ...            01/01/70 00:00      
                                                Divide-and-conquer requires reasonable split percentages            01/01/70 00:00      
                                             Seperate display processor            01/01/70 00:00      
   What kind of display?            01/01/70 00:00      
      Cross-reference            01/01/70 00:00      
         Seperate display processor            01/01/70 00:00      
            How does it work currently...            01/01/70 00:00      
               Seperate display processor            01/01/70 00:00      
            dirt cheap            01/01/70 00:00      
               Seperate display processor            01/01/70 00:00      

Back to Subject List