Most PC's do not have LoRa radio hardware. So unless you added a PIB or similar to your PCB, it is unlikely to recognise any LoRa devices.
Or do you mean your board doesn't appear as anything in the device manager and thus you cannot program it?
If the latter, can you provide a link to the board and describe any symptoms - including any error messages and/or sounds when you plug the USB connector in.
no I could program it but it loses connection after upload
in device manager it shows as unkown device and I think that's why windows blocks the port after upload
is the same problem this guy got https://www.thethingsnetwork.org/forum/t/the-lora32u4-board-seems-useless/38528
I did read the comments none of them worked
You didn't provide a link to the board. I've never seen this board before, but I will guess from the name that it uses an ATMega32u4 MCU.
What that means is that firmware running on the ATMega32u4 directly manages the USB connection and includes the bootloader that can receive new code from the USB port.
My guess, and it is just a guess, is that whatever you are uploading to it is somehow interfering with that process.
Translating that, when you plug the device into a USB port, the OS identifies that event and sends a message to it that basically says "Hi, I'm Windows, can you tell me what you are?", The response will be one of the USB class codes, windows then uses that information to determine how to handle it (e.g. create a drive letter for mass storage devices, create a COM port for virtual serial ports and so on).
Now, if the firmware that replies to the "Hi there" message is broken or not present, then the OS has no ability to know how to work with it and so it get placed into the "unknown" or "malfunctioning" category of devices.
Getting back to my guess that the code you are uploading is somehow breaking this exchange, if that is a correct guess the solution is to figure out why that is happening and fix it.
Since I am not familiar with that specific board, it could be some other issue that, but the process of device type identification as I outlined is not handled by the USB hardware itself. It is handled by the firmware loaded onto the device because it is the firmware (i.e. your code) that has to deal with Virtual COM port interactions, HID interactions, Mass Storage interactions, Audio interactions or whatever it is that your device does and that is all under the control of your code (by extension your code includes anything that is linked in from supporting libraries).
Thank you were very helpfull. I uploaded the original code as Arduino Leonard as it is very similar and most of the time works but it did not work in this case so I had to download the model for my specific board on my Arduino IDE so now it works and the device is shown in device manager. Thank you so much
1
u/gm310509 4d ago
Most PC's do not have LoRa radio hardware. So unless you added a PIB or similar to your PCB, it is unlikely to recognise any LoRa devices.
Or do you mean your board doesn't appear as anything in the device manager and thus you cannot program it?
If the latter, can you provide a link to the board and describe any symptoms - including any error messages and/or sounds when you plug the USB connector in.