CSL 2.10 Examples as standalone (flashed) applications

Christos Nikolaou12204

Hi,

Is there a procedure on making any of the CSL 2.10 examples as a standalone application in any of the EVM5515/eZDSP5515 by storing them to external flash memory and bootloading from there?

Is there anything that needs to be included in the CSL 2.10 examples or any change required in order for them to be standalone flashed applications?

Christos

over 14 years ago

0 Hyun Kim over 14 years ago

TI__Genius 14965 points

Hi,

There is no single document to explain all steps. Informations are scattered. I hope that we make a well explained documents regarding flashing it.

BTW, which hardware do you using, EVM or eZdsp?

Regards,

Hyun

0 Christos Nikolaou12204 over 14 years ago in reply to Hyun Kim

Expert 1790 points

Hi Hyun,

I'm using the eZDSP and the FDK.

What I'm interested is the required changes for a CSL 2.10 example to be a 'flashable' application.

I do know and have succesfully performed the flashing of the Spectrum Digital provided sample on the eZDSP5515 and the TI fingerprint sample on the FDK.

(Also flashed succesfully the http://code.google.com/p/c5505-ezdsp/ C5515_eZdsp_Audio_Filter_Demo)

It seems though that the CSL 2.10 examples even though when succesfully flashed, they do not work so my question is focused on that, what it takes for a CSL 2.10 example to be flashed and running?

Regards,

Christos

0 Hyun Kim over 14 years ago in reply to Christos Nikolaou12204

TI__Genius 14965 points

Hi,

The default compile option for CSL2.1 is for C5515EVM. In order to change compile option to C5515eZdsp, please read release note included in the CSL 2.1 package.

There are compile options in csl_general.h. Be notice that a certain example is not applicable to eZdsp. C5515 EVM works 100% with CSL examples. I know that I2S examples are not fully applicable to eZdsp. There issome missing area like eZdsp BSL not used. You need to modify code to work with eZdsp.

Regards,

Hyun

0 Christos Nikolaou12204 over 14 years ago in reply to Hyun Kim

Expert 1790 points

Hi Hyun,

You missunderstood the question.

I do not ask how to make the examples work for eZDSP, I can do that very easily and have done so far with great success.

The question that I ask is why the CSL 2.10 examples do not work when they are flashed ?

They work properly within CCS and the XDS100, yet when flashed they do not operate.

That is not the case though with the SD provided samples whereas they work ok in both the CCS environment and when they are flashed, the same applies to the FDK TI samples and the audio filter in googlecode.

That is the question, why these aforementioned samples worked when flashed whereas the CSL 2.10 examples (although work within CCS) do not run when flashed.

Regards,

Christos

0 Hyun Kim over 14 years ago in reply to Christos Nikolaou12204

TI__Genius 14965 points

Hi,

I see your point. The some CSL examples are not intended for flashing. The main purpose of example are showing how to use CSL functions and check it within CCS.

In order to flash it, you need to have additional steps depending on the example. For example, some example requires CPU to run over a certain frequency.

It's taken care of by GEL file in CCS. If you flash this example, it won't work correctly. Which example are you working with?

Regards,

Hyun

0 Christos Nikolaou12204 over 14 years ago in reply to Hyun Kim

Expert 1790 points

Hi Hyun,

Now you're right to the point.

The example of interest is the CSL_USB_DmaExample (CCS4), which it works ok under CCS yet it does not when flashed.

Regards,

Christos

0 Christos Nikolaou12204 over 14 years ago in reply to Christos Nikolaou12204

Expert 1790 points

Is there any suggestion on how to make this CSL_USB_DmaExample (CCS4) example running on flash?

0 Pratap Reddy M V over 14 years ago in reply to Christos Nikolaou12204

Expert 2605 points

Hi Christos,

How you are creating your boot image and how you are flashing it.

When running from the CCS, CSL examples depend on the gel file for the PLL clock configuration. If you take care of PLL configuration in your boot code, you should be able to boot and run the CSL examples.

After bootloader loads the CSL code, successful execution of the program depends on the code entry point. Boot loader should be properly configured to change the code execution from end of bootloader to start of your CSL example.

Pratap.

0 Christos Nikolaou12204 over 14 years ago in reply to Pratap Reddy M V

Expert 1790 points

Hi Pratap,

Nice to see you again.

The issue has been solved, I've used a modified version of the c5515_init.asm file from Real Time Power Monitoring example.

Regards,

Christos

0 Pratap Reddy M V over 14 years ago in reply to Christos Nikolaou12204

Expert 2605 points

Hi Christos,

Pleased to hear that you are successful in making the CSL examples work with bootloader.

Pratap.

0 Hyun Kim over 14 years ago in reply to Pratap Reddy M V

TI__Genius 14965 points

Hi Christos,

It's good to hear that you resolved your issue. Can you tell me how useful of Real Time Power Monitoring?

Regards,

Hyun

0 Andrea Cruz over 14 years ago in reply to Christos Nikolaou12204

Intellectual 650 points

Dear Christos,

I am trying specify the entry point reset_isr but without sucess (bellow link).

http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/p/53200/370611.aspx#370611

Looking for solution I found the bellow post that cites your.

http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/p/52076/326926.aspx#326926

I can not run the C5515EVM_Power_monitoring because I am using 5515 ezdsp and a lot of problems happened.

So, please, could you give more details how to use the c5515_init.asm to configure the DSP, for example:

1 - where do you put the lpva200.inc? do you have registers conflict problems? other files are necessary?

2 - how and where do you specify the entry point reset_isr? it is necessary? I think it is.

3 - what kind of changes do you make on vectors.asm file?

4 - what kind of changes do you make on Build Properties...?

5 - I am using dma, sd, i2c and i2s, please, could you share with me your configuration (c5515_init.asm)

Thanks for help,

Andrea

0 Rijurekha Sen over 14 years ago in reply to Andrea Cruz

Intellectual 645 points

Hi Andrea,

I am having similar problems as you.

I have built a hardware prototype with C5515 ezdsp, (gps+gprs) module sim548c and xbee radio. I have extended the CSL_MMCSD_FSExample project to receive packets on xbee radio using pingpong dma of uart, read timestamp from gps, store timestamped data in a file in sd card and send occasional messages to server over gprs. Everything runs fine using ccs.

But I cannot run the application without ccs. In fact, I cannot run the basic CSL_MMCSD_FSExample project in standalone mode.

1) I added the pll configurations (that gel does in ccs) in the application.

