Intel® Distribution of OpenVINO™ Toolkit
Community assistance about the Intel® Distribution of OpenVINO™ toolkit, OpenCV, and all aspects of computer vision-related on Intel® platforms.
6411 Discussions

Steps for installtion for Raspberry Pi 3 new sdk

idata
Employee
6,813 Views

Can any one please guide me in installing/setting up movidius for raspberry pi 3 jessie? Existing tutorials are based on earlier sdk.

 

Thank you
0 Kudos
69 Replies
idata
Employee
2,094 Views

@pkrush : Thanks for the suggestions. Here is what I have tried since my last post:

 

     

  1. Downloaded a fresh copy of Raspbian Stretch and burned to a brand new SD card.
  2.  

  3. Went through the entire installation steps once again from https://developer.movidius.com/start
  4.  

  5. Rebooted the R-Pi after that to be sure.
  6.  

 

Alas, after all that work, I ended up exactly where I started. The basic app (just connect and disconnect) works fine, but the GooGleNet Caffe model fails to run with a TIMEOUT error. I have two NCS sticks that are sitting useless now.

 

@AshwinVijayakumar can you help at all? If not, how do I go about getting support for the two NCS sticks I purchased that are unusable for me now? All I am asking is that the stock Caffe model from your own examples should work. I don't think I am asking for too much here.

 

Thanks,

 

-Kal.
0 Kudos
idata
Employee
2,093 Views

@AshwinVijayakumar on your advice I tried a buck converter and it seems to be working a treat. I was struggling with the NCS and my other pi peripherals(an LCD screen) causing low power throttling.. this seems to have completely fixed it. I used this device: https://www.amazon.com/gp/product/B06XRDV49T/ref=oh_aui_detailpage_o02_s00?ie=UTF8&psc=1

 

Here is a video of my car running.. https://www.youtube.com/watch?v=7nTZQC-Ayps Car driving my neural network on the pi, the NCS is doing object detection (not really affecting the car driving yet)

 

In regards to using the built in ECS for power. My ESC returns 6v on the BEC to drive servos. Almost just right, but I worried that there wasn't enough difference between the BEC 6v and 5.2v needed for the pi for a buck device to work well. All the specs I read seems to require at least 1.5v difference. I would like to try it anyway as more regulation is probably a good thing (filtering out high freqency noise etc) Im no electronics expert for sure.. maybe I should just use a resistor to drop that .5v from the BEC? suggestions? Oh, and to be clear, I'm using the Micro USB port for power IN on the pi, as I assumed there was probably some useful filtering\buffering\regulating or whatever going on on that input. Was that a reasonable thought?

0 Kudos
idata
Employee
2,094 Views

@kalkrishnan I wonder if your python version is the issue? I see in your text above that "/usr/local/lib/python2.7/dist-packages/mvnc/mvncapi.py" is where the mvnc stuff is.. ???

0 Kudos
idata
Employee
2,094 Views

@wheatgrinder thanks for that suggestion. After the fresh re-installation, here is the output. I made sure I was using Python 3 this time.

 

pi@raspberrypi:~/movidius/ncsdk/examples/caffe/GoogLeNet $ python3 run.py

 

Device 0 Address: 1.3 - VID/PID 03e7:2150

 

Starting wait for connect with 2000ms timeout

 

Found Address: 1.3 - VID/PID 03e7:2150

 

Found EP 0x81 : max packet size is 512 bytes

 

Found EP 0x01 : max packet size is 512 bytes

 

Found and opened device

 

Performing bulk write of 865212 bytes…

 

Successfully sent 865212 bytes of data in 146.219385 ms (5.643099 MB/s)

 

Boot successful, device address 1.3

 

Found Address: 1.3 - VID/PID 03e7:f63b

 

done

 

Booted 1.3 -> VSC

 

Traceback (most recent call last):

 

File "run.py", line 87, in

 

output, userobj = graph.GetResult()

 

