RTOS/TMS320F28069: Possible to use RTOSINT in Non-TI-RTOS or Non Sys-Bios Project?

John,

It might be possible, but you would need to generate the interrupt in software using the INTR assembly instruction (or in-line assembly with C) - see the CPU reference guide SPRU430f page 212.

I hope this helps. If this answers your question, please click the green "Verified Answer" button. Thanks.

- Ken

Hmm, I saw this:

John,

Are you attempting to use CPU Timer 2?

CPU Timer 2 maps to INT14 (RTOSINT).

CPU Timer 2 is reserved for DSP/BIOS. If the application is not using DSP/BIOS, then CPU Timer 2 can be used in the application.

Derrick

And I just wanted to post this:

and this:

just to clear that up.  Maybe more than one person could be confused by this and/or could be true of this subset and not others.

Regards,
John W.

Hello Ken,

So, if I do as instructed on page 212-213, once RTOSINT is asserted - it'll vector here:

//
// RTOSINT_ISR - RTOS interrupt
//
__interrupt void
RTOSINT_ISR(void)
{
//
// Insert ISR Code here
//

//
// Next two lines for debug only to halt the processor here
// Remove after inserting ISR Code
//
__asm (" ESTOP0");
for(;;);
}

?

Does the TI-RTOS/SYSBIOS do something similar?

Thanks!
John W.

John,

Yes, there may have been some confusion in a recalled post. The INT14/Timer2 and RTOSINT are two separate vectors. If you execute the INTR instruction that I pointed out to you, it will vector to the ISR. I am not an expert on TI-RTOS/SYSBIOS, but I would guess that it would vector to the same location and the OS software probably has something written at this location. But for your case, since you are not using TI-RTOS/SYSBIOS nothing should be written at the ISR location but your code.

I hope this helps. If this answers your question, please click the green "Verified Answer" button. Thanks.

- Ken

Hello Ken,

OK - so according to this also:

that it should be fairly easy to use the RTOSINT vector; but unlike the CPU timers, the RTOS timer "construct" doesn't appear to be part of the C2000-Ware release.  I suppose it's easy enough to create a timer that can use this; but I would think there could be specific RTOS Timer hardware registers that implement the timer that don't appear to be exposed.  Since the IRQ priority is higher than what's available for the timers in the PIE, that would appear to be the case.  Otherwise I'm not sure what makes the RTOS INT fire properly; and if this is a forced issue through the INTR instruction; it appears to be a chicken and egg type of problem using that approach.

Thanks,
John W.

John,

Yes, in the beginning I said it was possible, but necessarily wise to use the RTOS INT. It will work using the INTR instruction, but I am not sure of the other ramifications. You will need to experiment to know for sure.

I hope this helps. If this answers your question, please click the green "Verified Answer" button. Thanks.

- Ken

John,

After investigating further, please note that in spru430f on page 54:

"Interrupts DLOGINT and RTOSINT are generated by the emulation logic internal to the CPU"

and on page 55:

"For DLOGINT or RTOSINT, a signal sent by the CPU on-chip analysis logic causes the corresponding flag bit to be set and latched."

Therefore, you must be careful if using (or the functions of) the on-chip analysis logic. So, there could be some risk involved.

I hope this helps. If this answers your question, please click the green "Verified Answer" button. Thanks.

- Ken

Hello Ken,

If I make an example project for the TMS320F28069 with TI-RTOS/SYS-BIOS; will I be able to enable the RTOS INT?

Can you post an example that does this?

Thanks,
John

John,

If I am not mistaken, when using TI-RTOS/SYS-BIOS the interrupts including enabling and disabling are automatically managed. For TI-RTOS/SYS-BIOS questions, it would be best to close this thread and open a new thread directed to the TI-RTOS team,

I hope this helps. If this answers your question, please click the green "Verified Answer" button. Thanks.

- Ken

Ken,

Maybe you are not aware of what the TI-RTOS (now READ-ONLY) currently says:
e2e.ti.com/.../355

It's why I started the original thread in this forum.

So, I won't move or retract this question from this forum unless you know an active;where I can post, TI-RTOS only forum that's on the e2e site.

Thanks,
John

Ken,

This is what the TI-RTOS forum says:

And here's the thread that talks about that forum being read-only:

Regards,
John

Hi John,

FYI, there is still an RTOS team, even if there isn't an RTOS forum you can directly post to.

If, when creating a thread, you check 'I don't have a part number' and then select the tool as 'RTOS', the thread will get routed to the RTOS team regardless of the physical forum you select.

You can also create a new thread and explicitly say that your question is primarily RTOS related and we'll route it to that team.

Hello Devin,

I've already created a thread - this one; which is unanswered.

If that's the process - it's not clear - you guys need to supply explicit info on this.

I will do what you ask -but I will use this thread as my reference; and I will post a link in my "new" thread to this thread addressed to the "ghost" RTOS team.

Thanks,
John W.

Ken,

OK - but I think those instructions should be in big bold letters on the old TI-RTOS forum.

I thought I had been following the instructions that were left there - and that is why, I'll say again, I posted here.

And also, it was my understanding, from that post, anything with RTOS, TI-RTOS, etc. had already been "automatically" routed to the TI-RTOS
team and based on what this says, I thought I was following instructions as best as possible:

"The TI-RTOS forum is now closed to new posts. Since TI-RTOS is now included in the majority of TI's Software Development Kits (SDKs) for MCUs and Processors, the TI-RTOS questions are now routed through the device forums (whose teams produce those SDKs) instead of having a dedicated TI-RTOS forum. This allows for more device-specific answers and will lessen the chance of having to move the thread to another forum.

When you do create a new thread, please specify the device you are using in order to get a list of the relevant device forum destinations, so you can pick the most appropriate one.

Please note that TI-RTOS engineers are still involved in answering threads."

Regards,
John

Ken,

Just one more thing - for the 'c28x family, I don't think this structure is ever getting filled:

ti_sysbios_timers_rti_Timer_DeviceRegs

I was involved in a Hercules project not too long ago; and I was definitely using the RTI facility present in the Hercules family. When I saw the RTOS INT in the 'c28x; I possibly made an incorrect assumption thinking the RTI registers were present there.

At the same time; I have to wonder when TI refers to 'real-time-mode' on this family; what is really happening? Most if not all of the examples are using TIMER2; but TIMER2 is apparently at the lowest CPU priority or it's really close.

Anyway, just wanted to get this in on this thread; if nothing else for reference.

Thanks,
John W.

Hi John,

A little background...

We made a decision last May to make TI-RTOS read-only since TI felt the engineering teams supporting the device forums know enough (or should know enough) about TI-RTOS to handle first level support questions. Internally we can still escalate the threads to a TI-RTOS engineer to handle more in-depth RTOS questions.

And now back to your question...TI-RTOS does not touch or use RTOSINT. It is for emulation and TI-RTOS (right or wrong) does nothing with it.

Todd

Todd,

On the TI wiki:
processors.wiki.ti.com/.../BIOS_for_the_28x

Is this comment:
Important: Significant enhancements were made in SYS/BIOS 6.32 to support 28x devices. We recommend that you use SYS/BIOS 6.32.01 or a later version with 28x devices.

Is there a list that specifies what these enhancements were?

Thanks!
John W.