This stuff, is working really well, I managed to have around 150Ko/s (reading) which is far enough for my needs. Jan 1 00:00:49 OpenWrt user.warn kernel: mmc : Card was Found Jan 1 00:00:49 OpenWrt user.warn kernel: mmc : adding disk Jan 1 00:00:49 OpenWrt user.warn kernel: mmc : The inserted card has a capacity of 253231104 Bytes Jan 1 00:00:49 OpenWrt user.warn kernel: mmc : Card Initialised Jan 1 00:00:49 OpenWrt user.warn kernel: mmc : card in op mode
Wrt54g v4 manual driver#
Jan 1 00:00:49 OpenWrt user.warn kernel: mmc : MMC Driver for Fonera Version 2.5 (050507) - '2B|!2B' 1 00:00:49 OpenWrt user.warn kernel: mmc : Card Found Now, let’s try: insert a SD Card, and reboot, you should see something like this in your log.
Wrt54g v4 manual install#
Simply ipkg install the file and it should be ok. Next we need to install the kernel module on OpenWRT. So I decided to remove the capacitor on the SPI bus. In my first tests, I discovered the SD card is detected, so I checked the signals.
Wrt54g v4 manual serial#
You can solder the VCC, and Gnd on the serial pins. The first step, is to locate the SW pins (near the antenna). I run into one issue so I decided to describe the process here. I read on several websites, that some people managed to wire a SD Card (or a MMC) to a Fonera access point. This is a picture of the GPIO 3+5 for WRT54G v2.2 taken from WRT54G v3 and v3.1 GPIO 4 is located near the RA13 Text label (near to the Power LED) GPIO 3 can be found on Pin 3 of RP4 (near the BCM switch IC), just left of it you can find GPIO 5 next to the RA10 Text label. Using the mmc.o downloadable at the end of the thread the MMC is detected and working, the GPIO test is also working after loading this module. According to the reason is an incomplete initialization of the GPIOs. On a WRT54G Version 2 the tests on GPIO4 failed. I seriously recommend that you do this to verify which pins you are working on prior to doing any soldering. I then used my multimeter to detect the pin toggling between 0V and 3.3V every second. While true do gpio enable 5 sleep 1 gpio disable 5 sleep 1 done I toggled the pins with the following single line in the shell (example for GPIO 5): Can definitely confirm this swapped CLK/DO for my WRT54GS V1.0, so it's likely that the V1.1 statement before is correct, too) I soldered to the right-hand side of RP3 as shown in the picture with GPIO5 (DI) at the bottom, GPIO4 (DO) next up and GPIO3 (CLK) up from that.Ī good way to test the pin allocations is with the gpio utility and a script to toggle the GPIO pin periodically, then search for the pin with a digital multimeter or oscilloscope probe. The CLK and DO, which are GPIO3 and GPIO4, were swapped compared to the picture.įurther unverified evidence supports that the wrt54gs v1.1 hardware also has gpio 3 and 4 switched. The picture above was not correct for my V2 WRT54G. Important note for v2 hardware and some WRT54GS: It is worth double-checking the GPIO pin allocations on RP3. The mount-option -tmsdos has to be omitted. Using OpenWRT RC5 no msdos kernel module is needed. rwxr-xr-x 1 root root 16777216 temp3.binįilesystem 1k-blocks Used Available Use% Mounted on rwxr-xr-x 1 root root 0 Jan 1 00:07 bossepr0.pic Using /lib/modules/2.4.20/msdos.o mount -t msdos /dev/mmc/disc0/part1 ls -al /mnt Using /lib/modules/2.4.20/fat.o insmod msdos Using /lib/modules/2.4.20/mmc.o dmesg | tail -7 Lrwxrwxrwx 1 root root 28 Jan 1 00:01 wl.o -> /rom/lib/modules/2.4.20/wl.o insmod mmc Check with dmesg that everything went OK, and hopefully you should now have some new devices in /dev/mmc/… Here is a little snippet of a “conversation” with the ls -al /lib/modules/2.4.20/ Make sure a card is placed in the reader and then load the module. But you may just as well install the freifunk-sdcard and freifunk-sdinit mmc module packages which work fine on my whiterussian RC5. When that is done just type make (ignore the warnings - they are OK). You will need to modify the Makefile to point to where your OpenWRT linux kernel headers are and also the mipsel compiler location. These are some things you may want to include in your. Partition support must be built into the kernel whereas VFAT can be built both as a module or into the kernel. This section is obsolete, see driver section for driver installation.įirst of all we suggest that you configure a kernel with support for MSDOS partitions and VFAT.