Skip to content
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

update new mode to post-sensor mode #431

Merged
merged 4 commits into from
Jan 2, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions sdk/app_cpu1/common/drv/timing_manager.c
Original file line number Diff line number Diff line change
Expand Up @@ -172,10 +172,10 @@ uint32_t timing_manager_get_trigger_count(void)
/*
* Specify the interrupt source of the scheduler ISR:
*
* Mode 0 uses the timing manager's 'trigger' signal, i.e. the control
* Mode 0: legacy mode - uses the timing manager's 'trigger' signal, i.e. the control
* frequency is based on the PWM carrier frequency and the user-specified PWM sub-ratio.
*
* Mode 1 uses the timing manager's 'all_done' signal, calling the scheduler
* Mode 1: post-sensor mode - uses the timing manager's 'all_done' signal, calling the scheduler
* when all the sensors are done with acquisition. When no sensors are enabled,
* the scheduler is called as in mode 0 (based on the trigger). This mode
* supports reporting of the timing for each sensor
Expand Down
2 changes: 1 addition & 1 deletion sdk/app_cpu1/user/usr/user_config.h
Original file line number Diff line number Diff line change
Expand Up @@ -12,7 +12,7 @@
// Specify the source of the scheduler ISR
// Mode 0: legacy mode - scheduler is triggered based on the PWM carrier events and ratio
// of carrier frequency to desired control frequency
// Mode 1: new mode - scheduler is triggered when all the enabled sensors are done
// Mode 1: post-sensor mode - scheduler is triggered when all the enabled sensors are done
// acquiring their data
#define USER_CONFIG_ISR_SOURCE (0)

Expand Down