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

BIOS_Start() does not start my tasks

Nivedita Velagaleti
Prodigy 100 points

Other Parts Discussed in Thread: SYSBIOS

I created two tasks from the main method and the handles returned a non-NULL value. The execution is at BIOS_Start and none of the task functions have been called. I have added System_printf functions in both of the task functions and I don't think the tasks are scheduled. How do I check if the tasks are scheduled and called?

I used Task_create() method to create two tasks.

  • 0
    TI__Guru* 85400 points
    Moving to TI-RTOS forum

    Regards,
    Gigi Joseph.
  • 0 in reply to Joseph Gigi
    TI__Genius 12025 points

    Nivedita,

    Are you using CCS? Are you single-stepping? You have to set a breakpoint in the task function and then let CCS run. Or are you debugging some other way. Please provide more details.

    Also, what device and software versions are you using?

    ~Ramsey

  • 0 in reply to Ramsey
    Prodigy 100 points
    Hey,
    I am using an RTSC application. I don't think it is the problem with task function. I feel I can't execute any Simplelink api such as sl_start() or sl_wlanconnect() from an RTSC application. The same works perfectly fine in CCS application. It sounds absurd but I am trying to figure out what could be the difference between RTSC and CCS. Everytime I try to execute the code, it gets stuck in the api call and debugging into the api call reveals it is randomly accessing different memory location in the file instead of executing the api method.
    If executed in a task it dumps this in the console.
    ti.sysbios.family.arm.m3.Hwi: line 1095: E_hardFault: FORCED
    ti.sysbios.family.arm.m3.Hwi: line 1172: E_busFault: PRECISERR: Immediate Bus Fault, exact addr known, address: 4f4002f2
    Exception occurred in background thread at PC = 0x2000f2b4.
    Core 0: Exception occurred in ThreadType_Task.
    Task name: {unknown-instance-name}, handle: 0x20011c88.
    Task stack base: 0x2000f3a0.
    Task stack size: 0x800.
    R0 = 0x4f4002f2 R8 = 0x00000000
    R1 = 0x2000f920 R9 = 0x00000400
    R2 = 0x00000004 R10 = 0xffffffff
    R3 = 0x00000003 R11 = 0xffffffff
    R4 = 0x00000004 R12 = 0x00000000
    R5 = 0x20016228 SP(R13) = 0x2000f918
    R6 = 0x000090fd LR(R14) = 0x2000b7f3
    R7 = 0x00000004 PC(R15) = 0x2000f2b4
    PSR = 0x01000000
    ICSR = 0x0400f803
    MMFSR = 0x00
    BFSR = 0x82
    UFSR = 0x0000
    HFSR = 0x40000000
    DFSR = 0x0000000b
    MMAR = 0x4f4002f2
    BFAR = 0x4f4002f2
    AFSR = 0x00000000
    Terminating execution...
  • 0 in reply to Nivedita Velagaleti
    TI__Genius 12025 points

    Nivedita,

    I don't understand your reference to a CCS application vs. a RTSC application. By CCS, do you mean a CCS project? And by RTSC do you mean building from the command line with Make?

    Or are you using a CCS project in both cases, but one has the RTSC support and the other does not?

    Which device are your working on and what software products are you using. Please specify versions as well.

    ~Ramsey