File "/usr/local/lib/python3.5/dist-packages/mvnc/mvncapi.py", line 262, in GetResult

 

raise Exception(Status(status))

 

Exception: mvncStatus.TIMEOUT

 

pi@raspberrypi:~/movidius/ncsdk/examples/caffe/GoogLeNet $
0 Kudos
idata
Employee
2,094 Views

@kalkrishnan

 

It would be nice if Movidius provided a SD Card image. I plan to put one together:

 

https://github.com/GemHunt/movidius-on-rpi/blob/master/build.md

 

It's frustrating because I build up a number bits of advice, but I don't know exactly what advice fixes what problem.

 

Other hints:

 

With the Movidius repo installs and examples when something did not work I tried again using sudo.

 

Check out Adrian Rosebrock's says about swap space in a TensorFlow install: https://www.pyimagesearch.com/2017/12/18/keras-deep-learning-raspberry-pi. I have seen out of memory issues with Caffe, but I have forgot where…

0 Kudos
idata
Employee
2,094 Views

@pkrush - appreciate your efforts in putting together an SD card image. However, I think Movidius/Intel should be able to conduct QA such that if they go through the steps I did (Download & burn fresh Raspbian Stretch, then git clone and run their supplied make install), it should reliably work every time. Have they even tried that? If certain commands require sudo, the script should be able to take care of this, and prompt the user for the password. This is not rocket science. I am very very unhappy with the way that they leave their customers flapping in the wind.

 

Anyone considering buying this product for use on an R-Pi should really think twice about it, given my experience. I bought two, and they are totally useless pieces of junk at this time. I note that @AshwinVijayakumar said he could help me debug this situation, but has been totally silent since then, with no concrete help. I have been trying stuff on my own, to no avail.

 

-Kal.

0 Kudos
idata
Employee
2,094 Views

@kalkrishnan, as mentioned before - "except for profiler and compiler support for TF, NC SDK is validated to run well on RPI 3 (Stretch OS)". This is based on the QA we do prior to every release, which is documented here - https://github.com/movidius/ncsdk/releases.

 

There are many documentation resources for 'NCSDK installation on RPI', many of which are discussed in this thread itself. I have outlined a few for your reference:

 

     

  1. https://github.com/movidius/ncsdk/releases --> Refer errata 1, 2, 5 & 7 for V1.11.00
  2.  

  3. https://developer.movidius.com/start --> NCSDK installation steps that applies to all supported platforms
  4.  

  5. https://ncsforum.movidius.com/discussion/comment/1034/#Comment_1034 --> Installing NCSDK API only on different platforms (architectures & OS). Refers to https://movidius.github.io/blog/
  6.  

 

It could be possible that the issue you are facing is specific to your setup, so please help me better understand your setup by performing the steps I previously asked - https://ncsforum.movidius.com/discussion/comment/1320/#Comment_1320.

 

     

  1. Are you able to run networks other than GoogLeNet? ex. AlexNet, SqueezeNet, Age/Gender, etc?
  2.  

  3. What happens when you transfer a pre-compiled graph file (generated on a laptop/desktop) and then run the examples?
  4.  

 

Please also provide any additional information that might be relevant. ex. I see that you are running on a fresh OS install, but can you confirm if there are any other installations that has python dependencies? ex. Anaconda, OpenCV, ROS, etc.

0 Kudos
idata
Employee
2,094 Views

@wheatgrinder, I am glad the buck regulator solution worked out for you. The 1.5v difference you mentioned is the dropout voltage property of any voltage regulator. If you are OK using both the ESC and the buck regulator, I'd recommend using a power distributor to supply both the ESC and the buck from the same battery. If you prefer to further optimize your electronics, then pick up an ESC that has a built in 5V BEC like this one - https://hobbyking.com/en_us/hobby-king-30a-esc-3a-ubec.html.

 

NOTE: Most ESCs with built in BEC continue to supply the regulated voltage (5V) even after shutting down motor supply, but I am not sure about the one I referenced above, so please do some research before purchasing.

 

 

