- Ask a related questionWhat is a related question?A related question is a question created from another question. When the related question is created, it will be automatically linked to the original question.
Tool/software:
Hi Team,
As my code size increased, the memory bank .sysmem : > RAMLS5 got exhausted. So, I changed the initial setting from .data : > RAMLS5 to .data : > RAMLS6.
After this change, the function call:
Flash_initModule(FLASH0CTRL_BASE, FLASH0ECC_BASE, DEVICE_FLASH_WAITSTATES);
started hitting the __error__() handler:
void __error__(const char *filename, uint32_t line)
{
// ASSERT condition failed. Use filename and line to debug.
ESTOP0;
}
What could be the root cause of this issue, and how can I resolve it?
Added initial error snip below .
After changing .data 
Another strange point is I also tried with increase the length of RAMLS5 , from length = 0x000800 to length = 0x001800, It started working . But when I add more buffers as my application need, then it again started going into
__error__() handler:
Hi,
Have you aligned your data buffer secion with ALIGN directive?
Regards,
Rajeshwary
Hi Rajeshwary,
Thanks for the response.
C2000 sdk device_init() function call have Flash_initModule(FLASH0CTRL_BASE, FLASH0ECC_BASE, DEVICE_FLASH_WAITSTATES) inside it .
You are suggesting to comment out it ?? But when buffer size is less same call was working good .
By commenting out Flash_initModule(FLASH0CTRL_BASE, FLASH0ECC_BASE, DEVICE_FLASH_WAITSTATES) also return same error .
Can you check the filename and line number from where it is going to _error_()?
Yes,
"filename char * 0x00090196 "/home/ubnu..." Register XAR4
line unsigned long 33 Register AL
"
But this is very unclear .
If you want I can provide previous version, current version of my code .where I only added more buffers of size 256 .
Initially I used single buffer of 256 as I am testing for single phase, that time same program was working fine.
Then as my application require 3 phase , i simply added 2 more buffer with 256 sizes. After that same issue started .
I found by debugging more deep in working program when from device.c function call Flash_initModule(FLASH0CTRL_BASE, FLASH0ECC_BASE, DEVICE_FLASH_WAITSTATES) passing values of cntrlbase and ecc base as defined in .h file like below.
#define FLASH0CTRL_BASE 0x0005F800U
#define FLASH0ECC_BASE 0x0005FB00U
But in new program ctrlBase and eccBase passed as 0x0000F800 and 0x00000000 .
Most of the base addresses of memory and peripherals from HW_MEMMAP_H were affected in runtime after the function call of memcpy(&RamfuncsRunStart, &RamfuncsLoadStart, (size_t)&RamfuncsLoadSize);
Regards,
Ramakrishna
