• State TI Thinks Resolved
  • Locked Locked
  • Replies 5 replies
  • Answers 1 answer
  • Subscribers 54 subscribers
  • Views 1784 views
  • Users 0 members are here
Support feedback
Options
Options
Similar topics

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.

CortexR5: File Loader: Memory write failed: Unknown property "FlashBlankCheckToggle"

Dan K87420
Intellectual 630 points

I upgraded my computer, re-installed CCSV6, am able to build my 'old' projects, but when I try to debug, I get -

CortexR5: File Loader: Memory write failed: Unknown property "FlashBlankCheckToggle"

This is driving me bananas.  What is broken and how do I fix it?

  • 0
    Intellectual 630 points
    FYI, was CCSV6.0, is CCSV6.1, have tried all the various recent arm compiler releases.
  • 0 in reply to Dan K87420
    TI__Expert 4695 points

    Dan,
    Looks like the issue is in C:\ti\ccsv6\ccs_base\DebugServer\propertyDB\TMS570xC_RM57_4MB_FlashProperties.xml.

    The FlashBlankCheckToggle property id is commented out.
    Remove the comment out operators "<-- ! till --> to include this function.

    Also I see have a different action than the other devices at the end of the file and should be updated as well

    Replace the three instances of BankToggle# <0, 1, and 7>
    <action>DPActiveDebugSession.flash.performOperation("BankToggle0")</action>
    With
    <action>for( var i = 0; DPActiveDebugSession.options.optionExist( "FlashBank0Sector" + i ); ++i ) { DPActiveDebugSession.options.setBoolean( "FlashBank0Sector" + i,!DPActiveDebugSession.options.getBoolean( "FlashBank0Sector" + i ) ); }</action>

    Regards,
    Forum Support

  • 0 in reply to Dave Livingston
    TI__Genius 11645 points

    Dan,

    Can you pls close this thread if Dave's suggestion works for you.

  • 0 in reply to KARTHIKEYAN RAJAMANICKAM
    Intellectual 630 points

    I think it turns out that I just had version issues.  When my old laptop was turned in and I did a fresh install of CCS and went from 6.0.1.00040 to 6.1.0.00104, this is when I discovered issues, including what initiated this forum post.  I backed up a version and things seemed to get resolved (but not without a lot of fooling with settings).  I looked at the version change notices (high level, not deep dive) between 040 and 104 but didn't see anything relevant.  But I think there might be.  Any insight from you guys regarding the version update path in terms of debug files?  If so, it should be clearly pointed out.

    Thanks,

    Dan

  • 0 in reply to Dan K87420
    TI__Genius 11645 points
    Hello Dan,

    Probably someone from CCS forum might help with this. So I'm moving this thread to CCS Forum.