| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| en:multiasm:exercisesbook:avr:sut [2026/04/30 10:02] – [Handling of the buffered 4 digit, 7-segment display] pczekalski | en:multiasm:exercisesbook:avr:sut [2026/05/04 14:50] (current) – [Visualising Instruction Execution Time Using an Oscilloscope] pczekalski |
|---|
| |
| |
| ==== Handling of the buffered 4 digit, 7-segment display ==== | ==== Handling of the buffered 4-digit, 7-segment display ==== |
| To display a digit in the 4x7seg. display, there are two definitions needed: the shape of a digit (or other symbol), and its position (1,2,3,4: a binary mask). | To display a digit in the 4x7seg. display, there are two definitions needed: the shape of a digit (or other symbol), and its position (1,2,3,4: a binary mask). |
| |
| .byte 0xC0, 0xF9, 0xA4, 0xB0, 0x99, 0x92, 0x82, 0xF8, 0x80, 0x90 | .byte 0xC0, 0xF9, 0xA4, 0xB0, 0x99, 0x92, 0x82, 0xF8, 0x80, 0x90 |
| </code> | </code> |
| | In a common-anode configuration, the active signal to turn on a segment is LOW (0), and to turn it off, it is HIGH (1). The state of a single digit is represented by an 8-bit mask: 7 segments to build the symbol and a DP (decimal point). For example, a digit 7 is represented by bits corresponding to segments "a", "b", and "c" set to 0 (to turn segments "a", "b", and "c" on) and the remaining bits set to 1 (to turn them off), so the corresponding binary value looks as follows: 11111000b, hence the hexadecimal value is 0xF8 (as in the code above). The MSB bit represents DP, and the LSB segment "a". This definition affects how one loads data into the shift register: starting from MSB towards LSB, because of the way the register is built and connected to the segments - refer to the function ''display_digit'' below. |
| | |
| <note tip>Naturally, it is possible to expand those definitions to display other symbols, e.g., hexadecimal digits such as A,b,C,d,E,F.</note> | <note tip>Naturally, it is possible to expand those definitions to display other symbols, e.g., hexadecimal digits such as A,b,C,d,E,F.</note> |
| |
| |
| <note tip>Nodes are interconnected in pairs: 1-2, 3-4, 5-6, 7-8, 9-10. Scenarios for data transmission between MCUs require booking and the use of correct nodes for sending and receiving messages.</note> | <note tip>Nodes are interconnected in pairs: 1-2, 3-4, 5-6, 7-8, 9-10. Scenarios for data transmission between MCUs require booking and the use of correct nodes for sending and receiving messages.</note> |
| | |
| | ==== Visualising Instruction Execution Time Using an Oscilloscope ==== |
| | Let's try to visualise how code operates the GPIO. Naturally, in the remote lab, it is not possible to do it remotely, so here we present some desk-based experiments.\\ |
| | The ''LAT_PIN'' is GPIO4, and an oscilloscope is connected to it. |
| | In the function that displays a single digit, there is a section that loads a binary mask into the internal registers, enabling the LED segments that constitute the digit to be turned on and off. It is: |
| | <code asm> |
| | ... |
| | sbi LAT_PORT, LAT_PIN |
| | cbi LAT_PORT, LAT_PIN |
| | ... |
| | </code> |
| | |
| | The figures {{ref>arduinounodigitoscilloscope1}} and {{ref>arduinounodigitoscilloscope2}} present the ''LAT_PIN'' signal, called periodically during the display of the consecutive digits (they represent the same signal but differ by the oscilloscope time base for better observation).\\ |
| | ''SBI'' causes the signal to rise, while ''CBI'' to fall. Thus, the HIGH time is the exact time during which the CBI instruction executes. It takes about 120-130ns.\\ |
| | The Arduino Uno operates at 16 MHz, so each cycle is 1/16000000 s, which is about 63 ns. According to the documentation, ''CBI'' takes 2 cycles, which is ~126ns. |
| | |
| | <figure arduinounodigitoscilloscope1> |
| | {{:en:multiasm:exercisesbook:avr:pic_1054.png?300|}} |
| | <caption>''LAT_PIN'' signal (50ns time base)</caption> |
| | </figure> |
| | |
| | <figure arduinounodigitoscilloscope2> |
| | {{:en:multiasm:exercisesbook:avr:pic_1055.png?300|}} |
| | <caption>''LAT_PIN'' signal (25ns time base)</caption> |
| | </figure> |
