Add Zephyr WiFi Guide for NINA-W102 on APARD32690

[Brandon-Hurst]

This document is a guide for flashing firmware on the APARD32690's NINA-W102 WiFi module and getting the Zephyr WiFi sample running on the AD-APARD32690-SL board once the NINA firmware is flashed. It walks through setting up the devicetree and Kconfig files necessary to use the WiFi module on the APARD board.

Instructions include:

• Building and flashing boot firmware onto NINA-W102 module on AD-APARD32690-SL.
• Setting up a devicetree and Kconfig file to use the Zephyr Wifi sample with APARD
• Building & Flashing the Wifi demo
• Evaluating the Zephyr Wifi sample on APARD via serial terminal

This repeats #17 but it was the simplest way for me to leave out the irrelevant commits mentioned. It should only contain the Wifi guide now.

[gastmaier]

Hi @Brandon-Hurst ,

I did a small review and moved to solution, since we have an APARD32690 there, and the software folder is meant for software that supports multiple platforms and is run in user space.
So the new location is solutions/reference-designs/ad-apard32690-sl/nina-w102/index

what was you experience with this repo? If git lfs got on the way (e.g. took too much time to clone), I updated the instructions at forking_publishing to add how to skip the step of resolving the lfs artifacts (images, pdfs, powerpoints...) during clone and fetch them on demand using doctools serve.

I think you would have specially benefited from this feature since the PR adds no images.

About

it was the simplest way for me to leave out the irrelevant commits mentioned.
In git you can push/pull from whatever to whatever, so you could have done

git push add-zephyr-wifi:add-zephyr-wifi-apard --force

To preserve the old PR, from your new branch add-zephyr-wifi

[Brandon-Hurst]

Hey @gastmaier, thanks for the merge. Actually, the experience wasn't too bad. I'd say most of the friction I had is because I'm newer to Sphinx / transitioning from Markdown. How the indexes / toctree get set up is still a little fuzzy to me, but for simple guides like this it was actually very easy.

On the move to the solutions space, I will likely be pushing a couple more Zephyr guides to connect over 10BASE-T1L and Bluetooth. While we don't make another board yet with the NINA, these two other interfaces are supported on many, many boards. And we'll likely want a Zephyr section in that software directory anyway. If you have other ideas about where we'd put one, I'm happy to chat about it.

[gastmaier]

In this case, when you create the zephyr dir, feel free to move back