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.

RTOS/CC2650: Task never executes after BIOS_start() is called

Part Number: CC2650
Other Parts Discussed in Thread: SYSBIOS, CC2640

Tool/software: TI-RTOS

I have 2 seemingly identical custom boards exhibiting different symptoms.

One board, I'll call the working board, successfully calls my application task.

The other board, I'll call the failing board, never calls my application task.

The code calls 2 create task functions in main, just before it calls BIOS_start().

Both boards run the main() function to it's conclusion, where it calls BIOS_start().

But one of them (working board) will break on my application task and the other (failing board) never breaks on the application task.

What can I do to debug this issue?

I know this might be a hardware difference on the board, however, I would like to debug it in the emulator (debugger).

I've looked over both boards, and they seem identical.

Thanks,

John 

  • There was 1 reply to this message posted yesterday.

    Where did it go?

    Did the admin remove it?

    John

  • More...
    After running to BIOS_start(), then hitting go, the failing board runs but never breaks on the application task.
    Then, after hitting break manually, the TI_RTOS -> BIOS -> Scan for Errors reveals and exception as follows:
    mod: ti.sysbios.family.arm.m3.Hwi
    tab: Module
    inst: N/A
    field: exception
    message: An exception has occurred!
    I then refer to document SWRU393_CC2640_BLE_Software_Developmer's_Guide.pdf (Literature Number: SWRU393C, October 2010-Revised June 2016) section 9.8 entitled 'Deciphering CPU Exceptions'
    At this point the CFSR 'UNDEFINED INSTRUCTION' bit is 1 (all other bits are zero).
    Section 9.8.2 refers to the TI-RTOS configuration file, but, it doesn't say where I find this.
    Where do I find the TI-RTOS Configuration file?

    John
  • this was just my case.
    I also faced a similar one a few days ago, and it was solved through increasing allocated size of the corresponding task or PIN_init(BoardGpioInitTable) was called again.

    Ji Won