You did not post your project, and my crystal ball is still in repair, so I will take an educated guess.
RtcInt is an ISR that you did add to the RTC? If so, then yes it will be called whenever the interrupt gets triggered. There is no need to duplicate this functionality in main (but you should not do long-running stuff in the ISR, such as writing to the LCD - better just set a (volatile) flag which main can then read and react on).
No, there is no automatic way to set the time from the PC, and AFAIK even the Ardiuno doesn't have that (esp. when not connected to a PC...). But you can add this by yourself quite easily via the UART.
Thanks for the reply.
Its the RtcDesign Example file for the 5LP, that comes with PSoC v4 , not any code I have written , was just amending the code to change the layout of the lcd output when I found the problem as above.
Perhaps that Example code has just been quickly put together.....
As you say, its not good practice to use lengthy lcd routines in the ISR , though wondered with these faster chips if that was still a problem vs my old 8 bit Pic chips with Assembly code !
Welcome in the forum, George.
As hli says, it is easier for us to help you when you post your complete project. With the help of the IDE everything is easier to follow and to check.
Concerning lengthy interrupt handlers: I have seen issues where just a character was sent via USB stalling the system. Usually you are not aware of delay function calls within the generated code, so hli's suggestion makes sense. Of course the code might be a bit longer, as long as you are able to overview all the consequences.
Date is set for 12/31/2007 and time is set for 22:59:22 so you will need to change this to the correct date and time.
Its not the MCU speed thats the problem here - the LCD will just take a while for each characters, and your code needs to wait for that to finish.