May I suggest we move your discussion to a dedicated post? Your posts have novel content which might help other forum members looking to work on similar projects. If you agree, please feel free to start a new thread and tag me.

 

0 Kudos
idata
Employee
2,094 Views

Hi @AshwinVijayakumar - You had asked me to run "make profile" in 3 directories - AlexNet, GoogleNet and inception_v3.

 

For AlexNet & GoogeNet, I get the following:

 

`pi@raspberrypi:~/movidius/ncsdk/examples/caffe/AlexNet $ make profile making prereqs (cd ../../data/ilsvrc12; make) make[1]: Entering directory '/home/pi/movidius/ncsdk/examples/data/ilsvrc12' make[1]: Leaving directory '/home/pi/movidius/ncsdk/examples/data/ilsvrc12' chmod +x run.py making prototxt Prototxt file already exists making profile mvNCProfile deploy.prototxt -s 12 mvNCProfile v02.00, Copyright @ Movidius Ltd 2016 ****** WARNING: using empty weights ****** /usr/local/bin/ncsdk/Controllers/FileIO.py:52: UserWarning: You are using a large type. Consider reducing your data sizes for best performance "Consider reducing your data sizes for best performance\033[0m") USB: Transferring Data... [Error 25] Myriad Error: "mvncStatus.TIMEOUT".`

 

(Not including the GooGleNet output, since it is exactly the same).

 

On inception_v3, as expected, it just fails with "ImportError: No module named 'tensorflow'", since tensorflow is not installed on the R-Pi.

 

Interestingly, instead of "make profile" in AlexNet, if I just run "python3 run.py", I do get some results:

 

`pi@raspberrypi:~/movidius/ncsdk/examples/caffe/AlexNet $ python3 run.py Device 0 Address: 1.5 - VID/PID 03e7:2150 Starting wait for connect with 2000ms timeout Found Address: 1.5 - VID/PID 03e7:2150 Found EP 0x81 : max packet size is 512 bytes Found EP 0x01 : max packet size is 512 bytes Found and opened device Performing bulk write of 865212 bytes... Successfully sent 865212 bytes of data in 108.914949 ms (7.575916 MB/s) Boot successful, device address 1.5 Found Address: 1.5 - VID/PID 03e7:f63b done Booted 1.5 -> VSC ------- predictions -------- prediction 0 (probability 0.100040435791%) is n15075141 toilet tissue, toilet paper, bathroom tissue label index is: 999 prediction 1 (probability 0.100040435791%) is n02319095 sea urchin label index is: 328 prediction 2 (probability 0.100040435791%) is n02395406 hog, pig, grunter, squealer, Sus scrofa label index is: 341 prediction 3 (probability 0.100040435791%) is n02391049 zebra label index is: 340 prediction 4 (probability 0.100040435791%) is n02389026 sorrel label index is: 339`

 

So, finally, some signs of life, hooray!

 

As for your other questions, I believe I answered that already. All I did was did a fresh OS install, then git clone the ncsdk project and run make install. Nothing else is installed that is not part of the ncsdk installation, whatsoever.

 

Thanks,

 

-Kal.
0 Kudos
idata
Employee
2,094 Views

@AshwinVijayakumar - I know I am very frustrated, but look at it from my point of view. As already mentioned -

 

     

  1. I am running a plain vanilla (just downloaded) Rasbian Stretch OS.
  2.  

  3. I have NOT installed any other packages.
  4.  

  5. I scrupulously followed the Getting Started steps on your website.
  6.  

 

At this point, I have a reasonable right to expect that the supplied examples will work, except as documented (e.g., no TensorFlow, which I understand, and am fine with). Do you have any disagreement with what I am saying?

0 Kudos
idata
Employee
2,094 Views

@kalkrishnan, thanks for running the test. python3 run.py didn't actually work, notice how the predictions are all over the place? You should be seeing this instead:

 

