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

c6657 Gauss - Crash issue

Harikrishna Vuppaladhadiam
Expert 1855 points

Other Parts Discussed in Thread: SYSBIOS

Hi

   I have my programs working fine with RTSC Configuration without SYSBIOS - BIOS selection library type as " Instrumented". 

The moment I change it to "Custom" Crashes keep occuring at different stages of the code. 

The reason why we have to use "Custom" is that I am enabling to use MAILBOX. Mailbox uses Semaphores. Under Semaphores I need to select Basic Options Select "Support Events" as Mailbox needs this setting. Because of this change my code keeps crashing. 

Is there a way to resolve this issue. 

Regards,

HAri

[C66xx_0] 0x0
A8=0x9 A9=0x0
A10=0x0 A11=0x0
A12=0x0 A13=0x0
A14=0x0 A15=0x0
A16=0x0 A17=0x90
A18=0x90 A19=0x0
A20=0x810a43c6 A21=0x810a43cc
A22=0x810a4436 A23=0x810a4438
A24=0x184 A25=0x28
A26=0x810a4424 A27=0x810a442e
A28=0x810a43ee A29=0x810a4342
A30=0x810cd364 A3[C66xx_0] 1=0x3fff
B0=0x0 B1=0x0
B2=0x8102598a B3=0x80000000
B4=0x0 B5=0x0
B6=0x0 B7=0x90
B8=0x0 B9=0x810a43f2
B10=0x0 B11=0x0
B12=0x0 B13=0x0
B14=0x810899f8 B15=0x81138e00
B16=0x810a443a B17=0xfe
B18=0x18e B19=0x180
B20=0x1 B21=0x8109a2d4
B22=0x102 B23=0x58c
B24=0x[C66xx_0] 14a B25=0xae
B26=0x148 B27=0xac
B28=0x13e B29=0x134
B30=0xb2 B31=0xce
NTSR=0xf
ITSR=0x1800f
IRP=0x81066840
SSR=0x0
AMR=0x0
RILC=0x0
ILC=0x0
Exception at 0x81066840
EFR=0x40000000 NRP=0x81066840
UMC Exception MPFAR=0x0 MPFSR=0x110
Supervisor Write violation[C66xx_0] , Fault ID=0x1
ti.sysbios.family.c64p.Exception: line 248: E_exceptionMin: pc = 0x8104c8a6, sp = 0x81138e00.
To see more exception detail, use ROV or set 'ti.sysbios.family.c64p.Exception.enablePrint = [C66xx_0] true;'
xdc.runtime.Error.raise: terminating execution

  • 0
    TI__Mastermind 21645 points

    Hi Hari,

    What version of BIOS and XDC are you using ?

    From the exception dump it looks like the access permissions that are set in the MemoryProtect module are being violated. You may want to check your MemoryProtect module settings. To know access to which address is causing the exception, you could start by adding a breakpoint before the exception address (highlighted below) and then single stepping through the code.

    Harikrishna Vuppaladhadiam said:

    Exception at 0x81066840

    EFR=0x40000000 NRP=0x81066840
    UMC Exception MPFAR=0x0 MPFSR=0x110
    Supervisor Write violation[C66xx_0] , Fault ID=0x1
    ti.sysbios.family.c64p.Exception: line 248: E_exceptionMin: pc = 0x8104c8a6, sp = 0x81138e00.
    To see more exception detail, use ROV or set 'ti.sysbios.family.c64p.Exception.enablePrint = [C66xx_0] true;'
    xdc.runtime.Error.raise: terminating execution

    Best,

    Ashish

  • 0 in reply to Ashish Kapania
    Expert 1855 points

    As I said I just changed the cfg file. Without modifying BIOS to "CUSTOM mode" keeping it in "Instrumented" Mode, it works (in Instrumented mode). The only change from working to non-working is changing the BIOS type from Instrumented to Custom Mode. 

    Crash:

    The modules:

  • 0 in reply to Harikrishna Vuppaladhadiam
    TI__Mastermind 21645 points

    Hari,

    When you build BIOS with "Instrumented" libType, due to a bug, you do not get a memory protect (MPC) exception even if one was suppose to happen. If you build with "custom" libType then the exception starts occurring. What I am trying to say is that some problem might have always existed in the code but was not visible because the access violation exceptions were not getting generated.

    You need to debug this with the help of the exception address. This will help determine the cause of the exception.

    Best,

    Ashish

  • 0 in reply to Ashish Kapania
    Expert 1855 points

    Ashish,

      This information is useful. Thanks for the explanation. So far we tested our voip code based on Instrumented mode. We will debug now with Custom mode to see if there are any memory issues. 

    Can you forward any link where these bugs are explained for SYSBIOS. 

    Regards,

    Hari

  • 0 in reply to Harikrishna Vuppaladhadiam
    TI__Mastermind 21645 points

    Here's the link to the bug:

    https://cqweb.ext.ti.com/cqweb/main?command=GenerateMainFrame&service=CQ&schema=SDO-Web&contextid=SDOWP&entityID=SDOCM00099563&entityDefName=IncidentReport&username=readonly&password=readonly

    Best,

    Ashish