None of the examples of VCOM in the SDK worked in tests.
Tested on several PCs with Termit V3.3.
The fsl_ucwxp.inf trough installation is used.
First sent characters come back, while the next send the Windows hangs. Also with its own terminal program the same behavior.
MSC examples work well.
Can unfortunately not find the reason.
Please help me.
I had the same problem (sending the first character was ok, everything else afterwards was blocking the terminal) with the MCUXpresso SDK V2.2 for the FRDM-K22F board.
After poking around, I have found the solution: I had to configure the terminal connection to use flow control with RTS/CTS:
Then it worked.
I hope this helps everyone else,
Erich
Thank you Erich,
This is unfortunately no solution for me since PC software already exists among the customers.
We want to switch to a new generation of NXP MCU with HS USB.
Would be nice if the SDK without large error search / change was usable.
Can badly tell my boss "the SDK exists" and thereafter still month (s) look for errors.
Can I expect a solution of NXP in the near future?
Otherwise, I'm forced to deal with Cube...
With Cube kanns probably not synonymous everything to be smooth.
Otherwise the work of a programmer would be too easy:)
I have not checked it, but I think there must be an attribute or someting in the descriptor forcing that flow control. From other USB CDC implementations (e.g. NXP USB Stack 4.x) flow control is not necessary.
Erich
Can at least one confirm that it works?
NXP SDK for LPC54608 the same problem with VCOM example.
Keil pack 2.2.0 for LPC54608 VCOM example works...
I did the tests using TeraTerm, have you tried using a terminal other than Termit?
Hi Carlos,
Yes, I use Termite V3.3. and an own test program.
SDK 2.2 the same result. 2 of the COM ports are displayed in the device manager:
JLink CDC UART port (COM3) and Virtual Com Port (COM4).
VCOM can be opened. At the first send I get no answer and the Termite V3.3 hangs.
Keil CDC examples for LPC54608 work well. Unfortunately, no further...
Win10 32 Bit, EWARM 7.80.4. What is your test environment?
Hi Johann,
I have just tested the lpcxpresso54608_usb_examples_usb_device_cdc_vcom_bm example from the SDK 2.2 package and it is working correctly, which error are you getting? Is the vcom port being recognized? Do you have semihosting enabled?
Thanks in advance for your response!
Best Regards,
Carlos Mendoza
Technical Support Engineer
lpcxpresso54608_usb_examples_usb_device_cdc_vcom_bm example from the SDK 2.2 package
is for USB0 FS and it work well.
I would like to put the USB1 HS into operation.
Set for it
#define USB_DEVICE_CONFIG_LPCIP3511FS (0U)
and
#define USB_DEVICE_CONFIG_LPCIP3511HS (1U).
The result as already described - COM port is visible,
the application (e.g Termite) hangs after sending characters to the demo board
Is there a working example for USB HS in the SDK for LPC54608?
Can one help me please the USB1 in HS mode operate?
Best Regards,
Johann Zimmermann
Hi Johann,
I have just tested the lpcxpresso54608_usb_examples_usb_device_cdc_vcom_bm example from the SDK 2.2 package and changed to HS doing the same changes as you and it is working correctly, have you tried using TeraTerm? do you have another computer where you can test? Do you have a USB analyzer to capture what is happening?
I'm using windows 7 enterprise and MCUXpreeso IDE v10.0.0_344.
Thanks in advance for your response!
Best Regards,
Carlos Mendoza
Technical Support Engineer
Hi Carlos,
thanks for the answer.
nfortunately, CDC does not work with SDK_2.2_LPCXpresso54608_2 either.
Have the following stated:
The message arrives correctly, the length and content are correct.
Only the variable s_cdcVcom.startTransactions is never set to 1,
and USB_DeviceRecvRequest () is not called.
PC blocks sending from the next packet and the application hangs.
If I set the variable s_cdcVcom.startTransactions to 1 fix, then the CDC examples work.
Seems something is different on my PC ...?
EWARM V7.80.4
Windows 10 Pro x32Bit
AMD Athlon II X3 455 x64Bit
Best Regards,
Johann Zimmermann