CCS/F28M35H52C: Loading multiple executable causing failure

Steve,

Please check your map file to make sure that nothing went in to the security settings area in Flash sector A and sector N.  Check if you modified GRABSECT and/or other security settings.

What do you mean by erasing the sector would not validate the input you give?  Please explain clearly.  

Which gel file did you change to make it R/W and which entry in the gel file?  Please provide the detail.  Hope you are using the latest CCS.

Thanks and regards,
Vamsi

I had not checked the map file but the linker shouldn't have had anything be put into that space. unfortunately I likely would not be able to be able to exactly recreate the map file as i had made some alterations since the initial issue arose. As for the GRABSECT and other security options in the debug configuration settings I had not made any alterations to that. 

this was in reference to the memory fill tool in CCS. I was attempting to use it to write into the sector that was no longer functioning. when I filled in the inputs it requested it initially said that the memory map had prevented it from writing. which is what lead me to look at the memory map where it showed the M3 flash block as R only

I went to the f28m35h52c1_m3.gel file and altered this lin

    GEL_MapAddStr(0x200000,   0, 0x80000,    "R",   0);      /* FLASH BANK 1*/

to 

    GEL_MapAddStr(0x200000,   0, 0x80000,    "R|W",   0);      /* FLASH BANK 1*/

This solved the memory fill problem but then instead gave me the data validation error. 

the version of CCS being used is 6.2.0.00050 

Steve,

If not map file, you can directly check the security setting locations in the memory window and see what values are programmed in to them for both zone1 and zone2.  Even though you may not have made any changes in flash plugin GUI, sometimes any unmapped sections in the application may get mapped there.  Please check the memory window and let me know the values programmed for all the security settings.

Regarding the CCS memory window GUI memory fill option:  It won't work for flash space.  

Gel file:  Flash space is marked as R only.  It is not writable by debugger and hence is marked as R only.  When an application executable (.out) is loaded in CCS, if the memory range falls in R only area, then CCS will invoke flash programmer automatically to load to that memory range.  Hence, it is important to leave the flash/OTP space as R.

Thanks and regards,
Vamsi  

Vamsi, 

I have had a chance to hook up the board with the issue and look at the memory sections 

It seems as though the N sector has been altered. which is also the section that was having the erase issues. Are you saying that CCS will use any unmapped linker space as it sees fit? which also here happened to be the security settings?

can this be resolved?

Thank you for your help Vasmi. 

This solved the problem and addressed my concerns.