• State
  • Locked Locked
  • Replies 2 replies
  • Subscribers 81 subscribers
  • Views 802 views
  • Users 0 members are here
Support feedback
Options
Options
Related

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.

reposting a problem with flash programming of the c28 on concerto

Pat Harris
Genius 3890 points

Refreshing this post for better attention. Thanks for any input.

 

Reposted from TI-RTOS concerning flash boot programming...

I only need to boot the cm3. I download the app upgrade code from a communication network that the c28 controls. I transfer the code through the IPC and first store it into high flash on the cm3 side, using the falsh programming tools. Next I attempt to transfer the code from the high flash memory location down to 0x200000.

I have not had much luck in doing this. It appears that the ramfuncs code does not get overwritten (works until I cycle power).  I believe I could get it to work if I fix the boot up location and then only transfer the app code minus the ramfuncs. How do I determine the location of the c_int00() startup location and how do I fix it in memory? Any other suggestions as to how to overcome this / solve the flash code transfer problem would be helpful. I have had zero luck trying to set breakpoints in RAM with the debugger. The XDS560V2 does not support trace on the Concerto.

CCS5.4, Concerto f28m35h52c1, XDS560V2 STM USB are what I am using.

Thanks,

Pat

TI-RTOSEdit tags
PoorPoorFairFairAverageAverageGoodGoodExcellentExcellent
Report Abuse
Edit
Delete
All Replies
  • Pat Harris
    Posted by
    onNov 12 2013 09:33 AM
    Expert2970 points

    Follow up:

    I don't have the problem with the V140 example dual blinky. The differences seem to be the addition of the HWBistRegsFile. What does this file do?

    Thanks,

    Pat

    Edit tags
    Did this answer your question?Yes
    Report Abuse
    Edit
    Delete
  • Pat Harris
    Posted by
    onNov 12 2013 10:24 AM
    Expert2970 points

    Further info:

    The difference is in the map file. The .cmd files are identical. The V200 has the HWBistRegsFile included whereas the V140 does not. I understand that this is a self test feature. How could this be causing the C28 failure to run? What is the work-around for this problem?

    Thanks,

    Pat

  • 0
    Genius 3890 points

    I think some info was lost.

    Here's the current problem:

    I can load the dual blinky example, V140, using CCS5.4. The c28 compiler is V6.1.5. This will run in debug mode as well as after power cycle.

    But V200, using compiler 6.1.5, will download to both, but only the cm3 side will run regardless if I am in debug mode or after power cycle. V200 has additional code :

    #ifdef __cplusplus

    #pragma DATA_SECTION("HWBistRegsFile")

    #else

    #pragma DATA_SECTION(HWBistRegs,"HWBistRegsFile");

    #endif

    volatile struct HWBIST_REGS HWBistRegs;

    in the file F28M35x_GlobalVariableDefs.c. Removing this code and re-running the test made no difference. There is apparently something else that is different, but using WinMerge did not show any other changes in the source or .cmd files.

    This problem is preventing my application from running. I need some help with this please.

    Thanks,

    Pat