F28335 how to program in and load from flash?

Ok, so there is a flash example code for ezdsp that I found. So if I do these steps, with it solve my problem?

1) Delete current cmd file and copy and paste the cmd file from the flash example.

2) Add the DSP2833x_CSMPasswords.asm and DSP2833x_MemCopy.c from flash example to my project

3) Add these lines of code to my code:

extern Uint16 RamfuncsLoadStart;
extern Uint16 RamfuncsLoadEnd;
extern Uint16 RamfuncsRunStart;

                        MemCopy(&RamfuncsLoadStart, &RamfuncsLoadEnd, &RamfuncsRunStart);

                        InitFlash();

With this do the trick?

Muhammad,

In general, you cannot necessarily just paste a few files from a working example into your code and expect everything to work.  The .cmd files in SPRA958 have named sections in them that are used in the source code.  You would need your code to use the same named sections.  Also, copying a couple of DSP2833x_XXXXXX files from the SPRA958 example to your code is going to mix up the revisions of the peripheral header files.

What you should do is review the appnote, and then make the changes to your project.  Alternately, if it were me, I would take the flash nonBIOS example in SPRA958 and modify the source code to do what I want.  For example, modify the adc.c file as desired, delete ePWM.c and eCAP.c, etc.  Customize to do what you want.  That way, the project is already setup for flash operation.

Note that DSP2833x_MemCopy.c is a custom version of a memory copy routine.  The code in SPRA958 does not use it.  Rather, it uses the regular memcpy() function in the RTS compiler library.  Personally, I think the RTS lib function is a better way to go.  The custom version MemCopy() doesn't offer anything special.  It is just a re-write of the RTS version with a different set of passed parameters.

Regards,

David

David,

What is the location for DSP2833x_MemCopy.c ? I downloaded SPRA958 but did not find this file in any of the project folders. My project constraints do not allow outside party libraries, so

this file is of interest.

Thank you,

Chuck

Chuck,

DSP2833x_MemCopy.c is part of the peripheral header files that the C2000 applications team produces.  It can be found in ControlSuite, here (for example):

C:\TI\controlSUITE\device_support\f2833x\v133\DSP2833x_common\source

Realize that the source code for the compiler RTS library is included with the compiler however.  You could grab the source code for the functions you want from the library and use the source in your project instead of the .lib file.

Regards,

David

Hi Mohammad,

What you can do is use the flash project itself and paste your custom code in its main.c file. This is the easiest option.

Regards,

Gautam

David,

I am trying to modify the F28335_nonBIOS_flash example code to utilize the FLASH2833x_API.

My goal is the run one program from flash after power up. The "bootloader" will read

data serially via SPI and flash the data into a designated flash sector not being used. The bootloader will check

the integrity of the flashed data and then move into another flash sector to run in flash upon power reset.

When I try to compile this line of code I get a type error:

// Copy the Flash API functions to SARAM

memcpy(&Flash28_API_LoadStart, &Flash28_API_LoadEnd, &Flash28_API_RunStart);

Description Resource Path Location Type
#169 argument of type "Uint16 *" is incompatible with parameter of type "unsigned long" Main_nonBIOS.c /F28335_example_nonBIOS_flash/src line 46 C/C++ Problem

It appears memcpy is expecting an Uint16 but &Flash28_API_LoadStart is Uint32.

Any ideas why this is happening? I thought the memcpy routine was needed for the Flash28_API.

-Chuck

Charles,

I assume the memcpy() you are calling is the one from the compiler RTS library.  If that is the case, then the parameters you are passing it are incorrect.  The function prototype for memcpy() is:

 void memcpy(void *dst, void *src, Uint32 n);

So you want to call it like this:

memcpy(&Flash28_API_RunStart, &Flash28_API_LoadStart, (Uint32)&Flash28_API_LoadSize);

or if you do not have the LoadSize parameter generated by the linker .cmd file, you could do this:

memcpy(&Flash28_API_RunStart, &Flash28_API_LoadStart, (Uint32)&Flash28_API_LoadEnd - (Uint32)&Flash28_API_LoadStart);

Note that the example shown in the Flash API User's Guide is NOT using the memcpy() from the RTS library.  It is using it's own memcpy() function called Example_MemCopy().  This function is given in the API User's Guide.  Personally, I use the one in the RTS library.

Regards,

David

David,

We figured out our issues. The code we want to run from Flash Sector C has to have its linker.cmd set up to

have BEGIN_FLASH to point to the first two bytes of Sector C. We are able to convert the .out file into a binary

using hex2000. The main program has an inline branch instruction that directs the code to run at the beginning

of Sector C. When we debug the main program using the emulator, we de-select flash sector C for erasing and this

allows the binary file we uploaded to remain in flash.

To be clear, our method is to have the main program linker cmd file to have BEGIN_FLASH at the first two bytes

of Sector A, which is the factory setting, and the Flash code to have its linker command file to have BEGIN_FLASH at the first two bytes of Sector C.

There are details involving the hex.cmd file used to create the binary image with hex2000, but they are minor details.