Skip to content

Conversation

@meijemac
Copy link
Contributor

Woraround that sends a second vevif SW trigger. It seems that SCFW does not always catches each vevif IRQ - therefore a second time the vevif task will be triggered as a temporary workaround.


nrfy_vpr_task_trigger(config->vpr, nrfy_vpr_trigger_task_get(id));

k_busy_wait(VEVIF_RETRIGGER_DELAY);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

#include <zephyr/kernel.h> missing for k_busy wait

Copy link
Member

@gmarull gmarull left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why is this a noup?

@meijemac
Copy link
Contributor Author

why is this a noup?

Don't know what it should be - for the moment this is a workaround so that we can make a SDSC release. We are still investigating and we hope to find the root cause - so that we can elimate this workaround.

@meijemac meijemac force-pushed the vevif_tx_double_trigger branch from bc6a722 to 392c2f4 Compare February 27, 2025 10:21
@meijemac meijemac force-pushed the vevif_tx_double_trigger branch from 392c2f4 to 733703d Compare February 27, 2025 12:39
Copy link
Contributor

@57300 57300 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, assuming a noup is acceptable until the root cause of HM-25973 is found

@meijemac meijemac force-pushed the vevif_tx_double_trigger branch 2 times, most recently from 8784712 to 2fa8450 Compare February 28, 2025 09:25
When a LD sends an ic-msg to SCFW - it happens that sometimes that SCFW
does not handle the request.
For the moment the problem is solved by sending a second vevif event
shortly after the initial request.

Upstream PR #: 86455

Signed-off-by: Maciej Meijer <[email protected]>
@meijemac meijemac force-pushed the vevif_tx_double_trigger branch from 2fa8450 to 27f863e Compare February 28, 2025 12:48
@rlubos rlubos dismissed gmarull’s stale review February 28, 2025 14:44

The commit is no longer noup

@rlubos rlubos merged commit 3850f28 into nrfconnect:main Feb 28, 2025
17 checks passed
@shanthanordic shanthanordic added the backport v3.7.99-ncs3-branch Relates to NCS v2.9-nRF54H20-branch label Feb 28, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

backport v3.7.99-ncs3-branch Relates to NCS v2.9-nRF54H20-branch

Projects

None yet

Development

Successfully merging this pull request may close these issues.

10 participants