-
Notifications
You must be signed in to change notification settings - Fork 3k
Fhss timer dev #8478
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fhss timer dev #8478
Conversation
@mikter @juhhei01 @SeppoTakalo @kjbracey-arm please review |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
/morph build |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, just a non-blocking question.
|
||
static int platform_fhss_timer_stop(void (*callback)(const fhss_api_t *api, uint16_t), const fhss_api_t *api) | ||
{ | ||
(void)api; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this only to prevent compiler warnings?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes.
Also, what does FHSS stand for? |
Build : FAILUREBuild number : 3432 |
Strange. @JarkkoPaso would you mind reproducing the IAR error locally? I'm actually kinda surprised that this appears to be causing a linker failure. |
It seems that LPC4088/LPC4088_DM RAM region is too small in IAR build. RAM region is 64k and IAR linker is setting cstack size to 8k and heap size to 16k. Should we reduce the cstack and/or heap size or remove this target? @SeppoTakalo any comments? |
cstack should be set to 1K, that should help |
/morph build |
So this is kind of pending #7238 but that does not seem to progress very well. |
Build : SUCCESSBuild number : 3440 Triggering tests/morph test |
Exporter Build : FAILUREBuild number : 3061 |
That's frustrating. A 1GB error log (that could only reasonably be navigated through with Linux tools), and there are no good details on why mbed-os-example-blockdevice was unable to build. Going to restart in the hopes that this was a fluke. |
Exporter Build : SUCCESSBuild number : 3067 |
return read_current_time(); | ||
} | ||
|
||
fhss_timer_t fhss_functions = { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This should be const
to save RAM. But not seeing where this is declared, so where else you'd need to change.
#define NUMBER_OF_SIMULTANEOUS_TIMEOUTS 2 | ||
#endif //NUMBER_OF_SIMULTANEOUS_TIMEOUTS | ||
|
||
static Timer timer; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Follow-up job, as I failed to review earlier:
I would expect that timer
and fhss_timeout
would need to use SingletonPtr
to avoid increasing static RAM size for people not using Nanostack. Otherwise they'll always be pulled in just to run the constructors.
Although SingletonPtr can't really handle an array :( Might end up having to just new
fhss_timeout
.
(Is there a CI job monitoring size increases for blinky or something?)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think so. I think the other @kegilbert, @studavekar, or @SenRamakri should know tho.
Description
Implemented FHSS timer driver for mbed-os targets.
Tested locally with K64F and Nucleo-F429.
Pull request type