Did you remember to replace the defconfig file after modifying menuconfig? You always need to replace this file for the one created by menuconfig, otherwise the changes will not take place. To learn more about menuconfig and how it works, I’d suggest you to read Yocto’s Mega Manual (http://www.yoctoproject.org/docs/1.7.2/mega-manual/mega-manual.html).
Also, did you try the suggestion made by @JimR in https://communities.intel.com/message/338169#338169?
I went through the yocto manual
So this time I tried with a fresh copy of whole sdk/bsp (newly downloaded to enusre previous changes are not messing up)
I download the patch from pmu: stop powering up the pci device without driver · 01org/edison-linux@149de7a · GitHub
Moved it into
edison-src/meta-intel-edison/meta-intel-edison-bsp/recipes-kernel/linux/files and updated the linux-yocto_3.10.bbappend by adding the line
SRC_URI += "file://power.patch"
bitbake virtual/kernel -c menuconfig
cp tmp/work/edison-poky-linux/linux-yocto/3.10.17-r0/linux-edison-standard-build/.config ../../../meta-intel-edison/meta-intel-edison-bsp/recipes-kernel/linux/files/defconfig
After booting with the new image file the issue still seems to be there, ie; when I try echo -n "mem" > /sys/power/state for the second time Edison is not going to the sleep mode.
(Note: I verified that the file gets patched properly after compilation)
Am I missing something, please help me with your inputs ?
In this last build, which image were you using? Did you build it using the 2.1 BSP? Also, how did you verify that file was correctly patched? Have you tried to manually modify the file (instead of using the patch)? Is there any difference?
- which image were you using?
- I'm using the edison-sec-ww25.5-15.tgz downloaded from Intel site and It downloaded yocto project with linux kernel 3.10.17-r0
- Did you build it using the 2.1 BSP?
- I not sure about the version number of BSP, anyway I downloaded the latest tar/zip file from Edison forum
- Also, how did you verify that file was correctly patched?
- Yes I checked the file after compilation whether the chnages in the patch is reflected in the actual files, and the actual files got patched.
- Have you tried to manually modify the file (instead of using the patch)? Is there any difference?
- Earlier when I tried to edit file manually the changes were getting roll-backed after doing the bitbake edison-image, that's why I sticked with the patching method.
So what can cause the issue ? Is it possible to reproduce the same at your end, since our project is running out of date..
Also can you please suggest some place in the kernel file where I can put a printk() and ensure that is working.
1 of 1 people found this helpful
The link Flashing Edison does not work helped me solving issue.
Intel should consider seriously on changing the script, like, it should report error without superuser privilege (as of now it reports success even though its not flashed).
1 of 1 people found this helpful
I just had to run the script in super user privilege ie; sudo ./flashall.sh,
Please update this script so that others wont repeat the mistake again , I think this can be added at the starting of script so that it reports error at the starting itself.
if [[ $EUID -ne 0 ]]; then
echo "This script must be run as root"