CME34M Hardware Manual - RTD Embedded Technologies, Inc.
CME34M Hardware Manual - RTD Embedded Technologies, Inc.
CME34M Hardware Manual - RTD Embedded Technologies, Inc.
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
Common Problems and Solutions<br />
Table 66 lists some of the common problems you may encounter while using your <strong>CME34M</strong> cpuModule, and<br />
suggests possible solutions.<br />
If you are having problems with your cpuModule, review this table before contacting <strong>RTD</strong> Technical Support.<br />
Table 66<br />
Troubleshooting<br />
Problem Cause Solution<br />
cpuModule<br />
“will not boot”<br />
no power or wrong polarity • check for correct power on the PC/104-Plus (PCI) bus connector<br />
incorrect Setup • reboot and press Delete to run Setup<br />
defective or misconnected<br />
device on bus<br />
incorrect PCIe/104 cards<br />
installed (LED is Cyan)<br />
• check for misaligned bus connectors<br />
• remove other cards from stack<br />
• See PCIe/104 Type 2 Compatibility on page 45.<br />
cable connected backwards • verify all cables are connected correctly<br />
cpuModule keeps rebooting problem with power supply • check for correct power on the PC/104-Plus (PCI) bus connector<br />
reset switch is on • check that the reset button is not pushed in<br />
cpuModule will not boot<br />
from particular drive or<br />
device<br />
watchdog timer is not being<br />
serviced quickly enough<br />
• verify that the watchdog timer is being refreshed before it times<br />
out<br />
device not bootable • use sys command on drive or reformat the device using<br />
the /s switch<br />
device not formatted • format drive using /s switch<br />
power not connected to<br />
boot drive<br />
• connect power cable to floppy or hard drive<br />
erratic operation excessive bus loading • reduce number of modules in stack<br />
• remove termination components from bus signals<br />
• remove any power supply bus terminations<br />
power supply noise • examine power supply output with oscilloscope<br />
• glitches below 4.75 VDC will trigger a reset<br />
• add bypass caps<br />
power supply limiting • examine power supply output with oscilloscope<br />
• check for voltage drop below 4.75 VDC when hard drive or floppy<br />
drive starts<br />
• add bypass caps<br />
insufficient cabling through<br />
power connector<br />
• increase wire gauge to connector<br />
• power through bus connectors<br />
temperature too high • add fan, processor heatsink, or other cooling device(s)<br />
• See Thermal Management on page 81<br />
memory address conflict • check for two hardware devices (e.g. Ethernet, SSD, Arcnet,<br />
PCMCIA) trying to use the same memory address<br />
• check for two software devices (e.g. EMM386, PCMCIA drivers,<br />
etc.) trying to use the same memory addresses<br />
• check for hardware and software devices trying to use the same<br />
memory address<br />
• check for an address range shadowed (see Advanced Setup screen)<br />
while in use by another hardware or software device<br />
I/O address conflict • check for another module trying to use I/O addresses reserved for<br />
the cpuModule between 010h and 01Fh<br />
• check for two modules (e.g. dataModules, PCMCIA cards,<br />
Ethernet) trying to use the same I/O addresses<br />
96 <strong>CME34M</strong> cpuModule BDM-610000076 Rev A
Change language