This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

[DM365-IPNC] RTC was alway reset

HI all,

   I found that the RTC was alway reset. When reset the IPNC board, the RTC will run from year 2000.

# hwclock
Sat Jan  1 00:00:02 2000  0.000000 seconds
# hwclock
Sat Jan  1 00:00:05 2000  0.000000 seconds

BR
    Terry K.G

  • Terry, if you have't battery on device this is a normal.
  • HI Kirill,

      My board had battery yet.But I found 2 strange issues about R93 on mainboard.Here are the SCH & PCB copied from Appro:

      A.if Connecting R93, it will display "RTC time out" when loading kernel.
    rtc_davinci_dm365 rtc_davinci_dm365.0: rtc core: registered rtc_davinci_dm365 as rtc0
    rtc wait time out !!!!!
    rtc wait time out !!!!!
    rtc wait time out !!!!!
    rtc wait time out !!!!!
    rtc wait time out !!!!!
    rtc wait time out !!!!!
    rtc wait time out !!!!!
    Advanced Linux Sound Architecture Driver Version 1.0.12rc1 (Thu Jun 22 13:55:50 2006 UTC).

     B. If disconnect R93. The RTC will reset when power on.

    # hwclock
    Sat Jan  1 00:00:02 2000  0.000000 seconds
    # hwclock
    Sat Jan  1 00:00:05 2000  0.000000 seconds

    BTW, can you help my other post--How to flash ubl+uboot to IPNC from Serial ?

    BR
         Terry K.G

  • Hi

    Me too have the same issue, we aslo using appro refference design, when i put the R93 i am getting the "rtc wait time out !!!!!" due to the RTC Reset fail.. in the u-boot.

    Can u put some light into this issue, Is this a silicon bug with DM365

     

    Regrads

    Joseph George

  • Dear Terry,

    The status A is correct. Please turn off the IPNC about one hour and then reset the IPNC later, the messages "rtc wait time out !!!!!" will bypass. Of course, you can short the circuit about capacitor to discharge electricity directly.

    Best Regards,

    Appro Support Team

  • George,

    Thanks for picthing in and helping to answer on this pending topic.

     

    Regards,

    Anshuman

  • Hi

    Me too have the same issue, we aslo using appro refference design, (dm368)

    Please let me know if a solution for this exists

    Regrads

    jun-sic

    choichoro@yahoo.co.kr

  • Hi ?

    not be able to use the RTC dm365's are considered, connect an external RTC chip. And Replacing the RTC chip DS1307 rtc-ds1307.ko driver module from the kernel creates raised, but no there is no response. board-dm365-ipnc.c files at i2c/rtc set ds1307 need to register? Please help me.

  • Look like you didn't get any progress for the RTC issue on DM368? Now I am also response for that problem ... hope for some more useful information.

  • Hi,

    The platform is DM365 and DM368 IPNC.  It display "RTC reset fail"  in UBL  and "rtc wait time out !!!!!"  in loading kernel.

    I found that  RTC PRTCIF_CTRL Register's  BUSY bit  was always  '1', even if  I  reset IPNC or power off.  If  turn off the IPNC about  half one hour or short the circuit about capacitor, the message will bypass. 

    I don't  konw what is the actual cause fro this issue.  I will sell the IPNC product to my customers. When the RTC fail,  customers can't  turn off the IPNC about  half one hour or short the circuit.

    Can you tell me what is the actual cause and how to solve the problem ?

     Is this a silicon bug with DM365 or DM368 ?

    Thanks




  •   Hi, I'm Phil Yi, Dallas base Apps, and I'm currently working on this device. To help me finding the root cause, may I have your IPNC schematics and board file sending to pyi@ti.com?

    Thanks!

    Phil Yi

  • I have encountered the same problem, not solved untill now

  • Hi Sir

    Does anyone have update for this issue ? we also meet the same issue.

    we follow 3rd-party reference design and sometimes met boot issue. the log message is show as below

    ===================================================================================
    Trying to register davinci display video device.
    layer=c8181600,layer->video_dev=c8181760
    davinci_init:DaVinci V4L2 Display Driver V1.0 loaded
    i2c /dev entries driver
    nand_davinci nand_davinci.0: Using 4-bit hardware ECC
    NAND device: Manufacturer ID: 0xec, Chip ID: 0xf1 (Samsung NAND 128MiB 3,3V 8-b
    t)
    Creating 6 MTD partitions on "nand_davinci.0":
    0x00000000-0x00240000 : "bootloader"
    0x00240000-0x00260000 : "params"
    0x00500000-0x00700000 : "kernel"
    0x00700000-0x03000000 : "filesystem"
    0x03000000-0x03200000 : "data1"
    0x03200000-0x03400000 : "data2"
    nand_davinci nand_davinci.0: hardware revision: 2.3
    rtc_davinci_dm365 rtc_davinci_dm365.0: rtc intf: proc
    rtc_davinci_dm365 rtc_davinci_dm365.0: rtc intf: dev (254:0)
    rtc_davinci_dm365 rtc_davinci_dm365.0: rtc core: registered rtc_davinci_dm365 as rtc0


    thanks for reply.

    BR
    Yimin
  • Hi Sir

    after checking the Dm36x reference design of APPRO , we found it does not follow External control sequence for RTC  Normal mode?

    Does any one have any common or has fixed RTC reset issue ? 

    thanks for reply.

    BR

    Yimin