ashwin@ncp-demo-monster:~/workspace/ncappzoo/caffe/AlexNet$ python3 run.py Device 0 Address: 1 - VID/PID 03e7:2150 Starting wait for connect with 2000ms timeout Found Address: 1 - VID/PID 03e7:2150 Found EP 0x81 : max packet size is 512 bytes Found EP 0x01 : max packet size is 512 bytes Found and opened device Performing bulk write of 865212 bytes... Successfully sent 865212 bytes of data in 75.208594 ms (10.971226 MB/s) Boot successful, device address 1 Found Address: 1 - VID/PID 03e7:f63b done Booted 1 -> VSC ------- predictions -------- prediction 0 (probability 94.970703125%) is n03272010 electric guitar label index is: 546 prediction 1 (probability 4.76684570312%) is n02676566 acoustic guitar label index is: 402 prediction 2 (probability 0.102138519287%) is n02787622 banjo label index is: 420 prediction 3 (probability 0.0409126281738%) is n04517823 vacuum, vacuum cleaner label index is: 882 prediction 4 (probability 0.0347137451172%) is n04141076 sax, saxophone label index is: 776

 

What's weird is that I don't see any exception being thrown by any of the APIs after mvnc.OpenDevice; I'd expect at least AllocateGraph or LoadTensor to throw an exception . Can you please double check the results from your laptop/desktop?

 

In the mean time, I'll try to figure out how to read the status of your NCS device so that we can manually pull the device status anytime between OpenDevice and GetResult.

0 Kudos
idata
Employee
2,094 Views

@AshwinVijayakumar I tried on Ubuntu on the desktop and got the same output as you have shown.

 

kal@kal-VirtualBox:~/movidius/ncsdk/examples/caffe/AlexNet$ python3 run.py

 

Device 0 Address: 2 - VID/PID 03e7:2150

 

Starting wait for connect with 2000ms timeout

 

Found Address: 2 - VID/PID 03e7:2150

 

Found EP 0x81 : max packet size is 512 bytes

 

Found EP 0x01 : max packet size is 512 bytes

 

Found and opened device

 

Performing bulk write of 865212 bytes…

 

Successfully sent 865212 bytes of data in 254.899465 ms (3.237082 MB/s)

 

Boot successful, device address 2

 

Device 0 Address: 1 - VID/PID 03e7:f63b

 

Found Address: 1 - VID/PID 03e7:f63b

 

done

 

Booted 1 -> VSC

 

------- predictions --------

 

prediction 0 (probability 94.970703125%) is n03272010 electric guitar label index is: 546

 

prediction 1 (probability 4.76684570312%) is n02676566 acoustic guitar label index is: 402

 

prediction 2 (probability 0.102138519287%) is n02787622 banjo label index is: 420

 

prediction 3 (probability 0.0409126281738%) is n04517823 vacuum, vacuum cleaner label index is: 882

 

prediction 4 (probability 0.0347137451172%) is n04141076 sax, saxophone label index is: 776
0 Kudos
idata
Employee
2,094 Views

Hmm…

 

Excerpt from https://ncsforum.movidius.com/discussion/comment/1389/#Comment_1389

 

pi@raspberrypi:~/movidius/ncsdk/examples/caffe/GoogLeNet $ python3 run.py ... File "/usr/local/lib/python3.5/dist-packages/mvnc/mvncapi.py", line 262, in GetResult raise Exception(Status(status)) Exception: mvncStatus.TIMEOUT

 

Excerpt from https://ncsforum.movidius.com/discussion/comment/1401/#Comment_1401

 

pi@raspberrypi:~/movidius/ncsdk/examples/caffe/AlexNet $ python3 run.py # No TIMEOUT exception

 

Not sure why the inconsistency between GoogLeNet and AlexNet. I would like to rule out any issues with the graph compilation on your RPi, so let's please try another experiment:

 

