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/TMS320F28027F: serial flash programming questions

Part Number: TMS320F28027F
Other Parts Discussed in Thread: CONTROLSUITE, C2000WARE, MOTORWARE

Tool/software: Code Composer Studio

With my custom hardware I've been able to verify proper SCI communications and I'm now in the process of testing serial programming using c2prog program from a hex file generated by hex2000 utility within CCS.  Using the hex2000 options = "C:/ti/ccsv6/tools/compiler/c2000_15.12.3.LTS/bin/hex2000" --map="MyProgram.map" --memwidth=16 --romwidth=16 --intel -o "MyProgram.hex"  "MyProgram.out",  I am able to successfully program my device with the C2Prog window as follows;

*** PLEASE RESET TARGET IN SCI BOOT-LOADER MODE ***
Connecting with target (autobaud)... OK.
Bootloading... OK.
Please wait...
Connecting with target...
-Chip ID: 0xCF
-Chip Rev: 0x02
OK.
Unlocking target... OK.
Loading... OK.
Connecting with target...
-Flash API version: 200
OK.
Erasing flash... [ABCD] OK.
Programming... OK.

You may now close this window and reset the target.

After this i power down and set GPIO34 & GPIO37 =1 & TRST=0.  But on power up the device does nothing and I do not see the LED blink as it should in normal operating mode.  I assume I must be missing something in my process here?  

  • Hi Skip,

    Is this the example LED blink code from controlSuite/C2000ware? If so they're RAM based code and not Flash Based.

    Regards,
    Gautam
  • It's a modified version of Motorware lab10a.

  • So does this code load to flash or RAM? Check the cmd file.
  • I was able to determine the issue after reconnecting the jtag debugger.  To test my uart connection I followed section 6.7 in the motorware_hal_tutorial.pdf using the ISR setup as outlined.  In the process of verifying the uart communication was working I overlooked the fact that by adding this ISR it disables functionality of the lab itself along with the LED blinking.  I was under the assumption that by adding this function that it wouldn't disable the functionality of the lab as well unless I missed something which is very well possible as I'm pretty new to this.

    Having verified that I can update flash through SCI-A using C2prog I have some other questions.

    1.  My end goal is to have a windows gui that detects which firmware version is currently on the device and then update if necessary through the usb to rs232 connection I'm using (no jtag).  So if I'm correct, my options are to purchase the C2prog professional license to get access to their dll interface or end up writing up my own interface?  If we write our own, I came across a post that is somewhat dated that recommended documentation not directly meant for this mcu but described the basics of what is needed.  Is this still the recommended documentation?

    e2e.ti.com/.../287234