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/TMS320F28335: tms320f28335

Part Number: TMS320F28335
Other Parts Discussed in Thread: C2000WARE

Tool/software: Code Composer Studio

Hi my question is about “how to load application to FLASH RAM without emulator by SCI Boot loader.”

The documents I have referred are “Serial Flash Programming of C2000™ Microcontrollers “and “TMS320x2833x, 2823x Boot ROM Reference Guide “.

I’ve already checked hardware system I set for SCI communication with SCI echoback example code by TI. SCI communication goes well with my F28335 so it doesn’t seems to be have any issues on the hardware setting.

My F28335 communicates with PC host through RS232 protocol.

 

The photo below is the issue I have faced and i am unable to solve it out.

I am guessing I put the wrong argument onto command argument inbox that can be found at “debugging tag” of Serial flash programmer property. The line below is the argument i gave.

-d f2833x

-k C:\ti\c2000\C2000Ware_1_00_06_00\device_support\f2833x\examples

\f28335_flash_kernel\Debug\f28335_flash_kernel.txt

–a E:\CCS_Project\practice_v3.0\Debug\practice_v3.0.txt

-p COM4

-b 9600

The reason I did those things above is because I referred the line 6 and 7 of “6.2.2 Building serial_flash_programmer in Visual Studio” in the document “Serial Flash Programming of C2000™ Microcontrollers".

As the document I have mentioned above explains how to convert the .out file to .hex file at “6.1.1 Kernels” in the document mentioned above, i followed it with uncertainty.

I enabled the hex2000 utility for f28335 flash kernel example in CCS and set my project property as below with a hope that I did well to produce the hex file required for SCI boot loader.

It is said the format must be in the ASCII SCI boot format, which is why I check the square boxes as the photos above.

I gave the same options to my project targeted to be load in FLASH RAM.

 

After the setting above from ehx2000 utility, I could see hex file. I changed the .hex extension to .txt because of the description of “6.1.1 kernels” section. “f28335_flash_kernel.txt and “practice_v3.0.txt” are the extension modified files I got after build process.

 

I have checked the boot mode select pins (GPIO 87, 86, 85, and 84). I set them for the boot by SCI loader so there seems to be no any problem.

 

Thanks for your patience and your sincere answer on my question I appreciate!

  • Hi,

    Theh f2833x option is missing from the command line options. Please use f2806x or f2805x or f2803x or f2802x instead. The serial flash programmer behaves the same way for all of these devices.

    Also, please close the other thread which is a duplicate of this one.

    Also, please search the E2E forum for related questions.

    Thanks,
    sal
  • thanks for your quick reply SAL! 

    i did what you had suggested me however it didn't work well. 

    the command line i gave is below. 

    serial_flash_programmer.exe -d f2802x -k C:\Users\ysshim\Desktop\my_code\f28335_flash_kernel.txt -a C:\Users\ysshim\Desktop\my_code\practice_v2.0.txt -p COM4 -b 9600

    when i tried with this command line, what i saw on prompt screen is below

    It just stopped at the line “Downloading C:\User\ … “and went on next step.

    And I noticed that during building process, with hex2000 utility on with the options I set – the option can be checked at the photo I posted on my first question –

    F28335_flash_kernel example project provided by TI produced the .text file in ASCII SCI8 fortmat automatically but my project didn’t.

    so now I am guessing it is because my project missed any header and source file or library.

     

    The photos below show the sources and headers included in my project that I tried to load into FLASH.

    I eager to learn how to solve this problem SAL. I know you have the key answer brother!

     

  • Please clarify your question.

    First, make sure your post-build steps are the same for your application as for the kernel.

    Second, make sure you are booting to SCI boot mode and also using the right SCI pins for communication.

    I will likely not be able to respond until next week if you have further comments or questions.

    sal