dsk6455 flash burn example

Have you checked out SDS's website? There is some documentation there.

http://www.softwaredesignsolutions.com/flashburn.aspx

Thanks

ki

I want to write some information on flash memory while program is running on dsp.  Is there some API with examples for this?

Hi Ki,

Will this support DSK6455 ?

Akash,

Please check with SDS directly. Thanks

ki

Hi Ki ,

The SDS requires .hex file for flash burn ,
Is there any way to convert the .out file that i have got (from embedded coder ,simulink) to hex for DSK 6455 ?
Any Help would be extremely appreciated ....

Akash Mullangi said:

Is there any way to convert the .out file that i have got (from embedded coder ,simulink) to hex for DSK 6455 ?

Yes. A hex conversion utility comes with the compiler installation. See Chapter 11 of:

http://www.ti.com/lit/ug/spru186v/spru186v.pdf

Thanks

ki

Hi,

If you have a project, there is also a post-build step that is automatically configured. Check this thread.

Regards,

Rafael

Hi Rafael ,

Is there any way we could execute that step with out the build ,
This is because I have got my .out file from Embedded coder simulink ....
If so please let me know how to do it ....

Thank you

Hi,

The post build step can itself runs from the command-line, but because a project is used, all the Eclipse variables are properly resolved: the ${CG_TOOL_HEX}, ${BuildArtifactFileName}, etc. In the case of using an external builder, you will have to create your own post build step by following the syntax required by the utility <tiobj2bin.bat>. I suggest opening this batch file in a text editor as it contains its usage details (I couldn't find it documented anywhere else).

Hope this helps,

Rafael

Hi Again ,
The command say "${CG_TOOL_ROOT}/bin/hex${CG_TOOL_SUFFIX}.exe" --ti_txt "${BuildArtifactFileName}" -o "${BuildArtifactFileBaseName}.txt" -order MS -romwidth 16 .
I have resolved the things you have said ,
But what about the rest of the option like , entry point and stuff ?
dose hex6x utility build with all the defaults ?

PS: Thanx a lot for the support , I really Appreciate it .

I dint get any errors or warnings ... but is that correct ?
btw ccsv5 dosnt not support dsk6455 , but is it okay to use hex6x utilitiy ?

Akash

Akash Mullangi said:

Hi Again ,
The command say "${CG_TOOL_ROOT}/bin/hex${CG_TOOL_SUFFIX}.exe" --ti_txt "${BuildArtifactFileName}" -o "${BuildArtifactFileBaseName}.txt" -order MS -romwidth 16 .
I have resolved the things you have said ,
But what about the rest of the option like , entry point and stuff ?
dose hex6x utility build with all the defaults ?

As I mentioned earlier, please read Chapter 11 of:

http://www.ti.com/lit/ug/spru186v/spru186v.pdf

It has all the details of the hex utility

Thanks

ki

4628.Untitled.tif

5554.Untitled.tif

Hi Ki ,Rafael,

How do i remove the offset ? using the utility ...?
Do I have to use the memory image option ?

Akash,

Flashburn is not a product from TI. Please visit the SDS site for more information on Flashburn.

http://www.softwaredesignsolutions.com/flashburn.aspx

Thanks

ki

Hi ki ,

Could you help me with this , I am not able to input the option to the hex6x utility file ...
The command that I used is :  hex6x -a L1_Wavlet.out -memwidth 8 -image ROMS { FLASH : org = 0xB0000000, len = 0x2000, romwidth = 8, files = {OM2.hex} }
Is there anything wrong in the order of the inputs ?
one last help ki ... I think ill be done :)

Thank you

Hi ki ,

Could you help me with this , I am not able to input the option to the hex6x utility file ...
The command that I used is :  hex6x -a L1_Wavlet.out -memwidth 8 -image ROMS { FLASH : org = 0xB0000000, len = 0x2000, romwidth = 8, files = {OM2.hex} }
Is there anything wrong in the order of the inputs ?
one last help ki ... I think ill be done :)

Thank you

Akash Mullangi said:

The command that I used is :  hex6x -a L1_Wavlet.out -memwidth 8 -image ROMS { FLASH : org = 0xB0000000, len = 0x2000, romwidth = 8, files = {OM2.hex} }
Is there anything wrong in the order of the inputs ?

The ROMS directive is not an option that can be specified on the command line. It needs to be inside a hex command file which is then passed as an option to hex6x. Please refer to the hex conversion utility details in the C6000 Assembly Language Tools Users Guide.

hi Aarti ,

I did try that in the first case with these parameters .

/*******************************************************************************
 * Copyright 2004-2005 - Software Design Solutions, Inc.  All rights reserved.
 *
 * Portions of this work have been provided under license with Texas
 * Instruments Inc.
 *
 * $RCSfile: BlinkDSK6455_hex.cmd,v $
 * $Revision: 1.1 $
 *
 * Creates an ASCII Hex formatted .hex file.
 *
 ******************************************************************************/

L1_Wavlet.out

-a

-memwidth  8

-image

ROMS
{
    FLASH: org = 0xB0000000, len = 0x2000, romwidth = 8, files = {"C:\Users\Sahil\Desktop\OM2.hex"}
}

pause

but it says invalid input ....

I did try this cmd line :

cd C:\ti\ccsv5\tools\compiler\c6000\bin
hex6x  --ascii "C:\Users\Sahil\Documents\AHM Target Models\L1_Wavlet_ticcs\L1_Wavlet.out" -o "C:\Users\Sahil\Desktop\OM1.hex" -order L -romwidth 8  
pause

I was able to generate the hex file.
Just that I was not able input the ROM options ......

Akash Mullangi said:

but it says invalid input ....

What is the exact error? I created a similar looking hex.cmd file (I removed the pause at the end) and was able to use it succesfully without errors. I simply run it as:
hex6x hex.cmd