* Jenkinsfile loads CI_LIB@v2.6-branch
* 99-default-test-nrf.yml loads v2.6-branch of test-fw-nrfconnect-nrf

Signed-off-by: Thomas Stilwell <Thomas.Stilwell@nordicsemi.no>

We need to ensure that the BLE provider doesn't exist on the
recovery list to avoid putting it there once again.

Signed-off-by: Arkadiusz Balys <arkadiusz.balys@nordicsemi.no>

This commit increases number of available packet buffers in the system.

Signed-off-by: Łukasz Duda <lukasz.duda@nordicsemi.no>

If user selects a band, then we should restrict scanning channels to
that band, but using freq_list will only filter the results.

Fixes SHEL-2626.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Update nRF70 release/v2.6 firmware patch.

Signed-off-by: Karun Kumar Eagalapati <karun.kumar@nordicsemi.no>

This algo is useful to choose the best RSSI network independent of band.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

To cater for different needs add an configuration options for WPA
supplicant network selection (scan results sorting). The default is
still left unchanged.

Fixes SHEL-2626 (when using "reliability" based NW selection).

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Updating nRF70 release/v2.6 firmware patch.

Signed-off-by: Karun Kumar Eagalapati <karun.kumar@nordicsemi.no>

MAC address setting is a local operation i.e., doesn't need any FMAC
interaction and is essential for bringing the up driver in case OTP has
no programmed MAC address. This doesn't need any FMAC context checks.

Fixes SHEL-2675.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Pull a fix for PBKDF2 key generation API in OpenThread

Signed-off-by: Maciej Baczmanski <maciej.baczmanski@nordicsemi.no>

Update sdk-zephyr revision to include TCP fixes.

Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>

Due to recent changes in hostap to move few buffers from heap->stack (to
improve the reliability of allocations) this has increased the stack
size and with another recent change to increase the max polling sockets
this puts over the 4096 stack size for net_mgmt causing stack overflow.

Increase the stack size for net_mgmt to fix SHEL-2640 and SHEL-2676.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This is handy esp. in crowded channel environments to avoid false AP
dead detections, the default is chosen accordingly.

Implements SHEL-2689.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

…eout

Pull sending AP dead detection timeout to UMAC.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Pull in changes done for WPA Auto security support.

Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

Support BSSID configuration while setting up the network information
as part of the connect command processing.

Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

Support WPA Auto security mode wherein supplicant can
implicitly choose the highest security among WPA, WPA2
and WPA3 for association with a network based on network support.

Fixes SHEL-1131.

Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

The `connect` command has been updated to take key-value style
arguments. Update the description to include this information.

Fixes SHEL-2699.

Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

When WPA supplicant is enabled, use the default from hostap which sets
the appropriate value rather than overriding it. This helps us maintain
this setting.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

The current 800ms is not enough in real setups, where Thread
routers must serve as intermediate hops for many parallel
conversations. Bump this to 2s.

Signed-off-by: Damian Krolik <damian.krolik@nordicsemi.no>

Shell stack size is now increased, but forgot to update the debug
snippet.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Stack size was increased in 77cad23.
But connecion attempts, when done from `conn_mgr` module, add
a couple of levels of depth which causes the stack usage to exceed
the allocated space. Increasing the stack size by 200 bytes takes
care of this.

Signed-off-by: Ravi Dondaputi <ravi.dondaputi@nordicsemi.no>

Pull in a fix in pinctrl that prevents the nrf_qspi_nor driver from
failing to initialize when the flash chip is configured to work in
non-Quad mode.

Signed-off-by: Andrzej Głąbek <andrzej.glabek@nordicsemi.no>

Updating nRF70 release/v2.6 firmware patch.

Signed-off-by: Karun Kumar Eagalapati <karun.kumar@nordicsemi.no>

Kconfig options that were application-specific had not been documented.
This resulted in mentions in documentation not linking to anything.

CSA has changed the structure of their website.
This fixes the affected links in our documentation.

Signed-off-by: Wille Backman <wille.backman@nordicsemi.no>

Updating and creating release-related doc files.

Signed-off-by: Richa Pandey <richa.pandey@nordicsemi.no>

OpenThread requires flash because it uses the Trusted Storage
subsystem to store persistent keys in Internal Trusted Storage.

Signed-off-by: Georgios Vasilakis <georgios.vasilakis@nordicsemi.no>

We don't suppor the psa_its_file implementation
so don't include it in the build.

Signed-off-by: Georgios Vasilakis <georgios.vasilakis@nordicsemi.no>

Don't use the define from the CC3XX library in the
PSA crypto driver wrappers file. There are is a corner
case in which we will have to build this file without
including the headers for CC3XX.

Signed-off-by: Georgios Vasilakis <georgios.vasilakis@nordicsemi.no>

Add experimental symbol for legacy and PSA crypto
usage. This feature might be removed without notice
and should not be used in production.

