Search

Technical Discussion Group Forum

This forum is provided for user discussion. While Beacon EmbeddedWorks support staff and engineers participate, Beacon EmbeddedWorks does not guarantee the accuracy of all information within in the Technical Discussion Group (TDG).

The "Articles" forums provide brief Articles written by Beacon EmbeddedWorks engineers that address the most frequently asked technical questions.

To receive email notifications when updates are posted for a Beacon EmbeddedWorks product download, please subscribe to the TDG Forum of interest.

TDG Forum

PrevPrev Go to previous topic
NextNext Go to next topic
Last Post 14 Nov 2005 08:22 AM by  mikea@logicpd.com
Com port issues.
 13 Replies
Sort:
You are not authorized to post a reply.
Author Messages
rmysjr@hotmail.com
New Member
New Member
Posts:


--
07 Nov 2005 07:59 AM
    I have a thread looking into a com port. I had it with a ReadFile, because of this problem I changed to a WaitCommEvent.

    When I am running my application from the eVC++ 4.0 and PB 5.0 there is no problem. But when I run my application stand alone (using Lolo to boot and no debug) this serial port dies.

    This happens when I am doing something else that is not related with this serial port.

    I could not track the problem, because I can make it happen while I am debuging. What I could track was that the WaitCommEvent never returns. The thread does not die.

    Thanks.
    RM
    Anonymous
    Posts:


    --
    07 Nov 2005 11:46 AM
    Hello,

    Can you tell me what BSP you are using, is it Logic's BSP? What are you using for a debug bootstring?

    Thanks,
    rmysjr@hotmail.com
    New Member
    New Member
    Posts:


    --
    07 Nov 2005 11:51 AM
    Yes, I use Logic's BSP.

    exec rtc:rtc_a404_int:dbg_enet:91C111:dbg_enet_base:0x70000000:dbg_enet_irq:0x00000016:share_eth:1

    The serial that dies is not the on that I use to boot or debug.

    Rm
    Anonymous
    Posts:


    --
    07 Nov 2005 11:52 AM
    What bootstring are you using in the scenario where serial doesn't work?
    rmysjr@hotmail.com
    New Member
    New Member
    Posts:


    --
    07 Nov 2005 11:55 AM
    load bin /cf/NK.BIN;exec rtc:rtc_a404_int
    Anonymous
    Posts:


    --
    07 Nov 2005 12:59 PM
    Can you verify that you have added the following to your Windows CE image?

    Core OS > Services > Serial Port Support

    Third Pary > Device Drivers > Serial > lpd_lh7a40x_uart_a40x_50_x_x_x

    Also what COM port are you trying to use? They are mapped out on the LH7A40x as below in the Windows CE Driver:

    A40x com port mappings:
    COM2 - UART1/UARTC
    COM3 - UART2/UARTA - debug serial port
    COM4 - UART 3/UARTB



    Thanks,
    rmysjr@hotmail.com
    New Member
    New Member
    Posts:


    --
    07 Nov 2005 01:08 PM
    Yes. The drivers are installed.

    The port with problem is COM4.
    Anonymous
    Posts:


    --
    07 Nov 2005 02:12 PM
    Hello,

    If you're using the Zoom SDK you'll need to remember that the only UART that is tied to an external peripheral is COM3 - UART2/UARTA - debug serial port. For the others you'll need to hook up the UART to a serial port over the expansion headers on the Zoom SDK Application Board.

    Thanks,
    rmysjr@hotmail.com
    New Member
    New Member
    Posts:


    --
    07 Nov 2005 02:59 PM
    I have a custom board, where I use the 3 internal serial ports and another external uart with 4 extra serial ports.

    I've been using 5 ports and it works.

    About 5 months ago, we detected this problem, but because the problem did not occur in my development setup. I never took the time to fix it.

    Now, I have to fix it.

    My question is: why my board that I boot from PB 5.0 this problem does not occur and on all boards the I boot using the lolo script this problem happens.

    What is different about the kitl connection, that does not let COM4 die? I am supposing it is because of the debug connection, what else it can be? I don't know. I am running out of ideas.

    Thanks.
    Anonymous
    Posts:


    --
    07 Nov 2005 03:08 PM
    Hello,

    A likely reason for this is that there's some library that Windows CE needs that probably isn't included in your workspace or your application. But when you're booted in a debug state CE uses the connection over KITL to actually go get the resources that it needs from the C:\WINCE500 folder.

    Thanks,
    rmysjr@hotmail.com
    New Member
    New Member
    Posts:


    --
    07 Nov 2005 03:14 PM
    But then, COM4 would never work.

    COM4 works. But when I do something (I could not track where and what) in another thread (and the only thing that I know is that I am not acessing COM4 in this other thread at any time) that makes COM4 not respond anymore.

    Thanks
    Raul
    mikea@logicpd.com
    New Member
    New Member
    Posts:


    --
    10 Nov 2005 10:26 AM
    ryoung,
    Please send an email to platformsupport@logicpd.com about this issue. We will then contact you directly.

    Thank You,
    -Mike
    rmysjr@hotmail.com
    New Member
    New Member
    Posts:


    --
    12 Nov 2005 09:19 AM
    I sent and the smtp server return me an error.

    Please, send me another email address.


    Thanks
    mikea@logicpd.com
    New Member
    New Member
    Posts:


    --
    14 Nov 2005 08:22 AM
    ryoung,
    That is the correct email address. Please double check that you used the right address or the other option is to use 'Ask A Question'.
    https://www.logicpd.com/support/askaquestion.php

    You must be registered to use the 'Ask a Question' feature.

    Thanks,
    -Mike
    You are not authorized to post a reply.