RTC behaviour on reset

I believe that by default, DM365 EVMs do not have the required battery to properly keep RTC information from one session to the next.  You should be able to see a round battery holder between the UART and Ethernet ports on our EVM, which most likely is empty.

Hi Bandini,

I have the same problem, but I have the battery inserted, also power from the adapter remain still connected while reset.

Did the inserting of battery solve the resetting RTC problem upon powerup or reset?

Also mr. Brownell has the same problem:

http://linux.omap.com/pipermail/davinci-linux-open-source/2009-June/014213.html

Also he did not solve it since Jun 2009.

inserting the battery should solve this problem; unfortunately I do not have a battery to verify this with.  If you have a battery inserted and still have problems keeping time across boot-cycles, let me know and I will escalate to our design team..

Dear Juan,

Yes - problem persists also with the battery CR2032 (3V) inserted.

The behavior is the same.

Voltage on the pins TP19 ~ 1.25V, TP18 ~ 1.85V (as expected).

How to repeat:

Commands from MV linux:

# insmod rtc-davinci-dm365.ko

# date 101020202009

Sat Oct 10 20:20:00 UTC 2009

# hwclock -w

# hwclock

Sat Oct 10 20:20:03 UTC 2009 [ok]

Press reset on EVM DM365 or disconnect/connect the power adapter (system is rebooted)

# insmod rtc-davinci-dm365.ko

# hwclock

Sat Jan  1 00:00:07 2000  0.000000 seconds [wrong]

Yes，I　met the same problem.

Why don't have some ways to be presented ?

Although my specific application doesn't require the RTC, I do have batteries in two of my EVMs and can confirm that the boards cannot keep time through power cycle.  The process I used to store the time is similar to the above example.  It didn't seem like there was anything else to configure on the EVM jumper wise in order to enable this functionality.  TI, was this concern ever replicated on your end?  Is there an issue with the EVM design?  I too used a 3V lithium battery, is that sufficient?  It would be great to know if the reference design had an issue as I have based most of my uP setup on the DM365 EVM schematics.

Thanks!

Kevin

Apologies for the delayed response, I thought I had answered this already but this appears to be a different thread, please see http://e2e.ti.com/support/dsp/davinci_digital_media_processors/dm3x/f/100/p/7586/29936.aspx#29936

I have the same problem!

Same thing is happening with MSP430F5418. Could be problem with the chip. 

dehui lin said:

I have the same problem!

Is this also on DM365?  have you read the following thread (reposting for you convenience)

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/dm3x/f/100/p/7586/29936.aspx#29936

Harinath Babu said:

Same thing is happening with MSP430F5418. Could be problem with the chip. 

The issue here is not the MSP430 on DM365 EVM but rather the hardware changes suggested at the thread

http://e2e.ti.com/support/dsp/davinci_digital_media_processors/dm3x/f/100/p/7586/29936.aspx#29936

Also please not that as suggested in the above thread, the software support is not quite there yet either.