Signed-off-by: Georgios Vasilakis <georgios.vasilakis@nordicsemi.no>

Enable LTO for the WIFI shell sample to fix
flash overlfow issue. LTO is experimental but
the same goes for using legacy crypto and PSA
crypto at the same time and this sample does that
as well.

Signed-off-by: Georgios Vasilakis <georgios.vasilakis@nordicsemi.no>

This fixes an issue in nrf_security which allows
to support PSA APIs with Oberon PSA core when
legacy mbedTLS APIs are used.

Signed-off-by: Georgios Vasilakis <georgios.vasilakis@nordicsemi.no>

Fixed software maturity table in 2.6.1 to match
it with 2.6.0.

Signed-off-by: Richa Pandey <richa.pandey@nordicsemi.no>

Tagged repositories as required.

Signed-off-by: Vinayak Kariappa Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>

NCS version has been set to 2.6.1.

Signed-off-by: Vinayak Kariappa Chettimada <vinayak.kariappa.chettimada@nordicsemi.no>

Hostap now uses more stack, so, calibrate and increase stack sizes.

Fixes SHEL-2754.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

The memory for format is leaked. Instead of fixing the leak, move away
from malloc based implementation it is overkill for logging and also
protect the prints using a mutex, this should have been done even with
malloc/free for thread safety (apart from inherent malloc/free thread
safety).

Fixes SHEL-2274.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

The response handler doesn't check for failures and they will be
ignored, add a check for failures and return failure.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Now that the memory leak has been fixed, we don't need 100K heap for QT
app.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Fixes heap corruption seen in SVD test suites.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Updating nRF70 release/v2.6 firmware patch.

Signed-off-by: Karun Kumar Eagalapati <karun.kumar@nordicsemi.no>

Manifest update with fix for OpenThread.

Signed-off-by: Eduardo Montoya <eduardo.montoya@nordicsemi.no>

Update nRF70 firmware patch.

Signed-off-by: Prasun Sinha <Prasun.Sinha@nordicsemi.no>

[SHEL-2947] QoS null frame based legacy power save support.

Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>

[SHEL-2947] Changing naming of power save mode
to mechanism(Text change).

Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>

FMAC relies on these callbacks to perform a RPU recovery i.e., coldboot
the device in a clean way, this is achieved by performing an interface
down and then up, this properly cleans up the driver, performs a cold
boot and either through NET_IF events (for scan only) or WPA_S events
(for full Wi-Fi) notifies the applications.

Implements SHEL-2726.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

In case we get multiple watchdog timers in succession, we need to
sequentialize the recovery.

Implements SHEL-2726.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

In some scenarios esp. while debugging nRF70, this feature should be
disabled, so, provide a feature flag and mark it as experimental.

Implements SHEL-2726.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This delay ensures that the applications have enough time to perform any
cleanup and be prepared once the RPU is powered on again.

Implements SHEL-2726.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This is necessary as recovery involves calling down and up in a rapid
succession.

Implements SHEL-2726.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This helps us verify the recovery mechanism.

Implements SHEL-2726.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

During watchdog (or any) interrupt processing, RPU accesses are being
made and they assert the wakeup_now flag this causes RPU recovery to not
trigger.

New false or true recovery detection algo:

 Check the time difference b/w last de-assert and assert, and if it
 exceeds minimum time needed for RPU to enter sleep, then not the
 timestamp. This timestamp will be used to compare when a watchdog
 interrupt is received and see if during the last window if host has
 given a chance for RPU to attempt sleep, if yes, then attempt recovery
 else ignore watchdog.

Also, add a Kconfig for the 10s active time that triggers recovery, this
needs to be passed to the FW (once we have enough patch memory).

Also, add a Kconfig for the minimum time needed for RPU to attempt sleep
in positive case.

Also, add a new _ms API for time stamp fetch, this is to avoid
precision loss when converting to and from ms to us and also makes code
readable by avoiding *1000 and /1000.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

In case RPU is stuck and need a recovery, the failures in interface down
should be ignored as they are expected and we should proceed with device
removal that in turn removes power to the RPU.

TODO: This works for single VIF, but needs more thought for multi-VIF.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Before proceeding with RPU bringup, do a sanity check by reading a known
signature to make sure the Host-RPU comms are operational.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

These are helpful for debugging RPU recovery only.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

In order for the interface down to propagate and cleanup it needs more
time, using Shell 10ms was working due to human delay, but
programatically this needs higher delay.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

RPU is only providing the per-wiphy (RPU) extended capabilities, so,
remove storing of per-VIF extended capabilities.

BTW, there is a memory leak here when doing interface down and up.

Fixes SHEL-2738.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

The extended capabilities are not freed causing a leak on interface down
and up.

Fixes SHEL-2738.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

