TinyCLR Config v2.3.0.1000 silently crashes when connecting to a COM port. This happens when trying to set the speed to 921600, but most COM equipment does not support this speed and throws an exception, as a result the port is not initialized and the program crashes.
Please provide minimum setup and code needed to reproduce this issue. We need a way for us to see what you are seeing please.
Uhhh… Gus, I’m afraid you misunderstood me.
This has nothing to do with the program in SCM20260.
I have a physical COM port that doesn’t support high speed, and a USB-CDC adapter that supports 921600.
- I open TinyCLR Config v2.3.0.1000.
- SCM20260 is in Bootloader mode.
- I select the port: “COM1”.
- I click “Connect”.
- TinyCLR Config shuts down without saying goodbye.
I hope you won’t kick me too hard. I used dnSpy to try to find the cause of the crash. If connectionManager.Connect(port)
returns null
- then “TinyCLR Config” crashes.
But it returns null
:
- if there was an exception when changing the speed (in my case, it is a physical port);
- if it did not wait for a response;
- received a response at a speed of 921600 and requested a restart of the device (in my case, it is a virtual CDC port).
This we need to look into.
The baud rate doesn’t mean anything when using USB.
Thank for adding to github issue, we will look into it soon.
I agree, I made a mistake. When connecting USB<->USB-CDC it doesn’t mean. I meant the physical USB<->RS232 adapter on the CH430, FT232, etc. chips.