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.

How to burn a Network Programm(uses the NDK DaemonServer) into SPI Memory on the C6748 Board?

Hello, everyone here.

I have a question. I use a L138 Evalboard with the SOM C6748 DSP from Logic PD. I have written a Program which uses primary the Daemon Server of NDK. My board program works quasi as the Server. Der Windows-Computer works as the Client. By the Runtime the windows-computer try to connect the board. The Board Daemon-Server accept this request. And then they interchange each othe the data per Ethernet TCP Socket. I use the bios6-config to set a fest IP for DaemonServer.

My network programm uses the bios 6. I use the CCS V4.2 to programm it. For debug i use a Debugger XDS 560 V2. 

All my network programm run without problem with CCS V4.2. Now i want to burn it into SPI Flash and test, if it is faster than with debugger.

I have fund a Topic in this Forum: http://e2e.ti.com/support/dsp/tms320c6000_high_performance_dsps/f/115/t/112073.aspx

Its a very good documentation for Burning programm into SPI-Flash. I folge also the way which was descripted in this Topic. Firstly i use the AISgen to convert my release.out to flashing.bin. And then i burn it with the SPIWriter.

But after the Burning with the SPI-Writer and reset of the s7 Switsch to SPI Mode my Program doesn't run. After put the net cable in Win-PC and the Board, the Connection is not builded. The net logo in WINDOWS is not lighted.

I am sure, i use the correctly config of the ASIgen, because i have compared my ASIgen-Configuration with my c6748.gel.

In oder to test if the SPIWriter does run at all, i have burned the Workshop Bios_Led Programm into the Board. It does run without problem.

I guess, i must set the fest IP on my Board per Tools such as Putty. But How can i do this? Can anyone help me?

  • One of the first debug tips that we provide to debug boot related issues is connecting to device using the emulator and running diagnostics using the the OMAPLx Debug GEL file provided here. Make sure that you remove the device GEL file in CCSv4 if there is any included by default and then load the debug GEL file.

    Debug GEL file: http://processors.wiki.ti.com/index.php/OMAP-L1x_Debug_Gel_Files

    If  the debug GEL output indicates every thing looks okay, go to View->Disassembly and see where the program counter of your DSP is stuck at (Also provided by GEL file or can be seen in core registers of the Register view). If this is stuck in some location where your application binary is loaded. Go to Run-> Load Programs->load symbols only in CCS and select the .out file on your file system. This will show symbols in the disassembly without actually loading the code.  Then select View source option in the Disassembly window to find out exactly where the program counter is stuck.

    Let us know this helped you debug where the issue lies. If not post the debug log here so that we can help, you analyze the situation.

    Regards,

    Rahul

  • Hello, Rahul.

    Firstly thank you very much for your answer.

    What you mean is that i must find the location where my programm stop?

    Then which informations should i post here so that you can help me?

    Regards,

    Jia