Technical discussions about the TI C54x DSPs (including the c5401, c5402, c5402a, c5404, c5407, c5409, c5409a, c5410, c5410a, c5416, c5420, c5421, c5441, c549, c5470 and c5471).
|
When I use Single Step Target a asm Program,the CCS2.1 occur a message
like this:"Unexpected Fatal Error Encountered which may have been caused by a stack
overflow,out of memory condition,or access violation.I'm going to try and save your work before
TERMINATING this application."I doubt that FIRS instruction cause this problem.Is FIRS work on
DARAM?How can I to solve this problem?My program and cmd file is as follow:
;****************fir5.asm*******************
.mmregs
.def start .bss y,1 x_new .usect"DATA1",4 x_old .usect"DATA2",4 size .set 4 PA0 .set 0002h PA1 .set 0001h .data COEF .word 1*32768/10,2*32768/10 .word 3*32768/10,4*32768/10 .text start: RSBX CPL LD #y,DP SSBX FRCT STM #x_new,AR2 STM #x_old+(size-1),AR3 STM #size,BK STM #-1,AR0 PORTR PA1,@x_new FIR: ADD *AR2+0%,*AR3+0%,A RPTZ B,#(size-1) FIRS *AR2+0%,*AR3+0%,COEF STH B,@y PORTW @y,PA0 MAR *+AR2(2)% MAR *AR3+% MVDD *AR2,*AR3+0% BD FIR PORTR PA1,*AR2 .end ;***********************************
;**************fir.cmd********************
vectors.obj fir5.obj -o FIR.out -e start MEMORY { PAGE 0: EPROM:org=0E000H,len=1000h VECS :org=0FF80H,len=0080h PAGE 1: SPRAM:org=0060h ,len=0010h DARAM:org=0080h ,len=1380h } SECTIONS { .text :>EPROM PAGE 0 .data :>EPROM PAGE 0 .bss :>SPRAM PAGE 1 DATA1 :>DARAM PAGE 1 DATA2 :>DARAM PAGE 1 .vectors:>VECS PAGE 0 }
|
|
建山 江 wrote: > When I use Single Step Target a asm Program,the CCS2.1 occur a > message like this:"Unexpected Fatal Error Encountered which may have > been caused by a stack overflow,out of memory condition,or access > violation.I'm going to try and save your work before TERMINATING this > application."I doubt that FIRS instruction cause this problem.Is FIRS > work on DARAM?How can I to solve this problem?My program and cmd file > is as follow: Its not a problem with your code. That's a CCS/Windows error box saying that CCS has eaten itself alive and is in the process of crashing nicely. I wouldn't recommend letting it save the workspace or anything else it wants to do, it tends to corrupt whatever it tries to preserve. CCS 2.2 does this a little less often, but is still not what I would expect after paying a couple of K for a piece of software. It still has memory leaks that use up windows resources after opening/closing CCS multiple times without rebooting the machine. I sure wish there were a GCC target for the C5xxx series. Brian -- ----------------------------------------------------- Brian C. Lane (W7BCL) Programmer www.shinemicro.com RF, DSP & Microcontroller Design |