Hi,
I'm writing a C++ program that will run on an STM3210E-EVAL board and I'm having some problems using STL vectors. I'm wondering what I'm doing wrong. (Or if STL vectors are even supported.)
Here's a snippet:
#include <vector> . . . void func() { std::vector<int> temp; temp.push_back(5); }
When I try to run the debugger on my target, I end up somewhere in assembly land and never reach the beginning of my main() function. (I am not familiar with assembly so, I'm not quite sure where I am or how I got there.)
When I run in simulator mode, everything works fine. (I end up at the beginning of my main() function like I expect.)
It appears that whenever I make any command that increases the size of my vector, I get the same result. If I never insert into my vector or resize it, then the debugger brings me to the beginning of main(), like I'd expect.
The last time I saw something like this was when my heap was 0 and I tried newing something on the heap. If anyone has any ideas, I'd be grateful.
I'm required to write my program in C++ and though I'm not required to use vectors, I really would like to. (I also have a few ideas of how to implement it differently if it turns out that vectors don't work.)
Thanks,
Alright, I added the clock configuration:
void RCC_Configuration(void) { /* RCC system reset(for debug purpose) */ RCC_DeInit(); /* Enable HSE */ RCC_HSEConfig(RCC_HSE_ON); /* Wait till HSE is ready */ HSEStartUpStatus = RCC_WaitForHSEStartUp(); if (HSEStartUpStatus == SUCCESS) { /* Enable Prefetch Buffer */ FLASH_PrefetchBufferCmd(FLASH_PrefetchBuffer_Enable); /* Flash 2 wait state */ FLASH_SetLatency(FLASH_Latency_2); /* HCLK = SYSCLK */ RCC_HCLKConfig(RCC_SYSCLK_Div1); /* PCLK2 = HCLK/2 */ RCC_PCLK2Config(RCC_HCLK_Div2); /* PCLK1 = HCLK/2 */ RCC_PCLK1Config(RCC_HCLK_Div2); /* PLLCLK = 8MHz * 9 = 72 MHz */ RCC_PLLConfig(RCC_PLLSource_HSE_Div1, RCC_PLLMul_9); /* Enable PLL */ RCC_PLLCmd(ENABLE); /* Wait till PLL is ready */ while (RCC_GetFlagStatus(RCC_FLAG_PLLRDY) == RESET) {} /* Select PLL as system clock source */ RCC_SYSCLKConfig(RCC_SYSCLKSource_PLLCLK); /* Wait till PLL is used as system clock source */ while (RCC_GetSYSCLKSource() != 0x08) {} } /* Enable peripheral clocks ------------------------------------------*/ /* GPIOA, GPIOB and SPI1 clock enable */ RCC_APB2PeriphClockCmd(RCC_APB2Periph_AFIO, ENABLE); }
And I still have the same problem.
* are you getting any linker warnings? No.
* did you verify the layout of your flash through your map file? is everything that is involved in startup where is should be (reset vector, jump to __main, etc.)...? Uh... I'm not quite sure what I should be verifying... I have the default startup code if that's what you're asking about. (Except for a change in stack size and heap size.)
* are your clocks configured correctly? Oh, they're not configured at all... Let me go set some values and see if that helps. How would I know if they are "correctly" configured?
If they're not configured at all, would it still allow some programs to run and others not to? (Or is it undefined behavior?)
* maybe it is your watchdog (unlikely...)? How would I verify if it was or not?
* stack size? Stack Size = 0x200, Heap Size = 0x200.
* interrupt that occurs immediately after startup but is not handled...? I haven't enabled any interrupts yet in my program. Is there still a chance that it's caused by an interrupt?
* are you getting any linker warnings? * did you verify the layout of your flash through your map file? is everything that is involved in startup where is should be (reset vector, jump to __main, etc.)...? * are your clocks configured correctly? * maybe it is your watchdog (unlikely...)? * stack size? * interrupt that occurs immediately after startup but is not handled...? * ...
Yes, I'm aware that dynamic memory allocation while the system is running is bad. I plan on preallocate everything in the beginning. I would just like a solution that will be easily readable when I'm done.
Thank you for your tip though.
I haven't tested, so I can't really help with your problem.
But think twice about dynamic memory in an embedded application. The stl implementation may be leak-free, but not free from possible memory fragmentation.
And unless you preallocate everything, you can't test your code and know that it will also work out in the wild. With dynamic memory, the sequence and the quantity of allocations will matter, creatly increasing the number of permutations in how your program may fail.
View all questions in Keil forum