Cannot access board in IDE (COM port)

Using Arduino Installation & Troubleshooting
#1

I cannot select the com port in the IDE as it is gerayed out. I presume this is not a IDe problem but general problems.

In windows I have enabled legacy devices in device manager but COM port is showing error 34. I am on a thinkpad ryzen pro 7. All drivers etc are up to date according to AMD and Lenovo diagnostics.

i don't know where to start.

In linux (ubuntu 20.04.2) I get the following output:
cax@cax-ThinkPad-T14-Gen-1:~$ dmesg | tail
[ 6149.469381] ACPI Error: Aborting method _SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20200110/psparse-529)
[ 6149.469393] ACPI Error: Aborting method _SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20200110/psparse-529)
[ 6149.469400] ACPI Error: Aborting method _SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20200110/psparse-529)
[ 6149.541179] ACPI Error: No handler for Region [ECSI] (00000000275a2169) [EmbeddedControl] (20200110/evregion-127)
[ 6149.541192] ACPI Error: Region EmbeddedControl (ID=3) has no handler (20200110/exfldio-261)
[ 6149.541211] No Local Variables are initialized for Method [ECRD]
[ 6149.541213] No Arguments are initialized for method [ECRD]
[ 6149.541217] ACPI Error: Aborting method _SB.UBTC.ECRD due to previous error (AE_NOT_EXIST) (20200110/psparse-529)
[ 6149.541229] ACPI Error: Aborting method _SB.UBTC.NTFY due to previous error (AE_NOT_EXIST) (20200110/psparse-529)
[ 6149.541237] ACPI Error: Aborting method _SB.PCI0.LPC0.EC0._Q4F due to previous error (AE_NOT_EXIST) (20200110/psparse-529)
cax@cax-ThinkPad-T14-Gen-1:~$

cax@cax-ThinkPad-T14-Gen-1:~$ dmesg | grep tty
[ 0.120735] printk: console [tty0] enabled

I don't know where to start even. I have 3 new boards and multiple USB cables I have verified are functional.

#2

See if you can narrow down the scope of the problem. First try the hardware on another machine,if it works then the cables and boards are AOK. You could load Linux in demo mode and test it that way, that will confirm your hardware is ok and it is a problem with windows. Beyond that you will need somebody much better versed in windows then I am. I left Windows shortly after the release of version 7 and went to Linux, best computer decision I have made.

#4

Yeah, good idea to narrow down the problem like that. Could be a borked board or cable, so hard to tell.

#5

you could try a linux liveusb, they are good to have anyway, so your time spend making one won't be wasted.

#6

This topic was automatically closed 120 days after the last reply. New replies are no longer allowed.