Copy ~/movidius/ncsdk/examples/caffe/GoogLeNet/graph and ~/movidius/ncsdk/examples/caffe/AlexNet/graph from your desktop to the respective location on your RPi and rerun python3 run.py on your RPi.

 

 

Make sure the NCSDK version on your RPi is the same as your laptop/desktop, else this step won't work.

 

0 Kudos
idata
Employee
2,094 Views

Hi @AshwinVijayakumar - Here are the results:

 

     

  1. No difference in outcome after copying over the graph files from the desktop to R-Pi. (Yes, they are the exact same version).
  2.  

  3. As for the discrepancy between googleNet and AlexNet - I tried it various ways and discovered that if I just run the "python3 run.py" in the AlexNet folder after a reboot, I get the same mvncStatus.TIMEOUT error. However, if I first run the "make profile" command (which fails), and then run the python3 run.py command, I get the wild result. Not sure what this means, but thought I would mention in case it triggered some ideas.
  4.  

 

-Kal.

0 Kudos
idata
Employee
2,094 Views

Oh, also tried SqueezeNet just for completeness - no joy. Same TIMEOUT error.

 

pi@raspberrypi:~/movidius/ncsdk/examples/caffe/SqueezeNet $ python3 run.py Device 0 Address: 1.3 - VID/PID 03e7:2150 Starting wait for connect with 2000ms timeout Found Address: 1.3 - VID/PID 03e7:2150 Found EP 0x81 : max packet size is 512 bytes Found EP 0x01 : max packet size is 512 bytes Found and opened device Performing bulk write of 865212 bytes... Successfully sent 865212 bytes of data in 108.951684 ms (7.573361 MB/s) Boot successful, device address 1.3 Found Address: 1.3 - VID/PID 03e7:f63b done Booted 1.3 -> VSC Traceback (most recent call last): File "run.py", line 87, in <module> output, userobj = graph.GetResult() File "/usr/local/lib/python3.5/dist-packages/mvnc/mvncapi.py", line 262, in GetResult raise Exception(Status(status)) Exception: mvncStatus.TIMEOUT
0 Kudos
idata
Employee
2,094 Views

@AshwinVijayakumar - One additional thought:

 

Do you have access to a Raspberry Pi 3? Can you repeat the experiment that I did, namely:

 

     

  1. Get a fresh copy of Stretch from https://downloads.raspberrypi.org/raspbian_latest (I downloaded the full version, not the Lite version)
  2.  

  3. Burn it to a SD Card, and boot the R-Pi from it.
  4.  

  5. Go through all the steps exactly as outlined in https://developer.movidius.com/start (Yes, it takes FOR EVER, you have to be patient like your customers ;))
  6.  

 

Do the Caffe examples work for you?

0 Kudos
idata
Employee
2,094 Views

@kalkrishnan, I have tried to reproduce this issue several times on my bench, but no luck.

 

