Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
???
06/05/08 14:40
Read: times


 
#155535 - Leaky bandages
Responding to: ???'s previous message
Michael said:
Often when you have a problem like you are describing you are much better off going back to the source and adjusting the thing that causes the problem instead of trying to cover it over with a leaky bandage.

I agree with that philosophy 110%. However (at least at first), I didn't see that using the /FASTDETECT switch in BOOT.INI fell into the "leaky bandage" category. It seems to be well documented by Microsoft, after all, and not some shady bit of internet folklore. On the other hand, it doesn't seem to work for me. That could mean that it really doesn't work in every situation, or (more likely) simply that I don't fully understand what it's supposed to do.

In the case of your microcontroller project I would suggest that you think about changing your logic about the status dumping logic. You could do many different things but here are three ideas.

1) Add a serial command that can be sent from the PC to the MCU to turn on the status data stream.

2) Add some big divider resistors to an unused A/D input on the MCU and then connect to some outside pin on your project board. Only send the serial status out the serial port when you detect 24V (or whatever you choose) to this outside pin and the A/D gives a reading over some threshold.

3) Add some combination of user control panel switches that when simultaneously pressed (or pressed in some special sequence) will turn on the serial status flow.

In any of these cases it is probably sufficient to just have a turn on command and then let the MCU logic persist in the serial output mode until the next power cycle of the product.

As it turns out, the PC and the microcontroller are controlled independently, so it's possible for the PC to go through a boot cycle while the micro is still running. Probably the best solution is a variation on your #1, where, instead of turning on the status stream forever after, the serial command would just ask for a single packet of status information whenever it was needed. The micro would respond to these requests one by one as they arrived, and remain silent otherwise.

In any case, thanks for the hints.

-- Russ


List of 5 messages in thread
TopicAuthorDate
Problem with automatic mouse detection in Windows            01/01/70 00:00      
   Hmmmm....            01/01/70 00:00      
      Leaky bandages            01/01/70 00:00      
   According to M$..            01/01/70 00:00      
   Problem solved--more or less            01/01/70 00:00      

Back to Subject List