Hi
We had the problem too.
It's seems to caused by the mBed hardware to come up with I/O set to 1 outputs (without a chance to set a default value). Normally you would expect I/O to be tri-state or input with you can pull with a resistor. This is very unusual for I/O ports and CPU's.
The only way around it was to invert all outputs driving external hardware. So in out code the 1 output remains (and is inverted to be a 0 for the attached hardware) after our code starts. So no workaround, just cope with this quirk in the design of your hardware.
It also seems to be related to the (USB) power being applied so we also had to add a powered hub to keep the mBed powered when the PC is not attached.
regards
wvd_vegt
Has anyone observed this behaviour - at startup or straight after reset, any pins attached to a DigitalOut object will pulse on for a short time, even if the object is not referenced anywhere in the program. This is really undesirable for some equipment/devices attached to those output pins.
Any ideas on how to avoid this from happening?
regards, Adrian.