Ctxlink_wifi_options

[sidprice]

This PR adds Wi-Fi management for ctxLink using GDB and a new monitor command.

With the original releases of ctxLink some users had issues using the HTTP and WPS provisioning features of ctxLink.

Also, after provisioning some users found it hard to discover the IP address of ctxLink, this is required to connect to the probe.

The new monitor command is "wifi".

To inspect the current Wi-Fi status the following command is used:

mon wifi

This will display either "Not Connected," or the SSID, Signal Strength (RSSI), and IP address of the connected Access Point.

To connect to a Wi-Fi Access Point the following command is used, substituting the SSID and PassPhrase settings of the AP:

mon wifi SSID,Passphrase

Spaces are accepted for these two parameters, however, there should be no space before or after the ",".

Your checklist for this pull request

• I've read the Code of Conduct
• I've read the guidelines for contributing to this repository
• It builds for hardware native (see Building the firmware)
• It builds as BMDA (see Building the BMDA)
• I've tested it to the best of my ability
• My commit messages provide a useful short description of what the commits do

Closing issues

None.

[Misaka0x2730]

Hi!
First off, apologies if I’m stepping on your toes—I don’t mean to meddle in something that might be out of my scope.
I just wanted to suggest that there might be another way to achieve what you’re aiming for without modifying command.c.
Please, check the platform's custom command feature (PLATFORM_HAS_CUSTOM_COMMANDS), and you can find an example in my project here: https://github.com/Misaka0x2730/MioLink/blob/main/firmware/source/bmp/platform_commands.c#L38C17-L38C34
It could help keep the core code untouched while still delivering the same functionality.

[sidprice]

@Misaka0x2730 Hello!

This was previously suggested by @ALTracer, and is a good idea. Since this PR is a feature update it is awaiting review and merging until after the next release. Hopefully, during this period I can adopt the suggestion.

[sidprice]

I am not sure this is such a good idea since it prevents grouping the custom commands logically in the command list. Plus, there are quite a few other custom commands already in the command list, e.g. TraceSWO & RTT.

I think unless the maintainers (@dragonmux ) feel it is required I am going to leave the added command for this PR as it is.

[Misaka0x2730]

I agree that @dragonmux is the one who’ll ultimately decide here.
However, I want to clarify my thoughts on “custom” commands. For instance, TraceSWO and RTT are supported by many (if not most) platforms—so they’re hardly “custom” in the sense of belonging to just one.
By contrast, Wi-Fi is specific to your platform, which I believe aligns more with the idea of platform-specific commands.

[perigoso]

I agree that these should be platform commands at least for now, though not having control over the grouping is unfortunate.
I have some ideas to rework to the command system but until then we are limited with what we can do. Do note that this only affects the print on the help command and doesn't affect functionality

[sidprice]

@perigoso Thanks for your input. I would be happy to review the platform commands should the command table/architecture change in the future.