Page 5 of 5
Re: USB CDC on STM32F746 with ChibiOS 16.1
Posted: Sat Aug 06, 2016 11:14 am
by rew
Korken wrote:* If I do not send any data at all, there is no halt.
* If I do not send data until after I have opened the port (wait with sending until a character has been received), there is no halt.
You should not send data if the port is not opened. This overflows the buffer inside chibios and eventually halts your process, or in your case causes a "panic". It might be nice to have a flag say: "not really imporant, if the computer doesn't read this data, forget about it"...
Re: USB CDC on STM32F746 with ChibiOS 16.1
Posted: Sat Aug 06, 2016 12:54 pm
by Giovanni
The problem is that it should not panic, simply the writer should get MSG_RESET.
Panics cannot be a normal reaction to an externally-triggered event.
Giovanni
Re: USB CDC on STM32F746 with ChibiOS 16.1
Posted: Sat Aug 06, 2016 8:28 pm
by rew
In my case the important: "measure something (Debug: print measurement) do something " thread stopped. But I can imagine that e.g. a thread not processing data trhown at it would cause another thread to crash. On the other hand, IIRC there are traces that indicate that this is happing in the thread that is printing things to the USB port, right?
Re: USB CDC on STM32F746 with ChibiOS 16.1
Posted: Wed Aug 17, 2016 1:13 pm
by Korken
Have you had any success with this problem?
The workaround seems to be working good for those wondering.
Re: USB CDC on STM32F746 with ChibiOS 16.1
Posted: Tue Aug 30, 2016 10:06 am
by Giovanni
Hi,
I tried using CuteCom on Mint 18 and it works using trunk code on an STM32F746-Discovery board.
I get the prompt and the OS executes the commands.
Enabling/disabling handshake and parity on CuteCom makes no difference, am I missing some fundamental step?
Giovanni
Re: USB CDC on STM32F746 with ChibiOS 16.1
Posted: Fri Sep 02, 2016 1:14 pm
by Korken
Hmm, seems to be the correct procedure.
I will create a small example where I get the error.
Re: USB CDC on STM32F746 with ChibiOS 16.1
Posted: Fri Sep 02, 2016 2:27 pm
by Giovanni
Is it possible you have some backgroud process writing on com ports that triggers the problem?
I have a clean Mint Cinnamon install.
Giovanni