Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cannot access dev/ttyACM0: No such a file or directory #23

Open
Carbord opened this issue Sep 12, 2020 · 18 comments
Open

cannot access dev/ttyACM0: No such a file or directory #23

Carbord opened this issue Sep 12, 2020 · 18 comments

Comments

@Carbord
Copy link

Carbord commented Sep 12, 2020

I have been developing the ROS package for AWR1642ES2.0 EVM. However, when run the command "sudo chmod 666 /dev/ttyACM0", I encountered the error "cannot access dev/ttyACM0: No such a file or directory". I wonder if you have seen this error before and how to fix it. Looking forward to your reply, thanks!

@RahulKumarBazia
Copy link

try the following command to list the ports,
$ ls /dev/*
its usually either /ttyACM0 or /ttyACM1

@Carbord
Copy link
Author

Carbord commented Sep 22, 2020

try the following command to list the ports,
$ ls /dev/*
its usually either /ttyACM0 or /ttyACM1

Thanks a lot. And I would like to ask whether this ROS package for AWR1642ES2.0 EVM can capture 3D point cloud information of the object, since the z-coordinate is always 0 in my experiments. Looking forward to your reply, thanks!

@senguptaa
Copy link
Member

@Carbord Answered this in the other channel...tl;dr: Unfortunately no, 1642 doesnt have an elevation channel, so z would always be 0

@jacob-02
Copy link

I have tried the solution that @RahulKumarBazia has suggested. I cannot find a < dev/ttyACM0> file
Screenshot from 2021-10-23 19-44-59

@mggioffre
Copy link

@jacob-02 Did you ever figure this problem out? I'm having a similar issue. dev/tty/ACM0 does not show up when I use the ls /dev/* command

@Youri-is-super-awesome
Copy link

@jacob-02 got the same issue as you and @mggioffre

@CalenOlsen
Copy link

Same issue

@VenomFate-619
Copy link

same issue

@adithyasunil26
Copy link

I think the issue is that your board isn't even connecting properly or is unrecognised by your system which would lead to the mentioned files not existing. Are you able to flash the board with the demo files using uniflash from the same system?

@alexander-kle
Copy link

Did anyone solve this issue yet?

@aidahimm
Copy link

In my case, I connected the board and it was detected by UniFlash so it must have been recognized properly. I was able to flash the board using my binary file successfully, yet still there is no ttyACM0/1 in my /dev folder (neither on my mac OS nor using ubuntu VM)

@DevVermaTheOne
Copy link

DevVermaTheOne commented Oct 17, 2022

try the following command to list the ports, $ ls /dev/* its usually either /ttyACM0 or /ttyACM1

In my case it completely skipped ttyACM0 and ttyACM1.
My ports were ttyACM2 and ttyACM3.

@sreerakhi9
Copy link

I have tried the solution that @RahulKumarBazia has suggested. I cannot find a < dev/ttyACM0> file Screenshot from 2021-10-23 19-44-59

same in my case, did you find a solution?

@aidahimm
Copy link

Actually since I was using VirtualBox, I had to make sure the USB-connected sensor was recognized by the VM by adding it as a device in the settings (also, if you're using Contiki make sure you start the container /after/ connecting the sensors)

@sreerakhi9
Copy link

Thank you so much, the issue is resolved now

@Martin-Imrich
Copy link

Martin-Imrich commented Nov 18, 2022

I was working with STM32MP1C-DK2 there it is called with /dev/ttyACM0. But since I switched to another board STM32MP1C-Phytec. My port was /dev/USB0.

To find it in your case try:

  • Start with your device unplugged
  • Open terminal (i suggest in default home/(user)/)
  • Type "ls /dev > device_names.txt" command, to write all the device names currently available to a file.
  • Next, plug in your device to the port
  • I am using vmware and I also had to go to Player/Removable devices/(find your device in my case "RS232-HS") and click to connect
  • To same terminal type "ls /dev | diff - device_names.txt" you will get the differences between the current list of device, and the list after.
  • (maybe there is more simple way to check new device.... let me know)

image

You can try in another terminal window continuously monitor device with "watch ls /dev/ttyUSB0"

Now we found our device, lets connect:

  • minicom -D /dev/ttyUSB0
  • Permission denied?
  • sudo minicom -D /dev/ttyUSB0
  • Welcome to minicom

@MiguelCigano
Copy link

Hola les comparto la página en donde encontré la solución.

https://support.arduino.cc/hc/en-us/articles/360016495679-Fix-port-access-on-Linux

@adithyasunil26
Copy link

Another possible cause for the issue can be the incorrect setting of the SOP jumpers on the board. For the board to work as described, it must be in functional mode (Refer to the manual of the respective board for SOP jumper configurations for different modes).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests