Hi jefft,
Thanks for you help.
-
I have gone back to FreeRTOS v8.2.3 and it happens to me the same.
I have tried to compile the old project without changes using FreeRTOS v8.2.3 and have the
same problem
I changed my PC a month ago and I tried to put the same Eclipse Compiler,using arm-none-
eabi-gcc compiler… but I am afraid that I have something wrong in my compiler.
When trying to compile for release: I am able to compile the problem but for being able to obtain the hex file “I have had to remove two keywords from the make file “-map” and “-info” and maybe there are important. but otherwise I get some problem”.
And if i try to compile for debug I see that the scheduller doesn’t start properly.
unfortunately I am not able to recover my last configuration, as I haven’t got my old PC anymore…
- Refering to what you are talking about MSP
I have the following code at my main.c
/* Allocate two blocks of RAM for use by the heap. The first is a block of
0x10000 bytes starting from address 0x80000000, and the second a block of
0xa0000 bytes starting from address 0x90000000. The block starting at
0x80000000 has the lower start address so appears in the array fist. /
const HeapRegion_t xHeapRegions[] =
{
{ ( uint8_t * ) 0x20002710UL, 0x1CCF0 }, // 118K
{ ( uint8_t * ) 0x68000000UL+XRAM_OFFSET, 0x1C000 }, // 112K
{ NULL, 0 } / Terminates the array. */
};
/* Pass the array into vPortDefineHeapRegions(). */
vPortDefineHeapRegions( xHeapRegions );
/* Relocate Vector Table in the FW address 0x08060000 0x08040000, after BOOT area */
NVIC_SetVectorTable(NVIC_VectTab_FLASH, MAP_OFFSET); //0x60000 0x40000
NVIC_PriorityGroupConfig(NVIC_PriorityGroup_4);
where I hope I tell the Compiler where is place my vector table:
NVIC_VectTab_FLASH 0x08000000
MAP_OFFSET 0x00060000
so I think that should be right?
I am including here my compiler configuration …just in case you could find something wrong…
HW_UES_ENCODER_FP1.7z (12.2 KB)
Any more information please ask
Thanks a million
kind regards
Natalia