This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

High RAM Application Questions

According to the *.map file the .bss (RAM) usage for my Application is 0x16b8 or 5816 bytes. This is obviously a very high RAM Application, likely due to the abundance of app_timers I use. I am using SDK6.1 and SD7.1. I want to make sure I'm not going to run into RAM issues at RUN-TIME. With this RAM spec in the .map file do I need to modify the gcc_startup_nrf51.s ? Or modify any other files to account for this RAM usage? Any other considerations I should be mindful of? Thank you for your advisement Nordic.

-DC

Parents
  • Don't totally understand the question. If the app links without error and fits in the available space, it works, the link script has a check for this. The startup file is entirely generic and just copies things from one place to another, it doesn't matter if it copies 1 byte, 10 bytes or 16Kb.

    What issues were you concerned about, perhaps I'm just missing the point?

    That is a lot of RAM usage, the map file should tell you what it's all used for, although they're annoyingly tricky to read, you might want to confirm to yourself that it is app timer usage (they use that much??) and not something else.

  • Unforuntely we cannot get stack traces as there is a power-cycle uponing access the SWD pins. I believe the issue may again be related to the Scheduler. We use BLE event to trigger scheduler events. These events start app_timers. It is likely a condition where several BLE events (Stack uses the scheduler as well) causing several scheduler events which somehow fills up the Scheduler Queue and then odd things happen. I don't really know how to design around this. I cannot increase the Scheduler Queue anymore without RAM overflows.

    When using app_timers with the scheduler, do app_timer_start and app_timer_stop use the scheduler as well? or just the timeout_handler? Trying to track down how I could be filling up the queue.

    Thanks for the help guys.

    -DC

Reply
  • Unforuntely we cannot get stack traces as there is a power-cycle uponing access the SWD pins. I believe the issue may again be related to the Scheduler. We use BLE event to trigger scheduler events. These events start app_timers. It is likely a condition where several BLE events (Stack uses the scheduler as well) causing several scheduler events which somehow fills up the Scheduler Queue and then odd things happen. I don't really know how to design around this. I cannot increase the Scheduler Queue anymore without RAM overflows.

    When using app_timers with the scheduler, do app_timer_start and app_timer_stop use the scheduler as well? or just the timeout_handler? Trying to track down how I could be filling up the queue.

    Thanks for the help guys.

    -DC

Children
No Data
Related