In this thesis, we present a RISC-V processor that is extended with the MOLEN ISA extension, thereby granting it dynamic reconfiguration capabilities. The reconfigurable microcode (ρμ-code) of the MOLEN paradigm is modified to be suitable for (FPGA) implementation in the 64-bit Linux-capable CVA6 RISC-V processor. The set instruction performs reconfigurations by pointing it to a partial bitstream address, after which the execute instruction can perform operations on the reconfigured hardware. To this end, the concept of nested ρμ-code is presented, in which the reconfigurable opcodes are encapsulated in regular RISC-V instructions. Furthermore, a status instruction is introduced to enable the reconfiguration to be performed in the background. Consequently, the reconfiguration latency can be hidden, by allowing the CPU to do useful work during the reconfiguration. Using various experiments, it is demonstrated that the proposed implementation has a near-optimal reconfiguration performance and that the reconfiguration latency can be effectively hidden in typical cases.

Energiepaleis, a company that realizes sustainable home renovations, requested an application that uses augmented reality to show their customers beforehand, what certain sustainable devices would look like in their homes after renovations. A marker is placed on the spot where the device needs to stand and then the application will show the device on the screen. Before creating the application, research was done in the field of augmented reality. The research gave insights in the possibilities of augmented reality in mobile phone applications. The sustainable devices are represented by BIM models, these models are visualized using ARToolKit. The implemented system can be divided in three parts, augmented reality platform, user interface and the core of the application. The augmented reality platform handles the rendering of the models. The user interacts with the user interface and the core of the application controls the rendering based
on the user actions. Testing the application is done in two different ways, manual and automated testing. Manual testing is done after each new feature is implemented. Automated testing is used to assure correct behavior.