Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't open device file: /var/lib/jpcnn/char_dev and crashes on RPi/Raspbian #79

Open
hallba opened this issue Jul 22, 2017 · 1 comment

Comments

@hallba
Copy link

hallba commented Jul 22, 2017

Related to #36 and #56

Using the pre built rpi binaries, the error described in #56 arises. However, fixing the "MAJOR_NUM" and recompiling using one of the below make commands creates a binary that crashes the rpi requiring a hard reset (i.e. Pulling the plug)

make TARGET=pi GEMM=eigen
make TARGET=pi GEMM=piqpu
make TARGET=pi GEMM=atlas

@hallba hallba changed the title Can't open device file: /var/lib/jpcnn/char_dev and crashes on RPi Zero Can't open device file: /var/lib/jpcnn/char_dev and crashes on RPi/Raspbian Jul 24, 2017
@hallba
Copy link
Author

hallba commented Jul 24, 2017

Some further testing with a model B suggests that the issue is the updates to the OS not the hardware. Modifying the make file to create a new target allows compilation with alternative libraries.

Testing pull request #74 gives a working binary but much slower than reported elsewhere (order of magnitude). Testing with the supplied images takes ~30 seconds using a pi zero (compiled using piqpu). This is comparable to using atlas or eigen so I believe that the QPU are not being used, though I'm not sure why. Compiling the related pi-gemm repo gives the expected speed up.

As a workaround, creating a symlink from /dev/vcio to /var/lib/jpcnn/char_dev allow some the compiled binaries to work on both the model B and the pi zero. This is much faster than my own attempted compilations but still twice as slow as the reported speed (ie 6 seconds rather than 3). Until the compilation issues are fixed this is a good solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant