I wish there was some place or places where common issues and tips and the like were easy to find. I have used several different forums over the years and there are many different ways that the many different forums have done it. Some of the things I personally would benefit people include:
How to post questions: Questions should include enough details to reproduce the issue. Things like: Which Edison module do you have. What version firmware and IDE are you using? If you are asking about how to hook up to something, try to specify what hardware you are trying to attach, maybe include a link to it... If problem with code, try to include enough code source, such that someone can reproduce it. Also when showing code, try to show in code tags (In advanced editor you can do this by clicking on the >> ) Finally found that a day or two ago...
Reminder for when you are rusty at this: When you are on a Linux machine such as Ubuntu 14.04 and you wish to flash the Edison, remember to use the sudo command! That is if you are using the ./flashall.sh command or make flash remember sudo!
How to do some of the common things many of us do when we setup an Edison. Example flow for me:
1) Update the Edison to latest firmware - Note: the current reboot ota does not clear the contents of the PC Edison drive nor root directory on Edison. If you wish to clear everything use the flashall method
2) run the Configure_edison --setup
Go through the steps and setup name and Wifi.
a) My network is setup with the IP addresses in the range: 192.168.2.xxx which conflicts with some usb something so I then:
and change the two lines 192.168.2.15 to something like: 192.168.99.15
I then typically reboot then and setup my Wifi PuTTY for that machine...
EDIT: With new beta
Edit the file: /etc/systemd/network/usb0.network
to : Address=192.168.99.15/24
3) The boot segment is not setup to use all of the space that was allocated to it, which can cause issues when you try to update to a larger firmware set... Instructions on how to fix this is up at: http://alextgalileo.altervista.org/blog/install-kernel-from-repo-onto-edison-official-image/ http://alextgalileo.altervista.org/blog/install-kernel-from-repo-onto-edison-official-image/
Quick script to try here:
cp -rp /boot/* /home/root/boot-backup/
ls -alF /home/root/boot-backup/
mkfs.vfat -v -nboot -F16 /dev/mmcblk0p7
df -h /boot
cp -rp /home/root/boot-backup/* /boot
ls -alF /boot
rm -r /home/root/boot-backup
4) I configure to use get the recent copies of MRAA
opkg install libmraa0
4a) On Edison to keep the MRAA libraries up to date to use Eclipse
. Right now you can grab the latest tarball from
http://iotdk.intel.com/sdk/mraa-update/ http://iotdk.intel.com/sdk/mraa-update/, and http://iotdk.intel.com/sdk/upm-update/ http://iotdk.intel.com/sdk/upm-update/ respectively and extract it in the IDE folder.
5) There are lots of other packages now available to download fro AlexT, to configure:
set the contents of: /etc/opkg/base-feeds.conf
Then do: opkg update
Edit: To make it easier, script to do it:
And then do opkg install xxx
6) You can upgrade many of the packages by first seeing which ones are upgradeable:
You can then do an upgrade: opkg uprade xxx
Note: if you don't specify a package or packages, it will upgrade all that are upgradeable. However you can run into issues that the root directory gets filled, so see step 6)
7) Some of my stuff uses sound libraries and the like, to compile I need some additional things installed:
opkg install espeak
Nicely put KurtE.
Personally, I use the bookmarking system provided to keep track of interesting posts I run across and are relating to the segment I am working on, and I still find myself digging back through all the forum posts to find what I thought I read where as I progress to next tasks.
If edison was good-to-go out of the box for everyone, there would be no problems - 1 page instructions. But in that no one should try to be everything to all, there are times when issues arrive.
It is not for when there is no issues that you fill a simple document with too many if this and if that -- but all the if this and if that, why was this, why was that, that is definitely needed when issues do arise. Personally, I started with a bad mini breakout with no OTA drive functionality, had to get a second mini breakout to change the modules over to when I need to flash. Then configure_edison does not connect to wifi when wep_keys contain none ascii values (configure_edison --wifi only allows for string valued password, and doesn't accept hex). And but of course, half+ of the posts on the forum are people experiencing problems that they'd otherwise be off elsewhere and Making.
So for my two cents (or nickels now in Canada as our penny is gone), a task might have a quick-guide for the 90% that go through without any issues, but it would be good for that to also include an updating troubleshooting section that links to the deeper why's and how's of what that quick-guide was suppose to accomplish. What happens when there is no OTA drive access? etc.
Another suggestion would be some sort of acknowledgement section where known issues can be confirmed, looked up and the fix located so that we know that this issue is actively being looked into, and a status/estimate of progress for the user's issue.
I also use the bookmarks, for my own stuff, which is great.
I also know that my first posting above actually talked about several different things (i.e. - I don't think it should be a sticky...), but I was trying to point and you brought up several other examples where there are common issues and the like that it would be great if others could easily find the answer. Like how to update MRAA. Or I use a WEP system how do I enter the hex keys...
Also not sure what the best way to do this. For many of these a Wiki might be great. I also like the idea of some area that describes issues and maybe gives an indication if it is being looked into (like the issues area of a github project)
Again this is not unique to here. I don't know how many times up on the Lynxmotion forums we had questions about my PS2 controller does not work. But at least there was a Sticky post and a guide document that asked the user to try the following things, that we could simply point the user to.
Or how many times up on the Teensy forums (PJRC) you will see something like: My program does not work or This library does not work... And no other details. Which is why now the forum has the text: Forum Rule: Always post complete source code & details to reproduce any issue!
KurtE, I agree.
Didn't mean for it to sound like looking for a "Post-It Note" system, rather supporting the need to locate issues that we know we have already read, and bookmarks doesn't quite do it.
> I also like the idea of some area that describes issues and maybe gives an indication if it is being looked into
Not making it personal here other than to show I agree, that mini breakout board without OTA drive capability has no update on what if anything occurred. In that case it was referred to an email support and dropped without a status or way to check a status. We as users should be able to see if the causing issue is in a queue to be looked at, completed, or what not.
> Sticky post and a guide document
At the point of resounding what you are saying - related Troubleshooting links if the solution did not work. Some type of next step.
As for more complete details to try to reproduce, I agree. Sometimes 10 questions/posts are made just to find out info that could have been given in the very beginning.