Getting exception error while running SYSBIOS Helloworld on BeagleBoard-XM

Sreeram,

This error is a Data Abort exception catched by the EXC module of SYSBIOS (the module that handles exceptions). In CCS help you can search for E_dataAbort and find its reference.

The rest of the error message indicates the registers reported by the ARM core at the moment the exception happened: PC is the Program Counter and LR is the Link Register.

We (TI) follow the ARM implementation for the exception handling, therefore the best reference to investigate that is shown at the ARM infocenter, more specifically at this page.

In addition to that, some other references on the web may help you pinpoint the exact instruction that is causing that.

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

http://www.keil.com/support/docs/3080.htm

Hope this helps,

Rafael

Hi Rafael

Thanks for quick reply

Now i am not getting that Data Abort exception error after selecting exact platform "ti.platforms.evm3530 " in build settings (RTSC) for BeagleBoard-XM.

can you please confirm following configuration setup is correct or not

Main-:

output type=executable

family=ARM

varient=davinciDM37xx  BeagleBoard_xM

connection=TexasInstrument XDS100v2 USB Emulator

RTSC-:

Target=ti.targets.arm.elf.A8Fnv

Platform=ti.platforms.evm3530

Build-profile=release

With this configuration I am building SYS/BIOS Hello world  project  without errors. After that I clicked on debug symbol which is present in menu bar.  During debugging and loading  i am getting following logs (errors are highlighted in red color).

Cortex_A8_0: GEL Output: OMAP 32K Watchdog Timer is disable
Cortex_A8_0: GEL Output:  Putting DPLL into bypass before proceeding
Cortex_A8_0: GEL Output:  Putting CORE DPLL into bypass before proceeding
Cortex_A8_0: GEL Output:  Locking CORE DPLL
Cortex_A8_0: GEL Output:  PRCM clock configuration IIA setup has been completed
Cortex_A8_0: GEL Output:  SystemClock = 26.0 MHz
Cortex_A8_0: GEL Output:  DPLL_MULT_VALUE = 332
Cortex_A8_0: GEL Output:  DPLL_DIV_VALUE = 25
Cortex_A8_0: GEL Output:  CORE_DPLL_CLK = 664.0 MHz
Cortex_A8_0: GEL Output:  CORE_CLK = 332.0 MHz
Cortex_A8_0: GEL Output:  L3_CLK = 166.0 MHz
Cortex_A8_0: GEL Output: mDDR Hynix H8KDS0UN0MER - 2048 Mbit(256MB) on CS0, 16M x 32bit x 4Banks
Cortex_A8_0: GEL Output: Waiting for SDRC DLL to lock...
Cortex_A8_0: GEL Output: SDRC DLL successfully locked
Cortex_A8_0: GEL Output: common_sdram_init() completed
Cortex_A8_0: GEL Output: SDRC initilization for mDDR Hynix H8KDS0UN0MER completed
Cortex_A8_0: GEL Output: 26MHz clock configuration IIa
Cortex_A8_0: GEL Output: 26MHz clock configuration IIa
Cortex_A8_0: GEL Output:      CORTEXA8_CORE_VERSION = 0x413FC082
Cortex_A8_0: GEL Output: Target contains version r3p2 of the CortexA8...
Cortex_A8_0: GEL Output:     Read the ETM_POWER_DOWN_STATUS register...
Cortex_A8_0: GEL Output:      ETM_POWER_DOWN_STATUS = 0x00000001
Cortex_A8_0: GEL Output:     ETM Access is enabled!
Cortex_A8_0: GEL Output:     ETM_ID = 0x410CF236
Cortex_A8_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_A8_0: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x800083c8: (Error -1066 @ 0x333C) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.0.872.0)
Cortex_A8_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_A8_0: Trouble Setting Breakpoint with the Action "Process CIO" at 0x800061dc: (Error -1066 @ 0x333C) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.0.872.0)
Cortex_A8_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_A8_0: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x80006df0: (Error -1066 @ 0x333C) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.0.872.0)

I have not added any file like .GEL, .ccxml, .cmd files . Sysbios is taking default files (I checked in Target Configuration, it is taking GEL file "..\..\emulation\boards\am_dm37x_evm\gel\am_dm37x_cortexA.gel") and Linker commandfile is empty.

Is it required to add those files to sysbios hello world project for BeagleBoard-XM (DM3730)?

Thanks

Sreeram

palvadi sriram said:

Now i am not getting that Data Abort exception error after selecting exact platform "ti.platforms.evm3530 " in build settings (RTSC) for BeagleBoard-XM.

What were you using before?

palvadi sriram said:

Cortex_A8_0: Trouble Setting Breakpoint with the Action "Finish Auto Run" at 0x800083c8: (Error -1066 @ 0x333C) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.0.872.0)
Cortex_A8_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_A8_0: Trouble Setting Breakpoint with the Action "Process CIO" at 0x800061dc: (Error -1066 @ 0x333C) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.0.872.0)
Cortex_A8_0: Breakpoint Manager: Retrying with a AET breakpoint
Cortex_A8_0: Trouble Setting Breakpoint with the Action "Terminate Program Execution" at 0x80006df0: (Error -1066 @ 0x333C) Unable to set requested breakpoint in memory. Verify that the breakpoint address is in writable memory. (Emulation package 5.0.872.0)

You are getting memory access errors. The debugger is trying to set breakpoints at those addresses and it cannot write to it. Either that memory location is not valid or the debugger is blocking access to those memory regions.

palvadi sriram said:

I have not added any file like .GEL, .ccxml, .cmd files . Sysbios is taking default files (I checked in Target Configuration, it is taking GEL file "..\..\emulation\boards\am_dm37x_evm\gel\am_dm37x_cortexA.gel") and Linker commandfile is empty.

Is it required to add those files to sysbios hello world project for BeagleBoard-XM (DM3730)?

I believe SYS/BIOS will generate a cmd file for you. What you need to check is if the memory regions that the debugger is trying to access are valid memory regions. And if the GEL file you are using are the correct ones for your board.

Thanks

ki

Looking at the GEL file you are using, I see;

    /* !! FOLLOWING MEM SPACE TO BE CONFIGURED PROPERLY !!*/
    GEL_MapAddStr(0x68000000, 0, 0x98000000, "R|W|AS4"    , 0);  /* TO BE CONFIGURED */

I'm not sure exactly what the comment refers to but i assume it means that the memory region was be initialized or configured before it can be used.