Flick demo's won't run

[john63]

very new to begin with but have jessie running on rasp pi zero w. ran the install line for Flick gesture control without issue.When i run the flick demo in the terminal i get this
pi@raspberrypi:~ $ flick-demo
Did not receive firmware info
Traceback (most recent call last):
File "/usr/local/bin/flick-demo", line 4, in <module>
__import__('pkg_resources').run_script('flicklib==0.0.1', 'flick-demo')
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 534, in run_script
self.require(requires)[0].run_script(script_name, ns)
File "/usr/lib/python2.7/dist-packages/pkg_resources.py", line 1445, in run_script
exec(script_code, namespace, namespace)
File "/usr/local/lib/python2.7/dist-packages/flicklib-0.0.1-py2.7.egg/EGG-INFO/scripts/flick-demo", line 4, in <module>
__import__('pkg_resources').run_script('flicklib==0.0.1', 'flick-demo')
File "build/bdist.linux-armv6l/egg/flicklib.py", line 479, in <module>
NameError: name 'sys' is not defined
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "build/bdist.linux-armv6l/egg/flicklib.py", line 462, in _exit
TypeError: 'NoneType' object is not callable
Error in sys.exitfunc:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "build/bdist.linux-armv6l/egg/flicklib.py", line 462, in _exit
TypeError: 'NoneType' object is not callable

have no idea whats going on. I did notice at one point when i checked directories it installed at "root" instead of pi but even changing that produced same result. Do i need to update the flick software? and how do I do that?
Any help is appreciated. Yup, 30 seconds for most people but hours later......sniffle....

[ukscone]

the installer should have enabled i2c but that would be the 1st thing i'd check (after checking that the flick board is installed correctly e.g. the pins are lined up correctly and the board is pushed down enough)

sudo raspi-config

then go to interfacing options then select i2c and enable and after exiting raspi-config reboot

if that doesn't help i'd try reinstalling the flick software by rerunning

curl -sSL https://pisupp.ly/flickcode | sudo bash

if that doesn't work come back here and we'll see if we can workout what's going on.

[ukscone]

oh just had a thought


type the following line

Code: Select all

wget https://raw.githubusercontent.com/PiSupply/Flick/master/bin/flick-demo

then type

Code: Select all

chmod 777 flick-demo

then type

Code: Select all

./flick-demo

and see if you still get the errors

[Rekk]

Hi John63,
I've just tried to test my Flick today too, and I had the same issue.

Once I've try what ukscone said, the error was almost the same.

Now, after checking my wires, there is no more issue when I execute "flick-demo".

From the top left corner, the order of wires is : (in the bottom pins, from left to right) :
brown / red / orange / purple / blue / yellow / green / grey.

I hope this will help you.

[john63]

Thank you gentlemen will try today. Wish it was a wire issue but being a zero no wires just pins. Thanks for the reply though

[john63]

tried your suggestions to no avail. Error message is slightly smaller but still no go
pi@raspberrypi:~ $ ./flick-demo
Did not receive firmware info
Traceback (most recent call last):
File "./flick-demo", line 4, in <module>
import flicklib
File "build/bdist.linux-armv6l/egg/flicklib.py", line 479, in <module>
NameError: name 'sys' is not defined
Error in atexit._run_exitfuncs:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "build/bdist.linux-armv6l/egg/flicklib.py", line 462, in _exit
TypeError: 'NoneType' object is not callable
Error in sys.exitfunc:
Traceback (most recent call last):
File "/usr/lib/python2.7/atexit.py", line 24, in _run_exitfuncs
func(*targs, **kargs)
File "build/bdist.linux-armv6l/egg/flicklib.py", line 462, in _exit
TypeError: 'NoneType' object is not callable

Just can't understand the errors when others are putting in a line of code and their off to the races. Part of the learning curve I guess. Open to more suggestions though, Thanks

[john63]

I should also mention at boot I do get the e2fsck out of date...message don't know if this is contributing to the error. I understand what it is now, but not sure if its causing the error.Thanks

[ukscone]

i'm a bit flummuxed
to check there aren't any weirdnesses between the phat and hat i switched my flick hat for the phat and no errors or anything.

the only thing I can think of to try now is to do is to try a fresh sd card, do an apt-get update && apt-get upgrade and do a fresh install of the flick software.

it could work and if not then at least we'll have cut down on the things that it could be

[ukscone]

oh one other thing you could check is

Code: Select all

 i2cdetect -y -q 1

and see if 42 is shown

it'll look like

pi@raspberrypi:~/flick-tests $ i2cdetect -y -q 1
0 1 2 3 4 5 6 7 8 9 a b c d e f
00: -- -- -- -- -- -- -- -- -- -- -- -- --
10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
40: -- -- 42 -- -- -- -- -- -- -- -- -- -- -- -- --
50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
60: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- --
70: -- -- -- -- -- -- -- --
pi@raspberrypi:~/flick-tests $

if it does look a bit like that then we know the hardware is probably ok and we can concentrate on the software if it doesn't look like that it could be that i2c isn't setup right or it could be hardware

[john63]

with the example given there is a blank slate on mine. No 42, So I'm guessing its installation of the board? my install was basically plop the header on stuck the flick on top and mounted as instructed with flick. Hate to even say this out loud but the header I put on does it have to be soldered to the board, as mine is not.

[ukscone]

i'm not quite sure what you mean. did you not solder a header onto the pizero? you just rested the header on the holes?

could you post a photo?

you do need to have a header soldered on to the pizero, well soldered or hammerheaders.

[john63]

Sadly I think that's the answer, gauging from your answer. ( I did say I was new) In my defense and its weak at best, in the product description it said no soldering required. So going forward, I will solder the header to the board and let you know how that goes.Thanks

[ukscone]

it's ok it's a simple mistake to make. they mean that the flick board doesn't require soldering. they assume (and we all know what that means ) that the header is already soldered onto the pizero as well you can't attach a pHat without the pizero having a header.

[john63]

Thanks feel like an idiot, but at the same time appreciate the time you took to help me. My son has the electrician has steady hands and will do it for me mid week. Will do better research before I post and again thank you. John