Editing Granity for Linux
Your changes will be displayed to readers once an authorized user accepts them. (help) |
Warning: You are not logged in. Your IP address will be publicly visible if you make any edits. If you log in or create an account, your edits will be attributed to your username, along with other benefits.
The edit can be undone.
Please check the comparison below to verify that this is what you want to do, and then save the changes below to finish undoing the edit.
Latest revision | Your text | ||
Line 48: | Line 48: | ||
Granity from version 1.14.0 supports connecting with the direct support of FTDI USB chip found on Granite Devices products. This is alternative to the virtual serial port and if Granity finds the compatible FTDI device, it is automatically listed in the communication interface list. | Granity from version 1.14.0 supports connecting with the direct support of FTDI USB chip found on Granite Devices products. This is alternative to the virtual serial port and if Granity finds the compatible FTDI device, it is automatically listed in the communication interface list. | ||
− | {{info|Sometimes kernel's FTDI driver is being loaded automatically and it prevents the usage of direct FTDI support in Granity. If device connection fails to open, try running command ''sudo rmmod ftdi_sio'' and try launching Granity again (if it works, consider | + | {{info|Sometimes kernel's FTDI driver is being loaded automatically and it prevents the usage of direct FTDI support in Granity. If device connection fails to open, try running command ''sudo rmmod ftdi_sio'' and try launching Granity again (if it works, consider making it automatic with [https://www.cyberciti.biz/tips/avoid-linux-kernel-module-driver-autoloading.html these] instructions). Also it may be necessary to run Granity with root privileges (''sudo ./GrantyLinux'') or adjust system USB device permissions. }} |
===Scope graphs not displaying=== | ===Scope graphs not displaying=== | ||
This happens if the executable is launched in the other folder than it's location (because program doesn't find then "flot" folder). To workaround, start program in the same folder where the GranityLinux file is. I.e. in command prompt run ./GranityLinux. The fix for this is coming after V1.9.1. | This happens if the executable is launched in the other folder than it's location (because program doesn't find then "flot" folder). To workaround, start program in the same folder where the GranityLinux file is. I.e. in command prompt run ./GranityLinux. The fix for this is coming after V1.9.1. | ||
− | |||
− | |||
− | |||
− |