EnableAutoupdate
Should not matter...order wise other than after initstack...
MOD54415 Startup Time
-
- Posts: 67
- Joined: Thu Apr 21, 2011 7:06 am
- Location: Pittsburgh, PA
Re: MOD54415 Startup Time
Thanks for all your help so far, but I think it might be none of the above.
Of the 64MB of RAM for the device, I allocate 63MB as sort of a big heap for some other operation:
unsigned long all_memory[15615072];
When I change that to:
unsigned long all_memory[1];
it boots up super-fast.
Do you have any suggestions? Would malloc or memalign be a better way to go than declaring it in code?
Thanks, Dan
Of the 64MB of RAM for the device, I allocate 63MB as sort of a big heap for some other operation:
unsigned long all_memory[15615072];
When I change that to:
unsigned long all_memory[1];
it boots up super-fast.
Do you have any suggestions? Would malloc or memalign be a better way to go than declaring it in code?
Thanks, Dan
Re: MOD54415 Startup Time
Static global memory gets zerored...
Hummm I can fix this by adding an attribute and editing the linker script...
alas I'd rather not have to have you modify the linker script.
One of will get back to you... probably monday...
For now just do a malloc... (I dislike malloc's in embedded systems.)
Hummm I can fix this by adding an attribute and editing the linker script...
alas I'd rather not have to have you modify the linker script.
One of will get back to you... probably monday...
For now just do a malloc... (I dislike malloc's in embedded systems.)
Re: MOD54415 Startup Time
This is one way to do this...
https://mcuoneclipse.com/2014/04/19/gnu ... -variable/
https://mcuoneclipse.com/2014/04/19/gnu ... -variable/
-
- Posts: 67
- Joined: Thu Apr 21, 2011 7:06 am
- Location: Pittsburgh, PA
Re: MOD54415 Startup Time
Thanks again, I'll give that a try. I did do the malloc, though, and that seems to be OK for now. I'm with you, on an embedded platform I'd rather have everything predefined.