Hi there, I want to ask about Intel Integrated Sensor Solution FDK IDE and some contradicting ideas from its guide:
1) Automatically Maintained Code
The built-in user guide suggests to never "manually edit the files in the auto_generated_code folder. Any changes you introduce will at best be overwritten, and at worst render your sensor permanently unusable."
2) Getting event notifications from CS state change (i.e. enter/exit ModernStandby)
The built-in user guide shows steps how to do this for a virtual driver:
◦In its init callback, add notification mask SC_NOTIFY_HOST_OS_STATE_CHANGE_CS to algo_create_sensor function’s forth parameter.
◦In its init callback, call algo_register_notify_event_callback(context, &xxx_notify_handler) to register your notification handler.
◦In xxx_notify_handler, handle host CS state change as below:
sc_status xxx_notify_handler(INOUT algo_context *context,
INOUT void *private_data,
IN sc_event_notification_event_id event_id,
IN sc_event_info event_info)
if (event_id == SC_NOTIFY_HOST_OS_STATE_CHANGE_CS)
if (event_info.sc_notify_sensor_sys_state.system_state_statuses & SYS_STATE_CONNECTED_STANDBY)
// Enter connected standby, add your code
//Exit connected standby
Problem: The functions algo_create_sensor and algo_register_notify_event_callback are already used in the auto generated code portion of the project, attempting to change this auto_generated code violates Guide #1 Premise, and attempting to do first and second bullet of Guide #2 consequently will require modification in auto_generated code. This poses a dilemma because we want to implement notification of CS State Change, but we do not want to modify any part of the auto generated codes.
We would like to hear your suggestions that would best resolve this issue.
Thank you and regards,
Thank you for contacting Intel Embedded Community.
We want to address the following questions:
Could you please let us know the part number of the processors related to this situation?
What is the procedure that you have followed to obtain the software related to this situation? Please mention its version.
Hi @CarlosAM_INTEL ,
It appears we have a way to raise this concern to Intel internally, and I have been advised to take it there instead of discussing the matter in public. Sorry for the inconvenience, but thank you for your prompt response.