PicoCOM4 COM 1 and 2

    Hi


    We've been noticing some odd behaviour when trying to connect to the COM ports on the PicoCOM4.


    When trying to connect to COM2, the Tx activity appears to be on the COM1 port.
    When trying to connect to COM1, if serial debug is set to 'NO' in Eboot, when trying to connect on COM1 we get the error that COM1 is an invalid port, or if serial debug is set to 'YES' in Eboot, I get the error 'IOException, could not evaluate expression".


    So currently, we are unable to connect to a device connected to either COM1 or COM2.


    We have installed the latest Kernal onto the device (released 30/03/11).


    Any help would be greatly appreciated


    Will Stockton
    Intellident UK Ltd

    Quote from "wjstockton"

    When trying to connect to COM2, the Tx activity appears to be on the COM1 port.


    Could you please specify this observation in more detail?
    There only is a known timing problem with COM2 that causes that serial port sometimes can not be opened (-> PicoCom4:COM port problem!).


    Quote from "wjstockton"


    When trying to connect to COM1, if serial debug is set to 'NO' in Eboot, when trying to connect on COM1 we get the error that COM1 is an invalid port, or if serial debug is set to 'YES' in Eboot, I get the error 'IOException, could not evaluate expression".


    When serial debug is disabled in Eboot ('NO') the ndcucfg utility will by default run on this serial port. Hence you will need to disable ndcucfg to be able to use COM1 in your own application. To do this you should remove ndcucfg from init key in registry [HKLM\Init].

    Software developer, F&S Elektronik Systeme GmbH
    As this is an international forum, please try to post in English.
    Da dies ein internationales Forum ist, bitten wir darum, Beiträge möglichst in Englisch zu verfassen.

    Good morning,


    Thank you for your prompt reply on Monday, we have now solved the issue.


    We have built our own hardware which incorporates the PicoCOM4, and your hardware outputs are are documented as COM0 and COM1 (as per standard convention), but where as traditionally these are then translated to being COM0 = COM1, and COM1 = COM2, you have instead made COM1 = COM1, and COM0 = COM2. Hence, what we thought was COM1 was actually COM2, and vice versa. (We are somewhat perplexed as to why you have decided to go against convention in doing this?).


    But thank you for your help, we have now disabled the debug output on COM1 and can connect to a device on this port.


    Will Stockton
    Intellident UK Ltd