The content of this topic has been archived on 1 Apr 2018. There are no obvious gaps in this topic, but there may still be some posts missing at the end.
I a interested in getting SD storage onto the Merakis, something similar to the WRT54G hack:
I found some info about the GPIOs:
http://forum.openwrt.org/viewtopic.php?id=8852
but I was wondering if anyone had additional info about what each GPIO is currentlyused for, and which ones to not mess with.
Thanks!
you can install OpenWRT on the device as found at http://wiki.openwrt.org/OpenWrtDocs/Har … eraki/Mini
and you can download the GPIO program which you can compile it against the version of OpenWRT you installed. And I would imagine you could search for the GPIOs your self and port the sd card driver thats floating about, again im no developer but sounds possible to me 
and Ill be trying this myself when I get OpenWRT on my meraki device.
Cheers
Rip
I have compiled and install the meraki openwrt. I have also added the gpio_proc kernel mod. The GPIOs 0-7 are straight across JP2. The square keyed pad is GPIO0. GPIO3 is definitely used for the LED, the others seems to be free, although 5 may be used for reset (I will have to confirm that).
My plan is to write a small "bit-banging" SPI driver for the Meraki, ala: Linux/drivers/spi/spi_s3c24xx.c in the kernel (easy, I think).
Then add the development MMC-SPI driver: http://lkml.org/lkml/2007/1/28/110 which supposedly works with bitbanging SPI drivers already.
I will have to backport both to 2.6.16.
We shall see if this works...
I'm looking to create a general purpose bit-banging SPI interface myself, to communicate with an FPGA I/O extender. The actual bit-banging isn't that hard - look in the GPIO MMC drivers for example code.
What I would like to do is support multiple SPI devices with one interface. (since there are only a handful of GPIO available)
It would be nice if I could get both MMC storage AND a FPGA I/O extender on the same bus. Unfortunately, I'm not terribly familiar with kernel module development.
My end goal is to be able to create /dev/ttyS0x and /dev/gpio0x interfaces, where the underlying driver sends data to the FPGA via SPI.
gpio 5 is indeed used for reset, best not to play with it (except to reset the device), and 3 is of course the led. I believe all the others are usable (including the led, if you don't care about the normal function, I suppose), by virtue of not breaking anything from twiddling with them, and proper behavior observed for I/O using a multimeter
that new mmc-spi driver looks very interesting, definitely going to look at that
you should not have to backport to 2.6.16.16, openwrt uses 2.6.19.2 (or maybe 20 now) for the atheros port, and in any case I have tested 2.6.20 as bootable. had some problems with madwifi in 20 that might be fixed by now.
(Last edited by Kevin on 15 Mar 2007, 19:02)
Some other potentially good links. Seems like the mmc layer is independent of the spi implementation. Kudos!
http://www.vpx.nu/dokuwiki/doku.php?id= … figuration
http://blackfin.uclinux.org/gf/project/ … threv=2003
Seems like an easy MMC SPI driver for kernel 2.6
The discussion might have continued from here.