@György-Farkas It is a problem, since my client wants to to turn the AP off when the user is not configuring the IoT device, and other products allow this. The hidden SSID is a work around that is likely to be OK, but is not the proper fix. Even as a hidden SSID, it is still broadcasting and adding an extraneous AP to an already crowded WiFi spectrum.
I don't understand why this is a limitation? Either driver should provide such a feature. Another project using a Marvell chip has no problem turning of the AP while leaving STA mode operational.
With the number of inquiries about this request, it seems like a reasonable feature request for a future version of the drivers.
Documentation touch-ups are in on our backlog.
However, if you would not like to wait on us and want to make your own edits or updates in the meantime, the documentation is all open source and available on GitHub: https://github.com/OnionIoT/Onion-Docs
If you make a Pull Request with your changes, we'll review it, accept it when it's ready, and the changes will show up on docs.onion.io !
@Tisham-Dhar assuming you're using the hardware SPI and not bit-banging, I think it would be more straight-forward to use the designated SPI CS1 as the chip select, and then use a mux, with other GPIOs as control signals, to route the CS signal.
It's very likely possible to use the hardware controller with a GPIO CS signal, but it would likely involve quite a bit more work than the alternative.
uci -q batch <<-EOF > /dev/null