Making a score board in assembly language
Budget: $30 – $250 USD
I am looking for a developer who can create a score board in assembly language for me. I need the score board to have the functionality of displaying and updating scores only. I do not need it to be able to add, remove or update player names. The project will need to be completed to a high standard and is time-sensitive.
Here is the description of what is needed:
1) Design Properties
a) The system must use the following addressing modes in their most logical and appropriate uses (see functional requirements for some uses):
i) register mode
ii) index mode
(1) Putting data into an array (see 2.c below) would be a good use
iii) absolute mode
(1) Interacting with peripherals and hardware usually accomplishes this
iv)
indirect register mode or indirect autoincrement mode
(1) Reading data from an array (see 2.c.iii below) would be a good use.
b) The system must use at least one subroutine
c) The system must use at least one interrupt service routine
d) The system must use at least two peripherals (not including General Purpose I/O)
2) Functional Requirements
a) The system must possess and use a watchdog timer to ensure the program does not get stuck permanently.
b) The system must output some type of "heartbeat" indication (unless I/O limitations prevent this).
c) The system must maintain historical data of either a key data input value or output value over a fixed time base in an array.
i) The amount of data retained in the history must be appropriate and the frequency of storage must be appropriate for the application.
ii) It should be possible to easily determine the most recently written data
iii) For example if the system were a temperature monitoring/controlling system; every 30 seconds the current temperature should be placed in the array. It would be possible to determine the temperature 2 minutes ago, by looking at the location 4 records prior than the most recent data location.
Here is the description of what is needed:
1) Design Properties
a) The system must use the following addressing modes in their most logical and appropriate uses (see functional requirements for some uses):
i) register mode
ii) index mode
(1) Putting data into an array (see 2.c below) would be a good use
iii) absolute mode
(1) Interacting with peripherals and hardware usually accomplishes this
iv)
indirect register mode or indirect autoincrement mode
(1) Reading data from an array (see 2.c.iii below) would be a good use.
b) The system must use at least one subroutine
c) The system must use at least one interrupt service routine
d) The system must use at least two peripherals (not including General Purpose I/O)
2) Functional Requirements
a) The system must possess and use a watchdog timer to ensure the program does not get stuck permanently.
b) The system must output some type of "heartbeat" indication (unless I/O limitations prevent this).
c) The system must maintain historical data of either a key data input value or output value over a fixed time base in an array.
i) The amount of data retained in the history must be appropriate and the frequency of storage must be appropriate for the application.
ii) It should be possible to easily determine the most recently written data
iii) For example if the system were a temperature monitoring/controlling system; every 30 seconds the current temperature should be placed in the array. It would be possible to determine the temperature 2 minutes ago, by looking at the location 4 records prior than the most recent data location.