-
Notifications
You must be signed in to change notification settings - Fork 394
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
1,168 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm getting a permission error:
Failed to connect to port (/dev/serial/by-id/usb-Espressif_USB_JTAG_serial_debug_unit_40:4C:CA:C8:A7:40-if00). Error: Port failure Error: Permission denied. Try adding your user to the dialout group and restart (sudo adduser $USER dialout)
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm going to see if I can add it to rules.d to see if that makes a difference
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you, please update us on the rules. What's the VID:PID ?
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
303a:1001 Espressif USB JTAG/serial debug unit
I believe that is the one.
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Did the udev rules trick work? you're sure there are no other ports on the sytem?
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, I still have a permissions error. I also reloaded udev rules, gonna check a few things. There isn't already a pegasus.rules file somewhere else? I am in /usr/lib/udev/rules.d
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I even tried adding it to an existing rule to see if I could get it working, still shows permission denied.
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmmm looks like it thinks this is a dialout device. Gonna grep all the rules for 303a and see if it's somewhere else.
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Got it, yea it looks like we needed to at my user to the dialout group to get it working. weird.
I will put in a pull request to add the 99-pegasus.rules file
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Where do I add the rule for this? It's just adding vendor 303a to MODE="0666"
And I guess I we would need to test if the add user to dialout group can be resolved as well.
sudo adduser $USER dialout
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@chrysikos Can you offer any help regarding the issue reported above?
9b00c50
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It may be something unique to my ubuntu setup. I will try and setup on my other x86 Ubuntu and see if it happens again.
I don't think it was a rules.d permission setting but something to do with the user not setup to use that sudo adduser $USER dialout.
I couldn't find that vendor id being used as a dialout device. So I am not sure what's going on here.
I will try it on my other system tonight if I can.