• State Resolved
  • Locked Locked
  • Replies 3 replies
  • Subscribers 98 subscribers
  • Views 1640 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.

Asserts in SYS/BIOS

Kishor Jm
Prodigy 585 points


I would like to know the new asserts introduced in bios_6_34_03_19 , ipc_1_25_01_09, xdctools_3_24_03_33 compared to

versions bios_6_33_05_46, ipc_1_24_03_32 and xdctools_3_23_03_53

We found a Semaphore overflow count assert with the new version in our application. We want to know if any such new checks are introduced.

One more problem was the code causing the assert was not easily found by connecting to the target using CCS even in Debug build.  DSP was going to abort and we had to trace back using breakpoints.

One more question is by using the method mentioned in Section 8.7.2 Configuring Diagnostics from Bios_User_Guide, we can disable these assert.  Is it right?

-Kishor

  • 0
    TI__Mastermind 20480 points

    HI Kishor,

    An additional Assert_isTrue() was added in Semaphore_post(). It will assert that the internal counter of a counting semaphore hasn't overflowed (wrapped around back to 0). You may be posting many more semaphores than what you are pending.

    What did the error look like and what BIOS library type did you use?

    If you are using BIOS.LibType_NonInstrumented, then you won't get the Asserts. See section 2.3.5 in the User's Guide. Section 8.7.2 that you've mentioned will only work when using an instrumented or custom libtype.

  • 0 in reply to Tom Kopriva
    TI__Prodigy 585 points

    Hi Tom,

    I was not seting the BIOS.LibType in out cfg file. When I checked with XGCONF it seems to take Instrumented Library by default.

    I'm running on TI811X platform.

    The error was DSP abort. Nothing is displayed in CCS console.

    With NonInstrumented lib asserts are not raised and with Instrumented and Custom Libtype asserts are disabled if I use sec 8.7.2 procedure.

    So sec 8.7.2 procedure would be sufficient to disable asserts. Is it right?

    I want to confirm if the Semaphore count overflow is the only additional assert in BIOS and IPC versions I mentioned?

    -Kishor

  • 0 in reply to Kishor Jm
    TI__Mastermind 20480 points

    Kishor,

    You can disable "Assert_isTrue()" function calls by referring to Section 8.7.2. Disabling these asserts won't disable the abort on the DSP.

    Are you able to use ROV to see if it detects a problem? If you're not getting anything in the console makes me wonder if you can even get to main().