VoCore Forum

Most of the tutorials on Vonger's blog and the opkg.conf on the VoCore are set up to use the latest OpenWrt development trunk. While this will give you the latest and greatest, there are many issues to deal with when working with a platform based on the OpenWrt development trunk. There may be bugs introduced at any time, the kernel modules need to match the latest Snapshot upload kernel, etc, etc.

To alleviate at least some of these problems I have set up a source repository and a package repository.

You can clone the version of openwrt at the point of Vocore's addition with this:

Code: Select all

git clone -b VoCoreOrig https://github.com/noblepepper/openwrt

If you build this you will get an image which is very close to what is in the vocore.v1.0.bin
file in Vonger's upload area along with a lot of packages that will work with it.

If you don't want to build the whole enchilada I set up an area with what you get after building:
After you flash this image
http://noblepepper.com/wp/wp-content/vocore-1.0/openwrt-ramips-rt305x-vocore-squashfs-sysupgrade.bin
(make sure you check the md5sum which should be 95eaa2bdf6a5adeb8f74db50c003e1fa) you can use packages from my package repository without issues about kernel version. Do this by changing /etc/opkg.conf on the vocore to:

Code: Select all

#src/gz chaos_calmer http://downloads.openwrt.org/snapshots/trunk/ramips/packages/packages
src/gz chaos_calmer http://noblepepper.com/wp/wp-content/vocore-1.0/packages
dest root /
dest ram /tmp
lists_dir ext /var/opkg-lists
option overlay_root /overlay

If you want to switch back to the development trunk just uncomment the first line and comment the second line after you flash the latest image at https://downloads.openwrt.org/snapshots/trunk/ramips/openwrt-ramips-rt305x-vocore-squashfs-sysupgrade.bin.

What a nice idea! I've got some problems with additional module packages, so I think that this repository must solve my past problems.

I've got a question. Do your binary image have the last patches to support microSD?

Thanks a lot for your work!

No, this build is stock OpenWrt on August 1, 2014, specifically at the commit with this comment

ramips: Add support for VoCore
This is based and tested on VoCore Alpha, but other stuff like status/eth LEDs are present on the final board revision + VoDock.
All GPIOs are exported, except spi/i2c.

It has kernel version 3.10 and the same packages as vocore.v1.0.bin. Some of the packages are slightly different versions, for example the original image has hostapd-common - 2014-06-03-1 where mine has hostapd-common - 2014-07-29-1.

My intent is to have a base image very close to vocore.v1.0 and a repository of packages that don't require --force-depends to install them. I have since noticed I left kmod-usb-uhci out so there will be an update soon.

I tried the image with the microSD package and had some watchdog issues. I saw these issues with a home built image without the microSD patch as well. I think it is related to some change since VoCore 1.0, maybe the change to kernel 3.14.

Do you have the .config-file from the original image?

No, I wish I did, I simulated it the best I could by comparing the output of

Code: Select all

opkg list-installed

after flashing vocore.v1.0.bin to the output after flashing the image generated from my build.

The .config I ended up with is at https://github.com/noblepepper/openwrt/blob/VoCoreOrig/.config

There is an updated repository at http://noblepepper.com/wp/wp-content/vocore-1.0a/packages/ with many more packages, the matching base image is at http://noblepepper.com/wp/wp-content/vocore-1.0a/openwrt-ramips-rt305x-vocore-squashfs-sysupgrade.bin.

I have usb storage and extroot working with this, I'll be posting a link to some set up instructions soon.

I just ordered my VoCore and this repo idea is really great! Looking forward to testing it out.

any hope in getting vpn support?

I have been working on an updated repository with all the packages that compile easily.

Basically I start with the openwrt tree at the point VoCore was added, enable "Select all packages by default" then disable anything that causes the build to fail. I have had random watch dog reboots with some later releases (like the point where Vonger compiled the spi-mmc patch). I haven't had time to isolate this issue much more than this.

If you give me a specific package you need I will give it at least a little more effort (this is just a spare time project!). While I have gotten fairly good at working with the buildroot I am far from an expert on everything you can do with OpenWrt.

The attached file has a list of what I expect to be in my next repository

i will be thankful for
opkg install nfs-kernel-server