Last night I had troubles with Eclipse, when I put together those instructions (back in 2015) everything worked but things have changed on my system since then and neon doesn't like my java sdk anymore. I uninstalled/reinstalled java and switched to mars and it is happy now. This sort of crap is why I HATE JAVA, if a language can't be minimally compatible between the gobs of versions it has I don't even want to start to learn it! Anyway, if you have trouble try
Eclipse Mars. All this has nothing to do with OpenWrt or VoCore, it is Eclipse/Java !@#$%^&*(!!! Eclipse has some great features but I really wish it was based on a workable language instead of the steaming pile of shit that Java is (can you tell I don't care for Java?) Eclipse can also be frustrating and confusing to set up, many options look very similar to other options, make sure you follow the instructions exactly, I just did it and it does work. If things don't look like what I describe back up a few steps and make sure you did it just like the instructions. I wrote the instructions and I have to do that!
Once you get Eclipse working there are a couple more aggravations to deal with. You should really do this before you set up Eclipse but it doesn't matter much except you need to do it before Step 7 (Use Eclipse to connect to VoCore).
1. If you are using a VoCore2 withOUT a sdcard slot you will get an endless stream of
- Code: Select all
Sun Feb 5 12:40:36 2017 kern.err kernel: [ 34.810000] mmc0: error -22 whilst initialising SDIO card
Sun Feb 5 12:40:36 2017 kern.warn kernel: [ 34.840000] mtk-sd 10130000.sdhci: no support for card's volts
on the UART console, to kill this crap you need to hit enter and then
- Code: Select all
rmmod mtk-sd
This will come back when you reboot, to prevent this add the rmmod command to /etc/rc.local so it looks like this:
- Code: Select all
root@vocore2:/# cat /etc/rc.local
rmmod mtk-sd
uci set wireless.sta.disabled=0
uci commit
/etc/init.d/network restart
sleep 10
uci set wireless.sta.disabled=1
uci commit
# Put your custom commands here that should be executed once
# the system init finished. By default this file does nothing.
exit 0
root@vocore2:/#
Now you will still see the error messages but it will shut up once rc.local kicks in.
2. When you do
- Code: Select all
opkg update
you will get a scary message about a missing repo, it really doesn't hurt anything but to get rid of the message delete the line in /etc/opkg/distfeeds.conf that has "linkit" in it so it looks like this:
- Code: Select all
root@vocore2:/# cat /etc/opkg/distfeeds.conf
src/gz chaos_calmer_base http://downloads.openwrt.org/chaos_calmer/15.05.1/ramips/mt7628/packages/base
src/gz chaos_calmer_packages http://downloads.openwrt.org/chaos_calmer/15.05.1/ramips/mt7628/packages/packages
src/gz chaos_calmer_luci http://downloads.openwrt.org/chaos_calmer/15.05.1/ramips/mt7628/packages/luci
# src/gz chaos_calmer_routing http://downloads.openwrt.org/chaos_calmer/15.05.1/ramips/mt7628/packages/routing
# src/gz chaos_calmer_telephony http://downloads.openwrt.org/chaos_calmer/15.05.1/ramips/mt7628/packages/telephony
# src/gz chaos_calmer_management http://downloads.openwrt.org/chaos_calmer/15.05.1/ramips/mt7628/packages/management
root@vocore2:/#
I started the wiki update after my VoCore2 Ultimate shipped and wanted to be sure my changes matched the production units so I stopped. I really need to get the wiki fixed up but that is a different squirrel in a different tree from where I am now. The Ultimate actually showed up last week (>2 months transit, I have sent containers on a freighter and beat that time by alot!) so I will get back to it soon.
If you want to sign up and work on the wiki I'll be more than willing to help if you hit trouble.