Your code should compile without warnings. Often fixing the warning will fix your bug. Every warning can be fixed and removed. If you don’t know how to fix your warning, ask on the class message board.
Debugging from VS Code
If you want to try using the GDB debugger integrated in VSCode (along with the emulator – this doesn’t work on the board), you can follow these steps (note that sometimes it can be challenging using interactive debuggers with code that is driven by interrupts, like most of your labs):
Install GDB (This is already done in the VM we gave you):
sudo apt install gdb
You need to configure your compiler to generate “debug symbols”. Add the following line to the top-level CMakeLists.txt at line 10:
After you do that, it would be best to completely clean and rebuild your code:
cd ~/ecen330 rm -rf build_emu mkdir build_emu cd build_emu cmake .. -DEMU=1 make
In VSCode, open the .vscode/launch.json file to configure a debug session. You can edit the existing one, or create new ones.
Change this line to give your configuration a helpful name:
Change the “program” option to the path to your executable. Such as:
Go to your main.c and add a breakpoint to the start of main. You can do this by clicking the red dot next to the line number.
In the debugger panel, hit the green Play button. You should now be paused on your code like so:
Valgrind is a very useful tool for finding runtime issues with your code. This includes using uninitialized variables, referencing invalid pointers, and issues with malloc/free. This is only useable on the emulator, and you should have debug symbols enabled (see step #2 above).
Run valgrind on your program like this:
Look for the first error reported by valgrind and try and locate and fix the issue causing the error. This stack overflow post has lots of tips if you want to read more.
Building from Within VS Code
From within VSCode you can build your code as follows:
- To run
cmakeyou can press F1 and select Tasks: Run Task, cmake.
- To run
makeyou can press F1 and select Tasks: Run Task, make, or Tasks: Run Build Task, or Ctrl+Shift+B (on Windows).
The tasks have been set up in the tasks.json file. Consider adding a new task to this file that allows you to program lab1.elf to the board.