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.

xdc.runtime.Error.raise: terminating execution

Guru 15580 points
Other Parts Discussed in Thread: SYSBIOS, OMAP-L138

As I step through my (SYSBIOS) code I get the following error:

xdc.runtime.Error.raise: terminating execution

...when I attempt to execute the following code:

 

//-----------------------------------------------------------------------------

// \brief   transitions a local psc module to a new state.

//

// \param   psc_regs_t *psc - psc register that contains the local module.

//

// \param   uint32_t in_domain - input power domain (always on / internal).

//

// \param   uint8_t in_module - module to be set.

//

// \param   uint8_t in_next_state - next state for the local module.

//

// \return  none.

//-----------------------------------------------------------------------------

void EVMOMAPL138_lpscTransition(psc_regs_t *psc, uint32_t in_domain, uint8_t in_module, uint8_t in_next_state)

{

   // spin until existing transitions are done.

   while (CHKBIT(psc->PTSTAT, in_domain)) {}  *******ERROR OCCURS HERE ********

....the following error message is thrown in the console window:

 

Exception occurred in ThreadType_Main.

Main handle: 0x0.

Main stack base: 0xc20515b4.

Main stack size: 0x1000.

R0 = 0x00000001  R8  = 0x0ca00000

R1 = 0x00000001  R9  = 0xd0a09a5f

R2 = 0x00000007  R10 = 0x19a6f846

R3 = 0x00000003  R11 = 0x38402d55

R4 = 0x80000288  R12 = 0x01e27000

R5 = 0xc20524b0  SP(R13) = 0xc2052578

R6 = 0x00000000  LR(R14) = 0xc204753c

R7 = 0x0000802a  PC(R15) = 0xc2040bd4

PSR = 0x800000df

ti.sysbios.family.arm.exc.Exception: line 174: E_dataAbort: pc = 0xc2040bd4, lr = 0xc204753c.

xdc.runtime.Error.raise: terminating execution

Could someone please help translate this error code ??

Thx,

MikeH

 

 

 

  • And now when attempting to debug on the DSP side of my OMAP-L138 target, I get this :

    A0=0xB  !¼€(8J‰õB¼?*\A10=0xô A11=0x¨

    A12=0xBB#€¨¨ A13=0xB€#¨ô

    A14=0xB A15=0x€Á

    A16=0xô A17=0xBô

    A18=0xô A19=0xÁÁ#ôÁÁÁÁ

    A20=0xBB#<¨# A21=0x?€¨B›€

    A22=0x¨¨#›››€Á A23=0x¨<ÁBB

    A24=0x¨¨#›››€Á A25=0x?<?¨¨

    A26=0x?<Ò¨#¨ A27=0xô

    A28=0x€€›?€¨ A29=0xô

    A30=0xô A31=0xB

    B0=0xô B1=0xB

    B2=0xô B3=0x¨<ôB#ô€

    B4=0xÒ€Ò€Ò€Ò€ B5=0xBB#€#ô

    B6=0x¨¨¨¨¨¨ô B7=0xB<

    B8=0x€ B9=0x€

    B10=0xBB#¨# B11=0xBB¨¨€›B

    B12=0x<›€€<€B B13=0x<ôÁÒ€

    B14=0x¨<ô<¨ôô B15=0x¨<ô<¨¨#

    B16=0xô B17=0xBB#¨<

    BX£f©7â½xJNzšÊû¿¨:yJô‚½ƒ     ©ö¢½ÔB¾¿Ø˜¡xJÖõ‚½Ãùž˜¡xJÖõ‚½Ãùž"ÙÀƒ×B>¢NTSR=0xBôôô¨

    ITSR=0xô

    IRP=0xô

    SSR=0xô

    AMR=0xô

    RILC=0xô

    ILC=0xô

    Exception at 0xÒ€Ò€Ò€Ò¨

    EFR=0x< NRP=0xÒ€Ò€Ò€Ò¨

    Internal exception: IERR=0xB

    Instruction fetch exception

    Can anyone provide some insight into what is going on?

    Thx,

    MikeH

     

  • Bios guys & gals,

    Can anyone provide feedback on this? It's a new problem as of today.....

    Thx,

    MikeH

  • I'm not sure why your second exception is dumping gibberish.  However, the contents of your first post suggest that the following line is causing a data exception:

    CHKBIT(psc->PTSTAT, in_domain);


    What does the macro 'CHKBIT' do?  Is 'psc' a valid pointer?

  • Shreyas,

    Shreyas Prasad said:
    What does the macro 'CHKBIT' do?  Is 'psc' a valid pointer?

    CHKBIT is a macro from the Logic BSL

    #define CHKBIT(dest,mask)     (dest & mask)

    Below is the psc pointer address, which is 0x01e70000 on the OMAP-L138 PSC1.

    psc = 0x01E27000

    *(psc) = {...}

    REVID = Attempted to read unmapped virtual memory at 0x01E27000

    RSVD0 = 0x01E27004

    INTEVAL = Attempted to read unmapped virtual memory at 0x01E27018

    RSVD1 = 0x01E2701C

    MERRPR0 = Attempted to read unmapped virtual memory at 0x01E27040

    RSVD2 = 0x01E27044

    MERRCR0 = Attempted to read unmapped virtual memory at 0x01E27050

    RSVD3 = 0x01E27054

    PERRPR = Attempted to read unmapped virtual memory at 0x01E27060

    RSVD4 = Attempted to read unmapped virtual memory at 0x01E27064

    PERRCR = Attempted to read unmapped virtual memory at 0x01E27068

    RSVD5 = 0x01E2706C

    PTCMD = Attempted to read unmapped virtual memory at 0x01E27120

    RSVD6 = Attempted to read unmapped virtual memory at 0x01E27124

    PTSTAT = Attempted to read unmapped virtual memory at 0x01E27128

    RSVD7 = 0x01E2712C

    PDSTAT0 = Attempted to read unmapped virtual memory at 0x01E27200

    PDSTAT1 = Attempted to read unmapped virtual memory at 0x01E27204

    RSVD8 = 0x01E27208

    PDCTL0 = Attempted to read unmapped virtual memory at 0x01E27300

    PDCTL1 = Attempted to read unmapped virtual memory at 0x01E27304

    RSVD9 = 0x01E27308

    PDCFG0 = Attempted to read unmapped virtual memory at 0x01E27400

    PDCFG1 = Attempted to read unmapped virtual memory at 0x01E27404

    RSVD10 = 0x01E27408

    MDSTAT = 0x01E27800

    RSVD11 = 0x01E27880

    MDCTL = 0x01E27A00

     

     

     

  • Mike,

    I am going to move this thread to the OMAP-L1x forum to see if you can get a faster response there, as it appears that you are getting an ARM exception that, although it is being handled by BIOS, is being caused in non-BIOS related code.

    Dave