Quality RTOS & Embedded Software

 Real time embedded FreeRTOS RSS feed 
Real time embedded FreeRTOS mailing list 
Quick Start Supported MCUs PDF Books Trace Tools Ecosystem TCP & FAT Training



Posted by madis on January 3, 2008

I posted the same issue to the AT91 forum too, but no reply so far. I dont know how many of you follow the atmel forum, sorry if you all have seen it already. But maybe somebody can give me a hint.

Im running FreeRTOS and USB CDC device on SAM7X256 (USB stuff is the same as in FreeRTOS demo project).

Schematic is the same as for SAM7X evaluation board. USB pullup is permanently connected to the Vcc.

Everything works fine under normal conditions. I can open the virtual com port and communicate to it via terminal. But the problem occurs when I remove the USB cable or power and but it back while the com port is open under windows (terminal program is running and com port is open). After cycling the power or connecting/disconnecting USB cable, its not possible to communicate to device anymore. After I close the com port in terminal, Im not able to open it anymore. Only thing that helps is that after closing the com port in terminal software I have to recycle the power or disconnect/connect the USB cable again.

This is one way I can reproduce the problem. Original problem occurs after board is running for eight-ten hours and pc is constantly communicating to it. Virtual com port hangs up and not possible to reopen it without cycling the power of the pwb board or disconnecting/connecting the cable.

Is there any workaround for this problem? Any way to force windows to re-initialise the device while USB pullup is permanently on? One solution would be to make pullup switchable, but what about SAM-BA then, as I understood SAM7X bootloader does not deal with USB pullup...? And bad thing is that I dont have any IO left anymore...



Posted by Richard on January 3, 2008
Basically - I'm not sure what the issue is. The CDC driver is just a demo and may not be fully compliant. Running the comms through some sort of protocol analyser might highlight messages that are not being handled.


[ Back to the top ]    [ About FreeRTOS ]    [ Sitemap ]    [ ]

Copyright (C) 2004-2010 Richard Barry. Copyright (C) 2010-2016 Real Time Engineers Ltd.
Any and all data, files, source code, html content and documentation included in the FreeRTOSTM distribution or available on this site are the exclusive property of Real Time Engineers Ltd.. See the files license.txt (included in the distribution) and this copyright notice for more information. FreeRTOSTM and FreeRTOS.orgTM are trade marks of Real Time Engineers Ltd.

Latest News:

FreeRTOS V9.0.0 is now available for download.

Free TCP/IP and file system demos for the RTOS

Sponsored Links

⇓ Now With No Code Size Limit! ⇓
⇑ Free Download Without Registering ⇑

FreeRTOS Partners

ARM Connected RTOS partner for all ARM microcontroller cores

Renesas Electronics Gold Alliance RTOS Partner.jpg

Microchip Premier RTOS Partner

RTOS partner of NXP for all NXP ARM microcontrollers

Atmel RTOS partner supporting ARM Cortex-M3 and AVR32 microcontrollers

STMicro RTOS partner supporting ARM7, ARM Cortex-M3, ARM Cortex-M4 and ARM Cortex-M0

Xilinx Microblaze and Zynq partner

Silicon Labs low power RTOS partner

Altera RTOS partner for Nios II and Cortex-A9 SoC

Freescale Alliance RTOS Member supporting ARM and ColdFire microcontrollers

Infineon ARM Cortex-M microcontrollers

Texas Instruments MCU Developer Network RTOS partner for ARM and MSP430 microcontrollers

Cypress RTOS partner supporting ARM Cortex-M3

Fujitsu RTOS partner supporting ARM Cortex-M3 and FM3

Microsemi (previously Actel) RTOS partner supporting ARM Cortex-M3

Atollic Partner

IAR Partner

Keil ARM Partner

Embedded Artists