Yes, I am aware of that. It is because the development board I am using (EasyPic6) hardwires PortB RB0/RB1 to the LCD that the board uses, thus making a conflict with the RB0/RB1 pins that are used by my 18F4550 MCU for the I2C interface to the DS1337. That is why I am commenting out all of the LCD related code in this test version, which unfortunately makes it difficult to troubleshoot the DS1337 clock operations without being able to see the outpus on the LCD. I am therefore using my oscilloscope to check the DS1337 pins during ops as my only way to troubleshoot...awkward!
I have another LCD on order (two weeks delivery from Bulgaria) that will permit me to connect it as an external LCD to the EasyPic6 that will resolve this pin conflict, but in mean time I am still trying to troubleshoot code and get the clock working. Any suggestions how to troubleshoot without LCD??
One thing I am wondering....I have the DS1337 circuit with pullup resistors and capacitor installed on an Archer Universal Breadboard with wire connections to the EasyPic6 for the I2C interface and the ALarm1 input....would this be possible cause for the clock not working due to extra capacitance from wiring/breadboard hookup? I wanted to get code working before reducing everything to an integrated PCB.
I will try your contrl suggestion. Thanks for advice!
Bookmarks