• Locked Locked
  • Replies 2 replies
  • Subscribers 99 subscribers
  • Views 1809 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.

Data Abort occurs when you use the SYS / BIOS.

M.H
Genius 5960 points
Other Parts Discussed in Thread: SYSBIOS

Hi.

I am using SYS / BIOS and TMDSSK3358.

I attach the project.

1616.xx_bios_test_2.zip

Data Abort occurs when you run the line 16 "led.c".

log:

[CortxA8] Exception occurred in ThreadType_Main.
Main handle: 0x0.
Main stack base: 0x80010204.
Main stack size: 0x1000.
R0 = 0x0000005f  R8  = 0x000a0000
R1 = 0x44e10854  R9  = 0x00000000
R2 = 0x800037dc  R10 = 0x000298d0
R3 = 0x00000000  R11 = 0x000298d0
R4 = 0x4030cfd8  R12 = 0x0000005f
R5 = 0x0001dc4f  SP(R13) = 0x800111f0
R6 = 0x48040000  LR(R14) = 0x80008124
R7 = 0x4030fca0  PC(R15) = 0x80001a7c
PSR = 0x6000019f
ti.sysbios.family.arm.exc.Exception: line 176: E_dataAbort: pc = 0x80001a7c, lr = 0x80008124.
xdc.runtime.Error.raise: terminating execution

Is it possible to abort data so as not to cause How do I?

Best Regards,

hamada

  • TI__Mastermind 32475 points

    hamada,

    Please checkout the "4 Exception Dump Decoding Using the CCS Register View" from the following link for decoding the exception.

    http://processors.wiki.ti.com/index.php/SYS/BIOS_FAQs

    I didn't get your question "Is it possible to abort data so as not to cause How do I?" but I don't think its possible to do what you are thinking.  An exception is generated and it will go to abort.

    Do you have the data cache turned on?  If so, you might need entries in the MMU table for the LED addresses.

    Judah

  • TI__Mastermind 21645 points

    Hi Hamada,

    I believe you are getting a data abort due to a MMU fault on data read. The "initializeLED" function in your app is attempting to access some memory mapped registers at 0x44E1xxxx and 0x44E0xxxx without mapping these address ranges in the MMU.

    Please go through the A8 MMU cdoc to see how to add MMU entries for peripheral memory-mapped regs:

    http://downloads.ti.com/dsps/dsps_public_sw/sdo_sb/targetcontent/sysbios/6_40_01_15/exports/bios_6_40_01_15/docs/cdoc/ti/sysbios/family/arm/a8/Mmu.html#xdoc-desc


    Best,

    Ashish