During recovery we might get further watchdog interrupts causing
multiple recovery requests, ignore them if a recovery is already in
progress.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This is to avoid successive recoveries in case we get successive
watchdog interrupts from the RPU.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Check for RPU context as well.

To fix this properly we need more fixes to be backported, but this
should suffice for now.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

In case RPU is stuck in consecutive recovery over a time period then
that means it's not recoverable through RPU recovery, only thing left to
do is to trigger a system reboot. This feature is disabled by default,
so, either application can do their own implementatio or enable this
feature in the driver along with configurable retries and window period.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Though this is no-op for now, it would lead to crash if BAL de-init is
called which will be in the upcoming commits.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

BAL de-init was never called, so, these weren't caught. In upcoming
commits BAL de-init will be used, so, assign here to avoid crashes.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This can lead to crash in case driver initialization fails e.g.
flashing wrong build (5340 on 7002) or if this API is called too early
before the driver is initialized.

Fixes SHEL-2576.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

The QSPI dev context has it's own structure, so, need to be extract the
QSPI dev ops from the context, this has been implemented improperly, but
as it's not been used till date hadn't caused any problems.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Fix RPU recovery protection to solve build failures when RPU recovery is
disabled.

As recovery is primarily based on power-management, add a Kconfig
dependency to enforce, this simplies the macros to protect the code.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

During interface down in case TX has pending buffers in either TXQ or
Pending_Q then they are not freed instead the Q itself is freed.

Fix by traversing the Q and freeing all members.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This library should be used samples to manage Wi-Fi usage dynamically.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Use Wi-Fi ready library to manage Wi-Fi.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

These are very frequent, so, a separate debug is added for debugging
host RPU recovery logic.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

This is useful to understand the reason for comms trigger b/w host and
RPU.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Mention RPU recovery feature, there are no docs yet, so, no links.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

With this offload, host doesn't need to manage RX buffers for management
frames, and this saves Host-RPU comms and thus giving RPU to sleep more
often and is essential to test RPU recovery.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

In crowded environments RPU is active for more than 10s due to too many
retries and this triggers a false RPU recovery. To avoid this, increase
the default to 50s to handle corner cases, as this will only impact the
recovery triggered case, higher timeout doesn't have any impact in
normal cases.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

To handle interoperability issue with few APs, add a feature to keep
sending keepalive frames periodically to avoid AP disconnecting the STA.

This is disabled by default to avoid unnecessary power consumption as
it's only seen with few old APs.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Pull latest fixes backported to 2.6 branch.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Add a null check for HAL context in the interrupt handler, this was
causing locking issue operating on null. The root cause of null is not
known, but this solves the locking issue when data and control paths are
excited in parallel.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Ideally we should be using Zephyr spinlock APIs but that requires
changes to shim API, so, for this maintenance release just replace with
mutex to keep the context same and no API changes.

This solves the locking issue that we see when control and data path are
excited concurrently due to locking semantics of semaphores, the issue
is not root caused but mutex enforce strict locking semantics for
multiple threads and solve the issue.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Dynamically set power save exit strategy runtime configuration that
allows to switch b/w stratgies depending on conserving power and
low-latency traffic download.

Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>

Pull Wi-Fi management APIs for PS exit strategy configuration support.

Signed-off-by: Ajay Parida <ajay.parida@nordicsemi.no>

There is a race condition when recovery is in progress and in parallel
Wi-Fi util commands are being executed (CTF), where the RPU context is
de-initialized as part of recovery but no checks are present in the
Wi-Fi util command processing causing a crash.

This needs a proper fix for all commands, but for maintenance branch
fix is added only for commonly used commands.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Fixes comments in public header file.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Mistakenly the PR ref was merged, so, update with the SHA of the merged
Zephyr PR.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

The RPU context lock is not unlocked this is causing recovery to be
stuck waiting for the lock.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Absorb Watchdog timer related fixes.

Signed-off-by: Praveen Kankipati <Praveen.Kankipati@nordicsemi.no>

The mutex is used to protect RPU zephyr context which gets modified for
every interface down and up (including recovery), so, it was being
re-initialized but also used to protect down and up which is a bug.

Move the re-initialization to the driver entry so that it happens only
once and we can properly use the mutext for down and up protection.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Set VERSION in applications and samples to 2.6.2 for NCS v2.6.2
release.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

For the 2.6.2 release.

Signed-off-by: Chaitanya Tata <Chaitanya.Tata@nordicsemi.no>

Update docs for 2.6.2 release

Signed-off-by: Richa Pandey <richa.pandey@nordicsemi.no>

Update the manifest file with NCS v2.6.2 tagged repositories.

Signed-off-by: Robert Lubos <robert.lubos@nordicsemi.no>

v3 of actions/upload-artifact and
actions/download-artifact becomes obsolete

Signed-off-by: Jakub Ciesla <jakub.ciesla@nordicsemi.no>