2) I extended the nor_writer to write the boot image iteratively to the nor flash

But the ezdsp stick neither runs the program nor connects to ccs once I load my boot image. I have to short pins on the nor flash and corrupt the boot image, while powering the stick, to make it connect again to ccs.

Have you been able to sort out the problem?

Can you tell me the steps to make a proper boot image of the CSL_MMCSD_FSExample project and run it in stand alone mode?

Thanks in advance,

Riju

0 Rijurekha Sen over 14 years ago in reply to Rijurekha Sen

Intellectual 645 points

Even after booting large bin file, I am not able to run in standalone mode. Have you tried running the CSL_MMCSD_FSExample_Out project in stand alone mode?

If I add only PLL initialization in main program and create bin file and load to flash, my USB stick doesn't run my application nor does it connect to ccs. I have to shrt pins on the nor_flash during powering up the stick to corrupt the bad boot image, to make it connect to ccs.

After reading the infinite forum discussions related to this topic, I guess I need to

(1) include lpva.inc and vectors.asm files in the project from the C5515 Audio Filter project

(2) define and call InitSystem(); ConfigPort(); and SYS_GlobalIntEnable(); functions in my main program like the C5515 Audio Filter projectand also include the register_system.h file for register definitions.

(3) change the entry point of my program to reset_isr instead of c_init00

