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

Unable to find device #3

Open
bakerbrown opened this issue Aug 2, 2018 · 8 comments
Open

Unable to find device #3

bakerbrown opened this issue Aug 2, 2018 · 8 comments

Comments

@bakerbrown
Copy link

After a clean install 2018-06-27-raspbian-stretch I can build your code with DEBUG=1 and execute the code using ./AR1100 -c 9, but all I ever get is an error saying it cannot find the device?

@tom-2015
Copy link
Owner

I will have to update the code to be compatible with stretch. This will take some time.
Quick solution is to install Jessie on an other SD card, do the calibration and then swap back to the stretch SD card.

@rbrucemtl
Copy link

Hello, I also can not get the device to be found. I don't think this is related to just Stretch... I installed Jessie on a SD card as suggested above but still no device is found. I can use the windows official calibration app perfectly but I can't use that to calibrate my LCD on the Pi.

Any ideas on how to get this to work? What Pi OS version /kernel did you originally use to create this program?

Thank you.

@tom-2015
Copy link
Owner

tom-2015 commented Sep 15, 2018

I was going to test it this weekend but I can't find my AR1100 now. Can you check the product and vendor ID the device is using (command lsusb)? Maybe it's looking for the wrong product/vendor.

Can you try to compile with
make clean
make DEBUG=1
program will output what goes wrong

@rbrucemtl
Copy link

Hi,

Thank you for responding. I eventually got it working. I needed to install an older Jessie image and make sure not to do and apt-get upgrade. I also needed to run the command logged in as superuser (sudo su), just using sudo with the AR1100 command was not enough for some reason. Then the program ran. DEBUG=1 did not say anything about permissions only device could not be found.

I think some kernel changes in later versions of Jessie might have made even Jessie incompatible. I did not dig into it much. Now that my screen is calibrated and the calibration is stored in EEPROM I won't need it again until a future project.

Thank you for the utility it saved me a lot of time in my project.

@ghost
Copy link

ghost commented Sep 19, 2018

Hi,
I am facing the same issue, and going back to jessie is not a solution for me.
@tom-2015 If you have an idea of what needs to be done, I am willing to put in some work to solve this.

@tom-2015
Copy link
Owner

Must be a problem with the libusb but need more time to fix it.
You can use the jessie only for calibration, after that you can move to stretch (just change SD card). The calibration is stored in the AR1100. Just don't move the touch panel after calibration.

@ghost
Copy link

ghost commented Sep 20, 2018

Just tried again on a stretch and it worked out of the box.
I think I might have forgotten to run it with sudo

@tom-2015
Copy link
Owner

tom-2015 commented Oct 6, 2018

Tried it on stretch and seems to work for me but it needs to run as root (sudo).

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

3 participants