tordnat / microbitv2.2-environment

VSCode environment for debugging software developed for micro:bit v2.2.1 for Embedded Systems Course TTK4235

microbitv2.2-TTK4235-environment

VSCode environment for debugging software developed for micro:bit v2.2.1 for Embedded Systems Course TTK4235

Requirements

• Arm GNU Toolchain 12.X.X
• arm-none-eabi-gdb
• pyocd
• openocd

Installation

Since arm has decided not to include arm-none-eabi-gdb in apt package, you have to install Arm GNU Toolchain manually to use arm-none-eabi-gdb. This may also result with some libraries not being linked properly (which is described in common issues below).

Lab PC Installation

wget https://raw.githubusercontent.com/tordnat/microbitv2.2-TTK4235-environment/main/lab_installer.sh && chmod +x lab_installer.sh && sudo ./lab_installer.sh && pip3 install --user testresources==2.0.1 pyocd==0.34.3 

Normal Installation

wget https://raw.githubusercontent.com/tordnat/microbitv2.2-TTK4235-environment/main/installer.sh

chmod +x installer.sh

sudo ./installer.sh

Install Python dependencies

pip3 install --user testresources==2.0.1 pyocd==0.34.3

git clone https://github.com/tordnat/microbitv2.2-TTK4235-environment.git

Common issues

• Broken libraries

No such file libncursesw.so.5

    ln /usr/lib/x86_64-linux-gnu/libncursesw.so.6 /usr/lib/x86_64-linux-gnu/libncursesw.so.5

• Pip packages not on PATH

echo "export PATH=$HOME/.local/bin:$PATH" >> ~/.bashrc

• User doesn't have access to device

See this comment on the arm MBed blogpost for udev rules with pyocd.

Sources

• Debugging the BBC micro:bit with pyOCD and GDB
• Rust on BBC micro:bit - hardware debugging
• Micro:bit: DAPLink and the USB interface

microbitv2.2-environment's Issues

Unable to view register values in openOCD from terminal via GDB, but shows up in VSCode