(4) build the project after removing possible compilation and link errors due to register name conflict etc. due to the newly added files

(5) create bin and load using new nor_writer.

Am I correct in my understanding? Anyone, who has been able to succefully load and run a dsp/bios based csl project in satnd alone mode from flash, please help.

Thanks,

Riju

0 Rijurekha Sen over 14 years ago in reply to Rijurekha Sen

Intellectual 645 points

After screwing up my usb stick umpteen number of times with bad boot images, finally I am able to run the CSL_MMCSD_FSExample project in stand alone mode. I will summarize the steps, so that others don't have to go through the forum posts.

1) Download the audio filter project for c5515 available at http://code.google.com/p/c5505-ezdsp/. I include the project in this post for completeness. 0363.C5515_eZdsp_Audio_Filter_Demo1.zip

2) Copy the files vectors.asm, inc/lpva200.inc and inc/register_cpu.h from the audio project in the CSL_MMCSD_FSExample project folder.

3) Open the main_bypass1.c file in the audio project and copy the routines InitSystem(); ConfigPort(); and SYS_GlobalIntEnable(); into the main c program csl_mmcsd_atafs_example.c of the CSL_MMCSD_FSExample project. Call these 3 functions at the beginning of main. Include register_cpu.h in this c file.

4) Try to build the project. You might need to change vectors.asm file according to the name of isr functions defined by you. I had to change DMA_Isr and RTC_Isr to dma_isr and rtc_isr.

5) Right click on the project, go to Properties -> C/C++ Build -> C5500 Linker -> Symbol Management and put reset_isr at "Specify program entry point for the output module"

6) Build the project again. There should be a warning that entry point symbol other than "_c_int00" specified, which indicates that we have successfully changed the entry point.

7) Using windows command prompt, cd to code generation tools/ bin and create the bin image of the .out file using the following command line.

hex55.exe -boot -v5505 -b -serial8 file.out -o file.bin

8) Download this nor_writer program which is able to load large bin files to the nor flash of the stick, unlike the spectrum digital version which gets stuck at 32KB 4617.nor_writer.tar.gz. Import this project to ccs and load and run the out file. It will ask for the path to bin file in the console. Enter it (e.g. C:\file.bin). The console will show how the flash is erased, bin is written iteratively and boot signature is written.

9) Disconnect the stick from ccs and then plug it in to power it up. The stick should boot from the file.bin image that you have just loaded and write files to the micro sd card.

1), 2), 3), 4) are needed to have proper initialization of PLL and peripherals in the project, as in standalone mode, these initializations will not be done by gel file. 5), 6) are needed so that, after our boot image is loaded to ROM, the correct entry point to the code is specified. 7) is needed to create a proper boot image from our program. 8) is needed to load the boot image into the nor flash of the stick. 9) is needed to see that the program is running properly in stand alone mode.

The numerous threads in this forum that helped me to reach at the above steps are as follows:

1) http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/p/69160/261049.aspx#261049

2) http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/p/52076/371515.aspx#371515

3) http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/p/53200/370611.aspx#370611

4) http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/p/84222/402719.aspx#402719

5) http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/110/p/33709/117751.aspx#117751

6) http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/p/59233/213489.aspx#213489

7) http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/p/70095/374570.aspx#374570

8) http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/p/53200/372229.aspx#372229

9) http://e2e.ti.com/support/dsp/tms320c5000_power-efficient_dsps/f/109/p/66178/402327.aspx#402327

10) http://processors.wiki.ti.com/index.php/Debugging_Boot_Issues

It has happened many times in this process of testing whether my boot image works, that neither my boot image worked nor did the stick connect to the ccs with my bad boot image. Shorting pins on the nor-flash with a small wire while powering up the stick, corrupts the boot image on the nor flash and the stick can connect again to ccs.

Thanks,

Riju