Technische Universität München Release date: 03.11.

2022
Embedded Systems and Security Due date: 16:45 24.11.2022

Assignment 1: Morse Time

1 Introduction
As an additional opportunity to consolidate your skills, we offer three programming exercises.
They make up 20% of your overall grade as outlined in the first exercise session. You are
encouraged to discuss approaches and share experience with other students. But as it affects
your grade, your submission must of course be your own original work, and will be checked on
plagiarism.
The submissions are graded fully automatic once per hour after the grading machine is set
up (usually a day or two after the release date above). Together with your achieved points you
will be provided several logfiles which explain why your solution got this amount of points.
You can upload a new solution as often as you like during the submission period, but we will
ask questions in the case of a conspicuous high number of submissions. So don’t just adapt
your code to the grading framework. In the end, your best submission will be used for grading.
Should you find evidence that the grading does not follow the problem statement set out below,
please contact us as soon as possible, so we can look into the problem and fix it before too
many other students are affected.

2 Problem Description
2.1 Part A
In this part you have to write code that is able to send a given string in Morse code via LED1.
You probably want to use one of the example projects as a starting point, rename it to PartA,
and replace the example code with your solution.
Use the current ITU standard M.1677-1 for details on the Morse Code. You do not have to
implement punctuation characters. Letters and numbers according to Sections 1.1.1 and 1.1.2
are sufficient (excluding the accented e). The length of a dot has to be 100 ms ± 10 ms, confer
Section 2 of the standard for the length of the other signals. You can verify the length e.g.
by checking the time it takes to send a certain message divided by the length of the message
in number of dot equivalents. Send the string in the most simple form, i.e. not transmitting
a wrong character, then sending the correction signal and then the correct character. Instead
of the general transmission rules in Part II of the standard, send out the string repeatedly
while the device is on, without any calling or invitation signals but a pause of 5 s after each
transmission.
The string to send out is: I CAN MORSE

1
2.2 Part B
Copy the project from Part A, call the copy PartB and extend it as follows:
• The string is not sent continuously, but only once when Button1 is pressed down (not
when it is released).

• Once Button2 is pressed down (not when it is released), the time between the last and
second last press of Button1 in milliseconds is sent once in Morse code via LED1.
– If Button1 has not been pressed yet, send a single 0 digit.
– If Button1 has only been pressed once, send the time between boot and the first
press of Button1.
– The time has to be sent in decimal notation without leading zeroes or decimal point.
Round off to full milliseconds.

• While a transmission of Morse code is ongoing, any button press may be ignored.

• If both buttons are pressed simultaneously, the one pressed down first wins, and locks
the other one until the first one is released.
Make sure measuring the time between button presses does not interfere with your trans-
mission in Morse code. There are several solutions to this, e.g. using the SysTick or the
CCU4.

3 Hints
• Check the Board User’s Manual of the XMC Relax Kit (not the reference manual of the
XMC4500) for the GPIOs connected to the buttons (see Exercise 2, Problem 2.3.2)

• The buttons on the XMC Relax Lite Kit are equipped with RC filters for debouncing

• The drivers in XMClib may ease one task or the other

• Structure your program wisely

In case you opt for the CCU4 in Part B, here are a few hints:
• Do not be overwhelmed by the complexity of CCU4, you only need few of its features

• Remember how we used the CCU4 for PWM dimming in Exercise 2, Problem 2.3.3. Ex-
cept that this time you do not produce a PWM signal but let the timer count milliseconds
since it was last reset to 0 (the counter, not the whole peripheral).

• Use the search function of your PDF viewer to look up register names

• Remarks on section 22.6.1 of the manual:

2
 – Step 7 is not needed
– As we do not need to start timers synchronously, Step 9 reduces to setting the run
bit of the respective slice

4 Submission
4.1 What to Submit
• A ZIP archive containing both projects including all subfolders.
– I.e. your ZIP has to contain two project folders in its root, named PartA and PartB.

• Make sure the *.elf (or *.hex) files in your project are up to date, since they are used
without modification.

• If your submission neither contains an *.elf nor a *.hex file, your project will be rebuilt,
which adds a point of failure and might lead to zero points.

4.2 How to Submit

2. Make will create a .zip-file in ../.

3. Upload this archive via Moodle.