PicoCOM4 boot failure

      PicoCOM4 boot failure

      I have just inherited a product which has a module on it that indicates that it is a "Picocom4 windows CE" device.

      The module is connected like this (I assume that originally a picocom2 was used):



      The problem I have is although there is no drop out on the 3V3 rail during boot and not many pins are connected sometimes the module hangs during boot.

      When I get the module to boot I get the following debug output on COM1:
      NetDCU Config Utility Ready
      Version: 55
      Build from: Nov 30 2012
      Type help for commands

      !>

      Neither the original hardware or software team are available to ask so if anyone has any suggestions or pointers on what may cause the unreliable booting it would be appreciated!

      Cheers

      Matt

      Post was edited 1 time, last by “bbmatt” ().

      Hello,
      i think you should read First Steps Document fs-net.de/de/produkte/picocom/picocom4/. We cannot support such basic questions else this will end in a course of instruction!

      >>"During boot and not many pins are connected sometimes the module hangs during boot"
      << This may be true, each interface have to be terminated correct or disabled from load else it may be interrupt deathless and cause the system hang.

      I recommend you to contact the produc manufactor to clearify details.
      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.
      Thanks for your fast if not slightly curt response.

      We are the manufacturer by the way we have just lost the team who designed in your module. We have been building the product for years and now suddenly have bootup reliability issues on the last 150 boards we purchased from you.
      Sorry,
      but please understand that we cannot start from the beginning of deployment.
      If you read first steps, enabel serial debug output then check where in the boot process the board "hangs". Compare this output with a workíng one. Assume this will lead to the causing driver. Than you can terminate the pins or disable this driver.

      But this i not a real solution, maybe in one or two years, the problem will caused by another driver. So real solution is to terminate all interfaces. Small chnges in the timing may have big effect while pins not terminated. Imagine an open pin floats and causes an interrupts (e.g. CAN or COM Rx)!

      Do you still have a SKIT base baord?
      Do the PicoCOM4s always boot on this board?
      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.