| ??? 06/15/05 10:49 Read: times Msg Score: +1 +1 Informative |
#95003 - Testing I2C Driver Code Responding to: ???'s previous message |
It can be extremely difficult to debug hardware level drivers without the use of an oscilloscope. I can say from real world experience that there have been many many times that I have written code that I thought should work for some type of I/O only to find during the test / debug phase that it did not work at all. After some times of fighting this senario I can now say that I always have an oscilloscope connected to the interface lines and to a spare port bit whenever I am making software for I/O routines.
Michael Karas |
| Topic | Author | Date |
| I2C Sequential access | 01/01/70 00:00 | |
| write cycle time | 01/01/70 00:00 | |
| Nothing wrong here. | 01/01/70 00:00 | |
| Testing I2C Driver Code | 01/01/70 00:00 | |
| it is from my datasheet! | 01/01/70 00:00 | |
| Many Manufacturers | 01/01/70 00:00 | |
| two things | 01/01/70 00:00 | |
| What are you getting back? | 01/01/70 00:00 | |
| Problem is solved! | 01/01/70 00:00 | |
programming end polling | 01/01/70 00:00 |