RT-Thread / RT-Thread/rt-thread
AVR32: CDC VCOM console for MSH for Mizar32
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 12.2k
- Forks
- 5.4k
- Avg merge
- 4d 12h
- Merged PRs (30d)
- 40
Description
Dear RT-Thread community, Greetings!
I have been exploring the code to implement the support for USB CDC
for the Mizar32 (AVR32) platform. I have currently enabled UART-1 as
the default console for the Mizar32 platform. I had a few questions to
ask. I will list them as points:
-
Without going through the RT-Thread's USB communication device
sub-system/protocol (CDC), is there a way to route the default
RS-232 interactions on MSH via Microchip's CDC stack? -
I made a test (debug) Microchip Studio application a while ago
for testing RT-Thread's functionality with the drivers I
implement/experiment with; i.e. before I send a PR. The code is here
[1].
I tested VCOM on Mizar32 by calling the USB stack's routine within
RT-Thread. Can you please check [2]? In [2], I am just instantiating
a thread (rt_thread_usb) to invoke the Atmel's stack for
enumeration. I am attaching a picture of it.
I used an FTDI breakout to talk to MSH on UART-1 and spawned another
terminal emulator instance to check the output of CDC VCOM. It
works. Is there a way to override the default UART-1 to bring in
VCOM and the stack at [2] for MSH?
-
I have seen RT-Thread's support for CherryUSB and TinyUSB. They
are outside RT-Thread. Can a stack such as Atmel's in [3] be within
AVR32's BSP? Would you permit this? -
I read a very interesting article [4] which introduced me to
vconsole. I can find it within the packages menu but not on Github.
I am not sure if the link is broken. Is there a way to implement
what vconsole does by default on Mizar32 - with [3]?
Please do give me your suggestions. Merry Christmas!
References:
[1]:https://github.com/ramangopalan/rtthread_mizar32b_sample/
[2]:https://github.com/ramangopalan/rtthread_mizar32b_sample/blob/master/rtthread_mizar32b_sample/bsp/avr32/at32uc3a0256/application.c
[3]:https://github.com/ramangopalan/rtthread_mizar32b_sample/tree/master/rtthread_mizar32b_sample/bsp/avr32/software_framework/drivers/usb-cdc
[4]:https://github.com/RT-Thread/rt-thread/issues/4227
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the AVR32 application.c example and the usb-cdc driver directory linked in the issue, then compare the vconsole discussion in issue #4227. Investigate how MSH currently uses UART-1 and how RT-Thread's USB CDC support is integrated. The issue does not define a concrete acceptance condition for routing MSH through CDC or including the Atmel stack.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- cli, embedded-iot
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100