• State
  • Locked Locked
  • Replies 5 replies
  • Subscribers 99 subscribers
  • Views 1066 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

TMDXEVM5515: CSL_PowerManagement_IDLE3_Example doesn't work correctly

Yang Xiao32
Intellectual 560 points

Part Number: TMDXEVM5515

Hello,

I am trying to run the example code of C:\ti\c55_lp\c55_csl_3.07\ccs_v6.x_examples\power\CSL_PowerManagement_IDLE3_Example on EVM5515 board. But I found the problem is after the CPU set to IDLE state, it cannot be waken up by alarm and give the print "Current Time and Date is : ******" and "CSL RTC TESTS COMPLETED". Now the print while I was running thru JTAG debug is as below:

CSL RTC TESTS

This test demonstrates RTC ALARM interrupt generation capability
RTC_setCallback Successful
RTC_config Successful
RTC_getConfig Successful
RTC_setTime Successful
RTC_setDate Successful
RTC_setAlarm Successful
RTC_eventEnable for ALARM EVENT Successful

Starting the RTC..alarm will be produced on 12:12:30:0512, 3-12-13 ....Have a sleep

Current Time and Date is : 12:12:12:0122, 03-12-13

Disabling USB Clk domain

Disabling Clk to all preipherals except Sysclk to clk generator

RTC Alarm Interrupt has been generated

Sysclk and PLL turned back ON

  • 0
    TI__Guru**** 161600 points
    Hi,

    I've notified the software team. Their feedback will be posted here.

    Best Regards,
    Yordan
  • 0 in reply to Yordan Kovachev
    Intellectual 560 points
    hello,

    any feedback?
  • 0 in reply to Yang Xiao32
    TI__Guru**** 161600 points
    No, I don't have a feedback yet. I've sent a reminder.

    Best Regards,
    Yordan
  • 0 in reply to Yang Xiao32
    TI__Mastermind 30365 points
    Yang,
    When you are running the first time are you doing it off the SD card? If so, then you will notice the difference in behavior compared to the JTAG test might be the GEL file run on the core. Is that correct?

    It seems as thought there is something with the bootloader that needs to be configured to get the RTC in a proper state.

    Lali
  • 0 in reply to Lalindra Jayatilleke
    Intellectual 560 points

    Hi Lali,

    Thanks for your reply. I have 2 questions:

    1, what do you mean 'off the SD card'? I did it several times and it showed the same results. according to this test description, this test configures RTC for generating an alarm 8s after it's started, during which period the system is put into IDLE3 state. The subsequent RTC alarm interrupt should bring the CPU out of the IDLE3 state and resume execution from where it was before it idled out. But the problem is the interrupt didn't bring CPU out and resume execution. I don't know why it is connected to SD card?

    2, I ran it with CCSV6 thru JTAG. I didn't boot up from flash. So I am not sure what is the bootloader in this circumstance. Besides, RTC worked fine in my opinion as the alarm showing its interruption in the correct time. But the CPU seems doesn't wake up. is it possible because the CPU will reset the board after it getting out of IDLE state? If so, we need to run this demo from flash not from JTAG debug.