We bought the Intel Edison Arduino breakout board. First, we flashed the Yocto image on the board and everything seemed to work fine, until we tried to use opencv. we realized that some of the kernel modules fail to install even when we try to reboot the board. in addition, we noticed that the board does not appear as a drive anymore. we were trying to re-flash the image on the board but we couldn't as the drive does not show up (we are using a Mac).
when we tried to install modules needed for opencv, this is what we got:
npm ERR! Linux 3.10.17-poky-edison+
npm ERR! argv "node" "/usr/bin/npm" "install"
npm ERR! node v0.12.7
npm ERR! npm v2.11.3
npm ERR! code ELIFECYCLE
npm ERR! email@example.com install: `node-pre-gyp install --fallback-to-build`
npm ERR! Exit status 1
npm ERR! Failed at the firstname.lastname@example.org install script 'node-pre-gyp install --fallback-to-build'.
npm ERR! This is most likely a problem with the opencv package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node-pre-gyp install --fallback-to-build
npm ERR! You can get their info via:
npm ERR! npm owner ls opencv
we tried to reboot the board the error we got was:
Failed to start Load Kernel Modules. (during rebooting process)
We found this solution on the internet and we tried to follow it but the end result we the following:
here's the link for the solution we found -> No Edison Drive After Failed Flash
the result we got -->
terminal 1 (edison)
U-Boot 2014.04 (Jun 19 2015 - 12:05:55)
DRAM: 980.6 MiB
MMC: tangier_sdhci: 0
Hit any key to stop autoboot: 0
boot > <INTERRUPT>
boot > <INTERRUPT>
boot > c<INTERRUPT>
boot > run do_flash
Saving Environment to MMC...
Writing to MMC(0)... done
GADGET DRIVER: usb_dnl_dfu
terminal window 2 (host machine)
email@example.com. ~: ./flashall.sh
./flashall.sh: line 8: brew: command not found
./flashall.sh: line 16: greadlink: command not found
usage: dirname path
./flashall.sh: line 127: -o: command not found
Usage: flashall.sh [-h][--help][--recovery]
Update all software and restore board to its initial state.
-h,--help display this help and exit.
-v verbose output
--recovery recover the board to DFU mode using a dedicated tool,
available only on linux and window hosts.
Note: We are using Mac OSX.
Any Help is very much appreciated.