Debugging an XDC runtime error

Mike Volzer

Other Parts Discussed in Thread: SYSBIOS

I'm debugging a custom board in Code Composer 4 with a Stellaris 9000 series part on it using the Stellaris In-Circuit Debugger from the evaluation kits and I am getting an XDC runtime error. I was wondering if anyone could give me some insight on how to debug this error. It seems as though the error is thrown after SYS/BIOS starts. Tasks do begin running. I removed all of the tasks and it still crashes.

I think it is also important to note that I've successfully programmed and debugged this same board and code with a Spectrum Digital XDS510 USB emulator. No crashing at all.

{module-rope:8028}: line 601: error {id:0xb250000, args:[0x3, 0xdef4]}
xdc.runtime.Error.raise: terminating execution

Updated post with more information.

over 14 years ago

0 Bobby Bradford over 14 years ago

TI__Genius 10040 points

From the description of the error you provided, I believe this post may be better answered in the Code Composer Studio forum. I will move the thread into that forum for discussion.

--Bobby

0 ToddMullanix over 14 years ago in reply to Bobby Bradford

TI__Guru* 96960 points

Can you set a breakpoint at xdc_runtime_Error_raiseX__E. Unfortunately you probably will not get the back-trace, but you can look at ROV to determine where you were (e.g. main, Hwi, Swi or Task) when the error happened. Look at the BIOS in ROV. You'll see a "currentThreadType" field. Do you have the full error strings?

Todd

0 Mike Volzer over 14 years ago in reply to ToddMullanix

Intellectual 990 points

When I try to set the breakpoint I get this error. Do you know what I need to do to get around this?

0 ToddMullanix over 14 years ago in reply to Mike Volzer

TI__Guru* 96960 points

Mike,

Can you look in your mapfile and find the exact full name for Error_raiseX. It will be something close to what I said (e.g. xdc_runtime_Error_raiseX__E).

Todd

0 Mike Volzer over 14 years ago in reply to ToddMullanix

Intellectual 990 points

My project is "Stellaris_Boot"

I'm not too familiar with the map file, but it does have a line.

00000001 xdc_runtime_Error_raiseX__E

I tried setting the breakpoint in Stellaris_Boot/Debug/configPkg/package/cfg/Stellaris_Boot_pem3.c in the xdc_runtime_Error_raiseX__E function and that's when I get the error. There is also a xdc_runtime_Error_raiseX__F function in the map file.

0 ToddMullanix over 14 years ago in reply to Mike Volzer

TI__Guru* 96960 points

The mapfile tells you where all the functions, global variables, interrupt vectors, etc. are located in memory. Can you attach your mapfile?

Todd

0 Mike Volzer over 14 years ago in reply to ToddMullanix

Intellectual 990 points

The forum says this file type is not allowed so I changed the file extension to txt.

2235.Stellaris_Boot.map.txt

Edit: Got the breakpoint set. I'm also unfamiliar with ROV. Could you let me know what I need to do in order to find this?

0 Mike Volzer over 14 years ago in reply to Mike Volzer

Intellectual 990 points

Ok found ROV in the BIOS section my currentThread ti.sysbios.BIOS.ThreadType_Main

0 ToddMullanix over 14 years ago in reply to Mike Volzer

TI__Guru* 96960 points

Mike,

Since it is happening in main(), you should be able to step through in the debugger and find where the problem is being generated from. Common reasons for a runtime error

- Trying to allocate memory when there is not enough
- Calling APIs in the wrong context (e.g. Semaphore_pend with a timeout in main, a Swi or Hwi.
- Calling System_printf in a Swi or Hwi (if you have SysStd...which you do...I saw it in the mapfile).

Todd

Processors

Processors forum

Debugging an XDC runtime error