-
Notifications
You must be signed in to change notification settings - Fork 1
Troubleshooting
This section describes the problems you are likely to encounter and how to solve them.
- Check pin names:
Check preferences.h for pin configuration.
Check your screen’s pin names
Check whether the names of connected pins on the mcrocontroller and on the screen match. - Check for loose connections
- Check for short-circuits
The screen will not start up before it’s fully connected. Connecting it to Vcc and GND will not make Vout have voltage.
If your connection might be loose and you want to try that by wiggling the cable, reconnect it every time you change position until it shows something.
Place a capacitor between Vout and GND
Reduce the capacitor’s capacity between Vout and GND
That’s a software problem, fix coming soon
Reduce capacitor size connected parallel with the button (1µF goes well with ATTiny2313 and ATMega8 internal pull-up resistors).
Increase capacitor size connected parallel with the button (see http://www.ganssle.com/debouncing.pdf)
You may get output like this:
avrdude -c usbasp -p m8 -U flash:w:mmc.hex
avrdude: Warning: cannot open USB device: Permission denied
avrdude: error: could not find USB device "USBasp" with vid=0x16c0 pid=0x5dc
This means you don’t have necessary permissions to access your USB device. You can:
- Upload as root (not recommended – you’re likely to do all kinds of other things as root too)
- Change the device permissions
Manual changing of permissions is not worth the trouble. It’s not straightforward to find the device file and it needs to be done at every connect.
To change permissions automatically using udev, make sure you have a group called usb
and that your user is its member. Then create a rule file to match your device (don’t forget to change USB IDs):
SUBSYSTEM=="usb", ATTRS{idVendor}=="16c0", ATTRS{idProduct}=="05dc", GROUP="usb"
and save it as /etc/udev/rules.d/10-usbasp.rules
.
Restart udev, reconnect the device and check if it works.