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.

CCS: TIesr_C55_demo

Tool/software: Code Composer Studio

Hello,

Still yesterday, I was successfully running the TIesr_C55_demo on the EZDSP5535 we had purchased. I was able to change the phrase, and the performance was satisfactory. Then, by inadvertence, I closed the CCS6. Upon re-opening, the projects were no more there, neither was the configuration, perhaps I forgot to export. I followed the previously followed steps from the manual, and restored the project, so that I have three projects:

C55XXCSL_LP

TIesrDemoC55

TIesrEngineC55

Compiling and linking all went OK after a few hiccups. I also created the required Target Configuration, and tested it to connect OK to the board(I actually never disconnected the board).

Then I followed the steps: Run-->Debug Configuration --> Program, which showed the TIesrDemoC55.out in the folder C:\workspace\TIesrDemoC55\Debug and prior to that I checked this is the latest build from a few minutes before.

Then click on Debug, the program loaded(that is what the green bar and status windows show), and I have on the console window a message saying everything GEL is completed, on the middle window I have shown the source code of sys_init.c, and on the Debug window icons and messages that the XDS100v2 USB Debug Probe hit a SW Breakpoint. Exactly as before. Below that message I have:

main() at sys_init.c:71 0x01FE59

c_int00 0x03ED0A (the entry point was reached)

The EZDSP board has several LEDs lit, and a running message on its display: Play Audio From Your PC.

That is the full observable system status at this moment.

Then I hit Run(the green triangle on the top) and... nothing works. The board continues to display the Play Audio From Your PC message, the XDS probe in the Debug window shows: Suspended

and right below I have the message:

abort() at exit.c:92 0x025E31 (abort does not contain frame information)

In the middle window, next to the sys_init.c source code, a subwindow opened with a tag: abort() at /tmp/TI_MKLIBNhUOhW/SRC/exit.c:92 0x25e31

and inside that window two messages in red:

Can't find a source file at "/tmp/TI_MKLIBNhUOhW/SRC/exit.c"

Locate the file or edit the source lookup path to include its location.

The above described situation doesn't change, despite efforts to try to understand and fix it, for a few hours now and yesterday.

Please help.

Regards,

Vladimir

  • Hello,

    For the moment it is either this:

     undefined       first referenced                                                       
      symbol             in file                                                            
     ---------       ----------------                                                       
     __STACK_SIZE    C:/ti/bios_5_42_02_10/packages/ti/bios/lib/bios_NONINST.a55H<boot.o55H>
     __SYSSTACK_SIZE C:/ti/bios_5_42_02_10/packages/ti/bios/lib/bios_NONINST.a55H<boot.o55H>

    error #10234-D: unresolved symbols remain
    error #10010: errors encountered during linking; "TIesrDemoC55.out" not built

    when I put everything the required projects use the same(in terms of processor type, memory, pointer size, bios version, etc.)

    or the sudden exit() mentioned before, which I traced to the the function OpenASR, and inside OpenASR to the last memory allocation which doesn't return a success status, and because of that, after returning in main, an IF branches to an exit().

    But, it used to work fine, so I'm really puzzled, how did it work before?

    It probably has to do with the structure of the projects. Could you please help me understand what exactly this one has to be in a repeatable way. Meaning that I could reproduce the good working every time, and not be concerned that if I get it to work, it might be by chance, and if I close CCS, next time it will be like it never worked before.

    Best regards,

    Vladimir

  • Hi,

    Can you check the following two discussions:
      

    Best Regards,

    Yordan

  • Hello,

    Thank you! Yes indeed, I have read these forum entries. I think the guys are right, TIesr doesn't accept more than two phrases. Which is fine. exit() from such a situation is also fine, I have seen it with other programs too, non related to TIesr, EZDSP5535 demo programs.

    The main current problem is that there has not been a way to build the code again. atafs_bios_drv_lib builds fine, C55XXCSL_LP builds fine, cslVC5505 although referenced by TIesrDemoC55, is old, unavailable for CCS6, and a forum answer was that it can only cause trouble, and should be replaced with C55XXCSL_LP. TIesrEngineC55 also builds fine.

    I use the suggested by the project itself at certain point 5.42.2.10 DSP/ BIOS version for all projects involved(TIesrEngineC55 doesn't ask for BIOS version).

    TIesrDemoC55 executable however won't buid. There used to be errors with memory overlap at linking(compiling was fine), and a message thet _STACK__ was undefined reference. And then all of the sudden, the errors changed to compile time errors. Now it is:

    #167 Too few arguments in a function call

    and

    #167 Argument of type "Bool" is incompatible with parameter type "Int16"

    for this function call:

            status = I2C_read(readBuff,
                            1,
                            I2C_CODEC_ADDR,
                            TRUE,
                            startStop,
                            CSL_I2C_MAX_TIMEOUT,
                            FALSE);

    in file

    codec_aic3254.c

    which shouldn't make sense, since this is a TI system function.

    Any help is highly appreciated.

    Best regards,

    Vladimir

    P.S. The first time I followed all steps in the PDF documentation, TIesr did build and worked, even changed trigger phrases. Now it "refuses" to build, even in a totally new and clean workspace with exactly the same steps.

  • Hi Vladimir

    Since you have had multiple threads on TIesr ,  our support has been spotty but you seem to be able to make progress - I just wanted to check if the issues on this post got resolved for you or you still looking for guidance?

    Regards

    Mukul

  • Hello,

    It's all resolved now, thank you! I could use some more information on the design behind the code, and these language models that seem missing, e.g. the folder English, and eventually the programs in the tools folder, but there is no rush.

    Best regards,

    Vladimir