| Products > Test Equipment |
| Sniffing the Rigol's internal I2C bus |
| << < (810/899) > >> |
| wyx:
Hi, I am a EE student in US. I recently purchased a MSO2072scope and I follow the hack instruction using ubuntu to unlock my scope feature. However, there's always some error message while compiling the code from github. Can anyone help me with that? My scope is running software 03.01 and hardware 2.2 is it able to be upgraded using that hack?? |
| nbritton:
--- Quote from: wyx on October 31, 2015, 04:20:31 pm ---Hi, I am a EE student in US. I recently purchased a MSO2072scope and I follow the hack instruction using ubuntu to unlock my scope feature. However, there's always some error message while compiling the code from github. Can anyone help me with that? My scope is running software 03.01 and hardware 2.2 is it able to be upgraded using that hack?? --- End quote --- What is the error message? What version of Ubuntu are you using, I would recommend the 14.04 LTS release. |
| Macbeth:
Just remember with Ubuntu you often have to use sudo to do stuff. Like when compiling something you need to do sudo make install rather than make install. I know obvious, but I wasted a whole day when I didn't realise that just accessing serial ports or USB also requires root privilege! :palm: |
| farzadb82:
--- Quote from: Macbeth on November 01, 2015, 10:41:30 pm ---Just remember with Ubuntu you often have to use sudo to do stuff. Like when compiling something you need to do sudo make install rather than make install. I know obvious, but I wasted a whole day when I didn't realise that just accessing serial ports or USB also requires root privilege! :palm: --- End quote --- It sounds like you need to create a udev rule for your device. You should really avoid running things as sudo when possible. The only time you'd absolutely have to is when you're installing something into the system. Other than that, you shouldn't have to run commands using sudo. Here's a good reference for creating udev rules (http://ubuntuforums.org/showthread.php?t=168221). It talks specifically about creating rules for external media, but the same concepts can be applied to any usb device. |
| Macbeth:
--- Quote from: farzadb82 on November 02, 2015, 01:38:46 am --- --- Quote from: Macbeth on November 01, 2015, 10:41:30 pm ---Just remember with Ubuntu you often have to use sudo to do stuff. Like when compiling something you need to do sudo make install rather than make install. I know obvious, but I wasted a whole day when I didn't realise that just accessing serial ports or USB also requires root privilege! :palm: --- End quote --- It sounds like you need to create a udev rule for your device. You should really avoid running things as sudo when possible. The only time you'd absolutely have to is when you're installing something into the system. Other than that, you shouldn't have to run commands using sudo. Here's a good reference for creating udev rules (http://ubuntuforums.org/showthread.php?t=168221). It talks specifically about creating rules for external media, but the same concepts can be applied to any usb device. --- End quote --- Yes, that is exactly what I ended up doing. Thanks for reminding me! I also had to add my account to the dialout group to allow me to use /dev/ttyUSBx Oh, one thing that bugs me. I've installed the blackfin toolchain and whenever I am using UrJTAG (bfin-jtag) I've found the cursor keys seem to be mapped to something strange and so I just get things like "[]]]" output when I press a key. It makes recalling command history a PITA. I've also tried UrJTAG from the official repo using apt-get-install and with that version the command history and editing using cursor keys works as expected. :-// |
| Navigation |
| Message Index |
| Next page |
| Previous page |