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.

F28335 infinite loop

Other Parts Discussed in Thread: TMS320F28335

Hi All,

I use CCS v4.1.2.00027 with XDS100. I made a test project for  TMS320F28335 with rts2800_fpu32.lib and try to debug it. In this case program goes to

  _c_int00:

0x33970C:  MOV @SP,#0x0400
0x33970E:  SPM 0
0x33970F:  SETC OBJMODE
0x339710:  CLRC AMODE
0x339711:  SETC M0M1MAP
0x339712:  SETFLG RNDF32=1

and from 0x339712 jumps to

0x3FF9F4:  SETC OBJMODE
0x3FF9F5:  EALLOW
0x3FF9F6:  MOVZ DP,#448
0x3FF9F7:  MOV @41,#0x0028
0x3FF9F9:  EDIS
0x3FF9FA:  SB 0,UNC
0x3FF9FB:  ITRAP1
0x3FF9FC:  ITRAP1

and stucks at  0x3FF9FA forever. If I recompile this test project with Fix Point Library then it works fine.

I have a project wich I did with float point (and it was working and debugging well) on earlier version of CCS4. I try to debug it with current version of CCS4 and have the same problem. I hadn't such problems on earlier versions of CCS4.

Can You advice me something? Thank You in advance!!!

 

  • Hi All,

    I figure out that CPU falls in ROM exactly when it executes SETFLG RNDF32=1. This instruction is "set flag in FPU status register". I copied this instruction inside the code of  DSP2833x_CodeStartBranch.asm  file and tried to debug. When step by step debugging reaches and executes SETFLG RNDF32=1 in DSP2833x_CodeStartBranch.asm  file, program falls to ROM again at next address:

    0x3FF9F4: SETC OBJMODE
    0x3FF9F5: EALLOW
    0x3FF9F6: MOVZ DP,#448
    0x3FF9F7: MOV @41,#0x0028
    0x3FF9F9: EDIS
    0x3FF9FA: SB 0,UNC
    0x3FF9FB: ITRAP1
    0x3FF9FC: ITRAP1

    May be I should initialize FPU before  SETFLG RNDF32=1?????????????????????

    Any help please!!!!!!!!!!!!!

  • Mihail,

    Just to be sure, can you double check the markings on the device.  Is it 28335 or is it 28235?

    thank you

    Lori

  • Yes, You are right Lori. I allready solved this problem. I took enother device variant and forgot that it has 235 instead of 335. Thank You for your help!!!