I have a pi3 and just got the Flick large. Connected it up, checked the wiring all is good. Ran the i2cdetect and I have just this device detected as 0x42 perfect! right - ran an apt-get update, apt-get upgrade then the curl command to install the flick demo code and libraries. Everything seemed good. On this raspberry pi I do have a touch screen installed, which works great. Other than that this pi3 has nothing else attached to it.
When I run the flick-demo it starts up displays the text (I'm running it from an ssh session). Looks good so far, but when I try to use the pad nothing happens. When I p[ress Control-C to exit the program this is what I see:
Code: Select all
flick-demo 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).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 147, in <module> File "/usr/lib/python2.7/curses/wrapper.py", line 43, in wrapper return func(stdscr, *args, **kwds) File "/usr/local/lib/python2.7/dist-packages/flicklib-0.0.1-py2.7.egg/EGG-INFO/scripts/flick-demo", line 145, in main KeyboardInterrupt
Firmware valid: Yes
Hardware Revison: 99.128
Params Start Addr: 0x7300
Library Loader Version: 19.100
Library Loader Platform: Hillstar
Firmware Start Addr: 0x1000
Firmware Version: 1.3.14;p:HillstarV01;x:
Is there a script to help in debugging issues like this? If I run i2cdump -y 0x42 should I see anything other than zeros when touching the board?