I imagine you could you could use the "w" command to drive the signal but I think lolo will keep setting it back. at reset the pin is tri-stated so maybe there's a way to put it back in that mode and keep lolo from using it as an output but not sure.

Check section 2.11 of the hw guide:

http://www.logicpd.com/do..._MCF5329_HW_Spec.pdf

pmcelwee13,
I am pretty sure Lolo reads the STATUS_1,2 state then inverts them to create the toggling LEDs.

One way you could prevent this is use a lolo script at boot up to temporarily disable the GPO latch until your software begins running. This is done by driving the "MFP9 - TIN3/TOUT3" (CPU TIN3/TOUT3 pin) signal high.

Once your software starts up you can initialize the latch to your prefered state, then drive "MFP9 - TIN3/TOUT3" low again.

-K

Hey, sorry for not getting back earlier. It turns out that we can't use the GPIO latch for both output and input because of opto - isolators (spelling?) and such. So we moved the output GPIOs to PWM outputs that are driven at 100 % although I supposed we could vary them to get different buzzer / LED intensities.

Edit: I guess I have a couple different user names on here?!?! Man its been a while.