[GSoC 2018: SDHCI MMC Driver]: Third Phase Outline

Blog post by krish_iyer on Thu, 2018-07-12 10:52

So here we are in the final week of the second phase of this project. I would like to address what was planned for this phase and what we have achieved and will proceed to plan for the third phase. Second Phase Highlights We were successful in register mapping through MMUIO. We have created a bus manager but not linked with controller ATM. Interrupts have not been implemented but also not required in this phase.

[GSoC 2018: SDHCI MMC Driver]: Week #8

Blog post by krish_iyer on Mon, 2018-07-09 20:09

Hey guys! Last week we have improved the code and made it more readable. We have completed the reset and clock sequence and proceed with power sequence. In the 4th step of the sequence, it asks to get the Operation Conditions Register(OCR) value of SD card. In the SD host controller spec, in command register there is command index bits which mention about setting up command number specified in bits 45-40 of the command-format in SD Memory Card Physical Layer Specification.

[GSoC 2018: SDHCI MMC Driver]: Week #7

Blog post by krish_iyer on Tue, 2018-07-03 18:27

Finally, we got the register mapping work and they are responsive, we have tested by enabling software reset bit and it has all the default values of registers which are set by Qemu except the present state register and capabilities register. These both should be left unaffected as mentioned in the spec. We are following SD Host specification version 1.00 for now, which also doesn’t support UHS but Qemu seems to be supporting it well.

[GSoC 2018: SDHCI MMC Driver]: Week #6

Blog post by krish_iyer on Tue, 2018-06-26 15:04

Hello everyone! Here’s the update of week #6, in the last update we were not able to access the registers. When we tried mapping it, there were all zeros. so we knew there’s something wrong in the way we were accessing the register and in between this we got to know that qemu emulation for sdhc hardware only supports spec version 2 and 3 and the spec which we intended to implement was 4.

[GSoC 2018: SDHCI MMC Driver]: Second Phase Outline

Blog post by krish_iyer on Thu, 2018-06-14 11:51

Hey, folks! So we are at the end of first phase of the project and I had expected that I would be able to implement PIO but it seems that I have lagged a bit. Till now we have got our controller driver setting up the mmc bus and mmc disk driver to publish a slot. To implement PIO before DMA, also requires register mapping which we are currently working on.

[GSoC 2018: SDHCI MMC Driver]: Week #5

Blog post by krish_iyer on Mon, 2018-06-11 18:34

Hey, here I am with another update! Last time I mentioned about splitting up the module but due to time constraint we agreed to skip that currently and move forward. After setting up the bus, I thought it would be bus manager which needs to be setted up for data transfer and other read and write operations but it turns out to few things which need to be done before that and it’s actually not the bus manager who do these operations, it will just create an instance of the interrupts and the operations to be done, and call back after it’s done.

[GSoC 2018: SDHCI MMC Driver]: Week #4

Blog post by krish_iyer on Sun, 2018-06-03 21:11

Hey everyone! here I am with another update. Last time I had concluded-“PCI class is not discoverable to device manager”, it was actally a bit wrong. So korli explained that device manager won’t load a driver which system doesn’t know so in order for device manager to consider sdhci bus device, it has to be added under a condition of the devices of same type. So we added it under “disk”.

[GSoC 2018: SDHCI MMC Driver]: Week #3

Blog post by krish_iyer on Mon, 2018-05-28 20:35

Sorry folks! for the delay in the updates. I was pretty much occupied by end term exams. After initial setup, we divided the our initial plan in following steps. Discover PCI bus Filter out SDHC device from the connected devices on the bus. Register the device as the child node. As I was able to load the driver, it exited in between somewhere from the supports_device(). So I broke the conditions where it checks for the bus, device ID and vendor ID, in order to see where exactly it was not satisfying the condition.

[GSoC 2018: SDHCI MMC Driver]: Week #1 and #2

Blog post by krish_iyer on Sun, 2018-05-06 17:58

Hey folks! here’s the updates of past two weeks on the project! I have cloned the latest haiku source and built the image file. With the generated image file I have emulated sdhci-pci device successfully. Following are the instructions to be followed: Cloning the source code git clone https://github.com/haiku/haiku.git git clone https://github.com/haiku/buildtools.git Compiling Source Code Create a directory where you are going to save the build image and related files

[GSoC 2018] SDHCI MMC Driver

Blog post by krish_iyer on Wed, 2018-04-25 22:08

Hello everyone! I am B Krishnan Iyer(irc: krish-iyer, telegram: krish_iyer trac: krish_iyer, github: krish-iyer), currently pursuing bachelor's in Electrical and Electronics Engineering at Amrita University. I am one of the three GSoC participants with Haiku. I am greatful to everyone for accepting me as an intern. This summer I will be developing SDHCI MMC driver. About Me My area of interest lies in Embedded system, apart from academics, I work on developing drivers for microcontrollers.