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.

TDA4VM: C7x data abort

Part Number: TDA4VM
Other Parts Discussed in Thread: SYSBIOS

hi,

    After c7x runs for a long time, there is no response. After XDS110 is connected, page_fault is generated. We can see the registers by XDS110.

    How can we debug Page Fault according to c7x registers? Is there any document?

page_fault is below in psdk_rtos_auto_j7_06_02_00_21/bios_6_76_03_01/packages/ti/sysbios/family/c7x/Hwi_disp_always.s71:

.align 0x200
page_fault:
     b.b1 $PCR_OFFSET(page_fault)

    thanks!

  • Can  you please provide more details?

    1. What application are you trying to run?

    2. Are you running in the context of a task?

    3. Is your task doing a memcpy?

    4. Is the task getting interrupted frequently?

    If your answer to questions 2, 3 and 4 is yes, then you are hitting a bug in SYSBIOS (6_76_03_01) which is part of psdk_rtos_auto_j7_06_02_00_21

    We have a fix coming up in the next SDK release targeted in June. 

    As a workaround you can try disabling interrupts when you enter your task and re-enable when you exit the task.

    Regards,
    Shyam

  • Shyam,

    c7x:

    2. Are you running in the context of a task?  

        yes

    3. Is your task doing a memcpy?

        yes, We know the problem with memcpy, so we rewrote memcpy with a simple for loop.

    4. Is the task getting interrupted frequently?

     yes, Very frequent ipc interrupts.

    The problem occurs about once every 10 hours.

    In the datasheet <<c7x_cpu_mma.pdf>> 1.18.4.8.3, page fault is related to Speculative Load Instructions.

    IEAR(Internal Exception Address Register) : 0xFFFFFFFFFFFFFFFC

    so, Is this the same kind of problem as memcpy?

    Regards,

    cui

  • Cui,

    Yes this is the same issue. Please expect a fix by SDK 7.0 coming out this month.

    Regards,
    Shyam

  • Cui,

    We have fixed this issue in the upcoming SDK 7.0 release. Can I close this thread for now? You can reopen it or open another one if you face the same issue again using SDK 7.0

    Regards,
    Shyam

  • Hi Cui,

    Please watch the attached video in the zip file. That has all the details on the changes
    that were made in 7.0 to fix the issue. The changes should be backported to 6.02.

    https://e2e.ti.com/cfs-file/__key/communityserver-discussions-components-files/791/c7x_2D00_data_2D00_abort_2D00_fix_2D00_changes.7z
    Best Regards,
    Keerthy