Hello I successfully uploaded and ran the blink example to my arduino board and it worked perfectly. Then i uploaded the second 'AnalogReadSerial' sketch. The first time it worked fine i turned on the serial monitor and i saw the 1's and 0's output. Second time i tried to upload the blink example again but it threw an error at me (one in the subject) + did you select the right one from menu?

Using 'serial' to connect to an Arduino. >>fopen(s) Error using serial/fopen (line 72) Open failed: Port: /dev/ttyACM0 is not. The port should be found. Arduino Tools >Serial Port greyed out. The error message is 'Serial port COM1 not found. And change it to your port: serial.port=/dev/ttyACM0. Serial port not found /dev/ttyACM0 - Linux Mint 17 Qiana.

Well i can't since it's greyed out! I have looked at other posts in the forum but it's all bullshit no actual solution to the problem. This is seriously pissing me off right now, any help appreciated. My system: - Arduino uno, - Linux Ubuntu 'Natty' 11.04, 32-bit, Thanks, Janek566.

Trying to debug I need to use serial out to a Ubuntu Terminal. But I get connection error.

Using the CLI: gives me $ spark serial list Found 1 core(s) connected via serial: 1: /dev/ttyACM0 So the core is visible. But then: $ spark serial monitor 1 Opening serial monitor for com port: '/dev/ttyACM0' Serial err: Error: Cannot open /dev/ttyACM0 Serial problems, please reconnect the core. Best Italian Music Torrent.

I assume that reconnect means unplug then replug, which also removes power in my case. I am a member of the dialout group: sudo usermod -a -G dialout xxxxx. Nrobinson2000, thank you for the recommendation. Seems like something that should be included in the spark documentation somewhere. Still do not understand though why this is needed. I don't need similar to access usb drives, arduino's or multiple other devices.

In response to aceperry I read that it is not a good thing to run processes using superuser authority as this can leave my linux kernel open to attack. The general advice I see is that Superuser should be limited to maintenance activities where kernel changes are needed. A lot of other packages come with rpm install scripts that will do things like add udev rules to change the permissions on USB devices they want to talk to.

What you hear is correct, as a rule you want to avoid running packages under sudo, because it will result in painful things like files/directories created in your $HOME that you cannot access, overwrite or delete. The correct fix is adding and maintaining udev rules for the spark VID/PIDs, and automatically installing them as part of the install process. If this is supposed to happen already then it is broken, if not then it should be made to happen. Resident Evil Revelations 2 Corepack.