• State
  • Locked Locked
  • Replies 4 replies
  • Subscribers 83 subscribers
  • Views 202 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.

TMS320F28069: SYS/BIOS issue

Ethan Tian
Intellectual 1872 points
Part Number: TMS320F28069


Tool/software:

Hi experts

We have encountered some issues recently when using SYS/BIOS, mainly manifested as tasks failing to run and abnormal Mailbox status. The information obtained from the ROV window of CCS is as follows:

The scripts for creating tasks and mailboxes in the cfg file are as follows:

var phyTxTaskParams = new Task.Params();
phyTxTaskParams.priority = 13;
phyTxTaskParams.stackSize = 1024;
var phyTxTask = Task.create("&PHY_tx_thread", phyTxTaskParams);
 
var mbxPhyTxQueParams = new Mailbox.Params();
mbxPhyTxQueParams.instance.name = "PHY_TX_QUE";
Program.global.PHY_TX_QUE = Mailbox.create(1, 2, mbxPhyTxQueParams);

Tool versions:
CCS: 12.8.1.00005
XDCtools: 3.25.6.96
SYS/BIOS: 6.35.1.29

Hwi, Swi, and Timer are running normally, but the internal scheduling status of the Task is abnormal.

We have initially ruled out issues with stack usage and memory overflow, and suspect that version compatibility or interface differences may be the cause. We hope you can help us further analyze this. Thank you!

  • 0
    TI__Intellectual 1872 points

    Hi experts

    Any update about this issue?

    Further debugging revealed that an error occurred during the internal scheduling of the OS

    The value of tskKey is derived from Task_module -> locked

  • 0 in reply to Ethan Tian
    TI__Intellectual 1872 points

    Hi Whitney

    Could you please help on this issue?

  • 0 in reply to Ethan Tian
    TI__Guru 54195 points

    Hi Ethan,

    Thanks for your patience. We no longer support SYS/BIOS, so I'm not sure how much help I can be here. Mailbox is not one of the modules I'm familiar with unfortunately.

    You mentioned a suspected compatibility issue--was there a reason for that? Was there a previous version of this code that was working before changing versions? The bios_6_35_01_29 release notes say "XDCtools 3.24.06.63 or later," so that should be okay. 

    Whitney

  • 0 in reply to Whitney Dewey
    Prodigy 10 points

    When the task scheduler is in a locked state and there are no pending messages in the Mailbox, executing a pend operation will inevitably cause both the task and Mailbox to enter an exception state.

    We suspect that during certain kernel processing flows, the task scheduler becomes locked but fails to unlock in a timely manner.