I want to use RTC as sys clock, but also Middleware LPDS

Part Number:CC3200SDK

Hello, Friends,

I began this question at this link:

Also good ideas from this link:

And this post: e2e.ti.com/.../425801

I think I found that my solution would be to use RTC as my Clock.TimerProxy like this in app.cfg:

/* Required if timer/clock/timestamp is being used */
var Timer = xdc.useModule('ti.sysbios.hal.Timer');
//Timer.TimerProxy = xdc.useModule('ti.sysbios.family.arm.lm4.Timer');
Timer.TimerProxy = xdc.useModule('ti.sysbios.family.arm.m3.Timer');

var Timestamp = xdc.useModule('xdc.runtime.Timestamp');
//Timestamp.SupportProxy = xdc.useModule('ti.sysbios.family.arm.lm4.TimestampProvider');
//Timestamp.SupportProxy = xdc.useModule('ti.sysbios.family.arm.m3.TimestampProvider');
Timestamp.SupportProxy = xdc.useModule('ti.sysbios.family.arm.cc32xx.TimestampProvider');

//Clock.TimerProxy = xdc.useModule('ti.sysbios.family.arm.m3.Timer');
Clock.TimerProxy = xdc.useModule('ti.sysbios.family.arm.cc32xx.Timer');
Clock.tickMode = Clock.TickMode_DYNAMIC;

I am also using RTC as a Timestamper, which works the way I want across LPDS periods.

My problem occurs when I set the Clock.TimerProxy and Clock.tickMode as in the app.cfg.  Middleware lp3p0_board.c/platform_init() fails when attempting to register the INT_PRCM ISR with an "Invalid free" error message.  By selecting the Clock in this way, does TI-RTOS configure a static HWI? Then Middleware tries to delete the HWI object in order to replace it with its own, but a static HWI Object can't be deleted?

I sure like the idea of using RTC as the system clock, especially with the promise of the TickMode_DYNAMIC that unnecessary clock tick interrupts will be avoided.

Is there a way to get Middleware to play well with this use of Clock module?