Since plugging the battery in, the Wio cannot be detected as “STMicroelectronics Virtual COM Port” by the device manager while in normal mode. I can see the device while it is in DFU mode as “STM32 BOOTLOADER”.
I can upload code to the device in DFU mode but cannot seem to get it into ‘Normal’ mode to operate the code.
Note: before plugging in the battery I have been able to run code thousands of times after uploading in DFU mode by simply pressing the RST button.
Is this an issue that was fixed in the WIO V1.3?
If anyone can please help that would be greatly appreciated!
I Note that you have an incorrect Title on this Posting.
But I do have a battery issue. My Battery cannot connect because the battery plug does not fit the board socket, I tried to force it and the socket broke off the board. I have ordered a new board from Mouser, but I fear the new board will have exactly the same problem. What I need is for Seeed to point to where I can get the correct Battery plug for this board.
Putting that to one side, I too have issues with loading of the STM Virtual Port under Windows 10. This is supposed to be handled within default PlugNPlay operations in Win10.
Here is what happened to me. 
- I managed to get my PC to Load the STM32 Bootloader using the Zadig tool.
- I managed to load the correct board definition after Seeed fixed up the Boards Manager file.
- I loaded the first example Sketch which is sending of an SMS Message.
- When the sketch runs, it does not work, But Now two LEDS are turned on, both RED, located near the battery connector. One of them is flashing slowly.
I need some debug output, for which I need the virtual com port running, and view the output using a 3rd party Com Tool (I am using ‘Serial Port Monitoring’. I try to switch the board into Virtual Com Port Mode and out of DFU Mode, using a combination of Boot Button and Reset Button. What I get is ‘Unknown USB Device - Device Descriptor Request Failed’
I enquired with ST’s Technical Support, who indicated this is likely to be a manufacturer issue, e.g. Seeed
I looked thoroughly through the Seeed Wiki documentation looking for:
a) a description of the Button functions (3 buttons on the board)
b) description of LED’s on the board and which pins they are connected to.
c) Description of how to install SIM Card and SD Card, and what maximum capacity of SD Card is supported.
d) Description of how to connect the 3 antenna’ supplied and how to remove them safely when necessary. What is the best way to deploy the antenna when placing the board into an enclosure.? For example should both antenna be oriented the say way, or should one be vertical, the other horizontal ?
e) When instantiating the USB Board as debugging output (per the example sketch), how to get the correct Device Descriptor to make Windows 10 happy.
This information is not provided. Its a reasonable thing so I cannot see why Seeed have failed to include it.
I am wondering if it is worthwhile to connect up the Seeed OLED display and have it display Debug information. But others have trouble with that display, I fear getting into deeper trouble.
This whole thing is turning into a nightmare for me. Consuming much of my time for the last few days. Its a litany of different problems. Seeed seem to not put in enough effort to making certain the documentation is complete and that the Board works properly out of the box. They need to check what goes into the box when its packed in the factory. They need to ‘test’ the documentation with users to ensure it meets the needs of an average newbie.
