This week, I was able to pinpoint the reason behind the erratic behaviour of the board. Upon rereading the documentation for the Harmony USB Libraries, I found out that in particular for the PIC32MZ family of microcontrollers which includes the board that we were working on, the buffers that are sent to most library functions are required to be placed in coherent memory and aligned at a 16 byte boundary. This was not needed in the Ethernet Starter Kit as Read more…
This week I started working on front end for Dashboard. Dr Shawn has told me all the functionalities and all the things that are needed for the Dashboard so I need to find ways how to make all the things work. Actually it is quite hard for me to do the front end as most of the things that need to be included are customized so I spend a lot of time studying and trying to understand about admin on Read more…
This week, I explained to Dr. Shawn about the fact that the USB code managed to work on the PIC32MX but not the real boards in which he suggested to reduce the clock speed of the real boards to match the ones on the PIC32MX as it could be some form of rate-limiting for keyboards since the clock speed on the real boards were higher. Tried it but unfortunately it did not work. However, the rate-limiting idea gave a bit Read more…
This is my second time diving into the vast ocean of Poco Cache library source code. And since this is my second time studying it, I actually get a much better understanding and overview of how the Poco Cache really works. It works by event handling. The moment there is a need for the elements to be removed, it will fire an event to notify the strategy on which elements it would like to remove, and it will then pass Read more…
This week I worked on the front end of Boards and Projects. This two has different front end. For Boards the front end is quite simple because all the information are in list. Meanwhile for Projects Dr Shawn decided to make it in Card style. But the functionalities for both are quite similar. To help me understand how to build the front end I refer a lot to admin on rest demo because there are a few same functionalities in Read more…
After having much fun with the PIC32 Starter Kit, I am currently moving on to the real boards. As expected, the previous USB code that worked on the starter kit no longer work properly on the real boards. Got the 2 LEDs to work on the boards and hence started debugging the code but not much progress was made besides the fact that the computer detects it as a HID Keyboard. A quick check at the board documentation did hint Read more…
Last week was my final week in AESTE and I managed to wrap up all the C++ Drivers to spec thanks to Dr Shawn’s guidance as he nudged me ever so slightly in the right direction by questioning my thought process and making me reflect on the naming conventions that I’ve chosen. Fair enough, I’ve been inconsistent in some parts of my code in following the Camel Casing convention therefore I had to spend some time correcting them. However, when Read more…
I started this week by working on the bugs that I overlooked and it took me 2 days to solve all the bugs. After that I straight away working on the other project with another intern. We start working on the authentication part first which took us quite a while to fix it. Then we worked on CRUD (Create,Read,Update,Delete). Dr Shawn told us that he wants the front end to be in Card style but to be safe we started Read more…
This week started off with me making a terrible mistake. Dr. Shawn asked me to restructure the code as we need to start pushing any work related to front-end to the remote repository. I was instructed to download the zip file from admin-on-rest, unzip the file and push the whole thing into the remote repository. However, I went on git cloning the admin-on-rest repository and pushing it to the project repository, as I had always thought git cloning and zipping Read more…
Last week I successfully completed the Gpio and Spi driver heavily inspired by a third-party API so that there is consistency in the way the code is written and how it is called. Referring to the latter, I’ve alse included a T3 namespace so that functions are now called via the format, T3::Gpio::Write(int dvalue) for example. This week I will be wrapping up by internship in Aeste, it has been a tremendous learning experience so far, I’ve managed to hone Read more…