GPIO custom bus completed

During my 10th week at Aeste, I continued my unfinished business from the 9th week: bit banging the gpio to implement a custom 8 bits wide bus. I spent most of my time this week debugging the gpio driver for the custom bus. My code was ready at the beginning Read more…

Week 6: A presentation and a fake driver

I started my 6th week at Aeste by re-studying the beaglebone-6502 project done by matt porter of Texas Instruments. The reason my supervisor asked me to look back to this project was because it is simple and gives a good view of how remoteproc framework can be used. After studying Read more…

Week 5: Wrong path taken

My task for this week is to determine the interface of the remoteproc framework. As shameful as I could be, I still couldn’t figure out the interface and what is needed to make the framework runs. After some discussions with my supervisor, I was told that my work method was Read more…

Week 4: Setting up the test bench continued

It is almost unbelievable that it has been a month since I joined Aeste. This week has been my least productive week so far because I’d been trying to resolve non-important but work-hindering problems. During week 3, I managed to compile the remoteproc framework independently and the last thing that Read more…

Week 3: Setting up Linux kernel Test Bench

My task for this week is to compile the remoteproc framework, and setup its test bench. After analyzing the framework’s source code, I figured that it cannot be compiled as a modulable framework/driver. This means that I’ll have to compile the whole kernel in order to test the framework. To Read more…

Remoteproc/RPMsg Frameworks

As I mentioned in my previous post, my task for this week is to study the remoteproc framework. The goal is to discover how it works because later, I’ll be implementing about the same thing. Because of the limited resource and information on this specific framework, I had to start Read more…