The only other thing my team and I think about, is the power delivery from your USB port. I am guessing you are connecting the NCS, Keyboard and Mouse through a USB hub. Is this hub powered? If not, please try with a powered USB hub. If you are using BT keyboard/mouse and connecting NCS directly to RPi port (like I am doing), make sure your power supply to RPi is good (see @wheatgrinder's posts on this thread)

 

Below is the log from one of my runs.

 

     

  • Notice that I am running Stretch + v1.11.00.04 NCSDK
  •  

  • GoogLeNet and SqueezeNet work fine
  •  

  • AlexNet errors out during compilation due to insufficient RAM (more of a Caffe issue), but you can compile the graph on your laptop and move it to RPi for inference
  •  

 

pi@raspberrypi:~ $ uname -a Linux raspberrypi 4.9.59-v7+ #1047 SMP Sun Oct 29 12:19:23 GMT 2017 armv7l GNU/Linux pi@raspberrypi:~ $ cd workspace/ncsdk/ pi@raspberrypi:~/workspace/ncsdk $ git describe v1.11.00.04 pi@raspberrypi:~/workspace/ncsdk $ cd examples/caffe/GoogLeNet/ pi@raspberrypi:~/workspace/ncsdk/examples/caffe/GoogLeNet $ make run making prereqs ... making run ./run.py Device 0 Address: 1.5.4.4.3 - VID/PID 03e7:2150 Starting wait for connect with 2000ms timeout Found Address: 1.5.4.4.3 - VID/PID 03e7:2150 Found EP 0x81 : max packet size is 64 bytes Found EP 0x01 : max packet size is 64 bytes Found and opened device Performing bulk write of 865212 bytes... Successfully sent 865212 bytes of data in 774.342425 ms (1.065589 MB/s) Boot successful, device address 1.5.4.4.3 Found Address: 1.5.4.4.3 - VID/PID 03e7:f63b done Booted 1.5.4.4.3 -> VSC ------- predictions -------- prediction 0 (probability 0.99609) is b'n03272010 electric guitar' label index is: 546 prediction 1 (probability 0.0035095) is b'n02676566 acoustic guitar' label index is: 402 prediction 2 (probability 0.0) is b'n02396427 wild boar, boar, Sus scrofa' label index is: 342 prediction 3 (probability 0.0) is b'n02391049 zebra' label index is: 340 prediction 4 (probability 0.0) is b'n02389026 sorrel' label index is: 339 pi@raspberrypi:~/workspace/ncsdk/examples/caffe/GoogLeNet $ cd ../AlexNet/ pi@raspberrypi:~/workspace/ncsdk/examples/caffe/AlexNet $ make run making prereqs ... [Error 28] Caffe Error: MemoryError. Potential Cause: Available RAM not sufficient for Network to be loaded into Caffe making run ./run.py Device 0 Address: 1.5.4.4.3 - VID/PID 03e7:2150 Starting wait for connect with 2000ms timeout Found Address: 1.5.4.4.3 - VID/PID 03e7:2150 Found EP 0x81 : max packet size is 512 bytes Found EP 0x01 : max packet size is 512 bytes Found and opened device Performing bulk write of 865212 bytes... Successfully sent 865212 bytes of data in 134.378653 ms (6.140339 MB/s) Boot successful, device address 1.5.4.4.3 Found Address: 1.5.4.4.3 - VID/PID 03e7:f63b done Booted 1.5.4.4.3 -> VSC Traceback (most recent call last): File "./run.py", line 63, in <module> with open(network_blob, mode='rb') as f: FileNotFoundError: [Errno 2] No such file or directory: 'graph' Makefile:90: recipe for target 'run' failed make: *** [run] Error 1 pi@raspberrypi:~/workspace/ncsdk/examples/caffe/AlexNet $ cd ../SqueezeNet/ pi@raspberrypi:~/workspace/ncsdk/examples/caffe/SqueezeNet $ make run making prereqs ... making run ./run.py Found stale device, resetting Device 0 Address: 1.5.4.4.3 - VID/PID 03e7:2150 Starting wait for connect with 2000ms timeout Found Address: 1.5.4.4.3 - VID/PID 03e7:2150 Found EP 0x81 : max packet size is 512 bytes Found EP 0x01 : max packet size is 512 bytes Found and opened device Performing bulk write of 865212 bytes... Successfully sent 865212 bytes of data in 153.405999 ms (5.378737 MB/s) Boot successful, device address 1.5.4.4.3 Found Address: 1.5.4.4.3 - VID/PID 03e7:f63b done Booted 1.5.4.4.3 -> VSC ------- predictions -------- prediction 0 (probability 99.12109375%) is b'n03272010 electric guitar' label index is: 546 prediction 1 (probability 0.335884094238%) is b'n04517823 vacuum, vacuum cleaner' label index is: 882 prediction 2 (probability 0.151348114014%) is b'n02676566 acoustic guitar' label index is: 402 prediction 3 (probability 0.0977516174316%) is b'n03109150 corkscrew, bottle screw' label index is: 512 prediction 4 (probability 0.0661373138428%) is b'n03532672 hook, claw' label index is: 600
0 Kudos
idata
Employee
2,094 Views

THAT WAS IT!

 

Since the NCS blocks the other USB ports, I had used a USB extension cord to connect it. Apparently that is a bad idea (power drop in the cord?). I took that cord out, and plugged the NCS stick directly into the back of the R-Pi, and it started to work! Whew, wish I had thought of that first, would have saved us a lot of time and headache. Here is the output now:

 

pi@raspberrypi:~/movidius/ncsdk/examples/caffe/GoogLeNet $ python3 run.py Device 0 Address: 1.4 - VID/PID 03e7:2150 Starting wait for connect with 2000ms timeout Found Address: 1.4 - VID/PID 03e7:2150 Found EP 0x81 : max packet size is 512 bytes Found EP 0x01 : max packet size is 512 bytes Found and opened device Performing bulk write of 865212 bytes... Successfully sent 865212 bytes of data in 108.902934 ms (7.576751 MB/s) Boot successful, device address 1.4 Found Address: 1.4 - VID/PID 03e7:f63b done Booted 1.4 -> VSC ------- predictions -------- prediction 0 (probability 0.99609) is n03272010 electric guitar label index is: 546 prediction 1 (probability 0.0035095) is n02676566 acoustic guitar label index is: 402 prediction 2 (probability 0.0) is n02396427 wild boar, boar, Sus scrofa label index is: 342 prediction 3 (probability 0.0) is n02391049 zebra label index is: 340 prediction 4 (probability 0.0) is n02389026 sorrel label index is: 339 pi@raspberrypi:~/movidius/ncsdk/examples/caffe/GoogLeNet $ cd ../AlexNet/ pi@raspberrypi:~/movidius/ncsdk/examples/caffe/AlexNet $ python3 run.py Device 0 Address: 1.4 - VID/PID 03e7:2150 Starting wait for connect with 2000ms timeout Found Address: 1.4 - VID/PID 03e7:2150 Found EP 0x81 : max packet size is 512 bytes Found EP 0x01 : max packet size is 512 bytes Found and opened device Performing bulk write of 865212 bytes... Successfully sent 865212 bytes of data in 108.838054 ms (7.581268 MB/s) Boot successful, device address 1.4 Found Address: 1.4 - VID/PID 03e7:f63b done Booted 1.4 -> VSC ------- predictions -------- prediction 0 (probability 94.970703125%) is n03272010 electric guitar label index is: 546 prediction 1 (probability 4.76684570312%) is n02676566 acoustic guitar label index is: 402 prediction 2 (probability 0.102138519287%) is n02787622 banjo label index is: 420 prediction 3 (probability 0.0409126281738%) is n04517823 vacuum, vacuum cleaner label index is: 882 prediction 4 (probability 0.0347137451172%) is n04141076 sax, saxophone label index is: 776 pi@raspberrypi:~/movidius/ncsdk/examples/caffe/AlexNet $ cd ../SqueezeNet/ pi@raspberrypi:~/movidius/ncsdk/examples/caffe/SqueezeNet $ python3 run.py Device 0 Address: 1.4 - VID/PID 03e7:2150 Starting wait for connect with 2000ms timeout Found Address: 1.4 - VID/PID 03e7:2150 Found EP 0x81 : max packet size is 512 bytes Found EP 0x01 : max packet size is 512 bytes Found and opened device Performing bulk write of 865212 bytes... Successfully sent 865212 bytes of data in 108.780791 ms (7.585259 MB/s) Boot successful, device address 1.4 Found Address: 1.4 - VID/PID 03e7:f63b done Booted 1.4 -> VSC ------- predictions -------- prediction 0 (probability 99.12109375%) is n03272010 electric guitar label index is: 546 prediction 1 (probability 0.335884094238%) is n04517823 vacuum, vacuum cleaner label index is: 882 prediction 2 (probability 0.151348114014%) is n02676566 acoustic guitar label index is: 402 prediction 3 (probability 0.0977516174316%) is n03109150 corkscrew, bottle screw label index is: 512 prediction 4 (probability 0.0661373138428%) is n03532672 hook, claw label index is: 600

0 Kudos
idata
Employee
2,059 Views

@AshwinVijayakumar - Thanks for all your help and patience. You may want to include something about plugging the NCS directly into the back of the R-Pi (or use a Powered Hub) in the docs for the future.

 

-Kal.

0 Kudos
idata
Employee
2,059 Views

Hello,

 

I ran the installation on a RpI 3+, camera and 7 inch display installed, NCS occupies a USB slot directly. I am able to run the test models for GoogLeNet, SqueezeNet and AlexNet (getting also the "unsufficient memory" error as stated above).

 

But anything "tensorflow" does not work ..

 

Example:

 

pi@raspberrypi:~/workspace/ncappzoo/tensorflow/inception $ make run TF_SRC_PATH not set, making tf_src (cd ../tf_src; make all; cd /home/pi/workspace/ncappzoo/tensorflow/inception) make[1]: Entering directory '/home/pi/workspace/ncappzoo/tensorflow/tf_src' TF_SRC_PATH not set, will use project directory TF_SRC_PATH is now: /home/pi/workspace/ncappzoo/tensorflow/tf_src/tensorflow skipping clone, directory already exists: /home/pi/workspace/ncappzoo/tensorflow/tf_src/tensorflow make[1]: Leaving directory '/home/pi/workspace/ncappzoo/tensorflow/tf_src' TF_SRC_PATH is /home/pi/workspace/ncappzoo/tensorflow/inception/../tf_src/tensorflow Downloading checkpoint files... (mkdir -p model/v3) (cd model/v3; wget -nc http://download.tensorflow.org/models/inception_v3_2016_08_28.tar.gz;) File ‘inception_v3_2016_08_28.tar.gz’ already there; not retrieving. (cd model/v3; tar -xvf inception_v3_2016_08_28.tar.gz;) inception_v3.ckpt TF_MODELS_PATH not set, making tf_models (cd ../tf_models; make all; cd /home/pi/workspace/ncappzoo/tensorflow/inception) make[1]: Entering directory '/home/pi/workspace/ncappzoo/tensorflow/tf_models' TF_MODELS_PATH not set, will use project directory TF_MODELS_PATH is now: /home/pi/workspace/ncappzoo/tensorflow/tf_models/models Skipping clone, directory already exists: /home/pi/workspace/ncappzoo/tensorflow/tf_models/models make[1]: Leaving directory '/home/pi/workspace/ncappzoo/tensorflow/tf_models' TF_MODELS_PATH is /home/pi/workspace/ncappzoo/tensorflow/inception/../tf_models/models Exporting GraphDef file... (cd model/v3; python3 /home/pi/workspace/ncappzoo/tensorflow/inception/../tf_models/models/research/slim/export_inference_graph.py \ --alsologtostderr \ --model_name=inception_v3 \ --batch_size=1 \ --dataset_name=imagenet \ --image_size=299 \ --output_file=inception_v3.pb;) Traceback (most recent call last): File "/home/pi/workspace/ncappzoo/tensorflow/inception/../tf_models/models/research/slim/export_inference_graph.py", line 59, in <module> import tensorflow as tf ImportError: No module named 'tensorflow'

 

The same for any other TF related test run.

 

What could i do? I followed the instruction from https://developer.movidius.com/start of cause.

 

I am really eager to start with some of my models running on one or more NCS soon.

 

cheers

 

Juergen

0 Kudos
idata
Employee
2,059 Views

@jfey We currently don't have support for TensorFlow on the Raspberry Pi yet. Please refer to the release notes for the Neural Compute SDK version 1.12 @ https://github.com/movidius/ncsdk/releases/tag/v1.12.00.01 and scroll down to the Errata section.

0 Kudos
Reply