Artemis Bootloading error - COM1 is currently open. Please close any other terminal programs

Hello, I found some older topics on this issue, but no real resolution for Windows. I am running windows 11 Home 22h2. I am using the arduino IDE 2.2.1 and have a sparkfun artemis redboard. I have installed the Sparkfun Apollo3 board manager 1.2.1 core.

I am simply trying to get Blink to run. When I compile and upload the following is displayed:

"Sketch uses 8644 bytes (0%) of program storage space. Maximum is 960000 bytes.

Global variables use 33820 bytes of dynamic memory.

Artemis SVL Bootloader

COM1 is currently open. Please close any other terminal programs that may be using COM1 and try again."

I have tried various USb ports, but no joy. Also I should note that the PC does not beep when I connected the board to the computer via USB A to USB C. This is different behavior than when I hook up an arduino board

Thank you!!

Make sure that you have selected the correct board type in the Arduino IDE.

Make sure that you have selected the correct serial port in the Arduino IDE.

Make sure that the serial port is not already in use by another program.

Try restarting the Arduino IDE.

Try restarting your computer.

Thank you for your reply and I did try each of those steps without success.

Is the serial monitor open in the Arduino IDE? That might cause the bootloader to report that the COM port is in use.

No serial monitor is not open . . .

Is there a way of getting a list of connected USB devices on Windows 11? I’m using a MicroMod board with an Artemis module on Linux. After I connect the board via USB, running lsusb shows me this entry:

Bus 001 Device 006: ID 1a86:7523 QinHeng Electronics HL-340 USB-Serial adapter

The system log reports the presence of a serial device:

ch341 1-4:1.0: ch341-uart converter detected

Could it be a driver issue?

https://learn.sparkfun.com/tutorials/sp … -need-them

I did download the CH340 drivers and it indicated they were already installed. I am at a bit of a loss. I am traveling this week but when I get back I will try on an alternate PC.

Thank you BTW.

OK. Issue solved. I had tried different USBA ports on the pc, and now I just tried a USBC port and it worked. Thank you!