Hi
Can you explain what exactly you want to use the nRF7002 for on an ESP32 board (that already supports Wi-Fi AFAIK).
1. It should definitely be possible to connect the nRF7002 to the ESP32 over SPI, but we do not have any drivers available for communication between the ESP32 and nRF7002, as we focus on using our own SoCs as hosts. But it should be possible to use the drivers in the NCS as reference to communicate with the nRF7002 from the ESP32.
2. This would be through SPI/QSPI, but since we don't have specific drivers for this, you would need to provide support for it on your own. I would recommend checking out the Device Commissioning and Characterization to see how you should communicate with the nRF70 series.
3. I think you should see the two links above for what you need.
4. Yes, you can set the frequency band with
/**
* @brief IEEE 802.11 operational frequency bands (not exhaustive).
*/
enum wifi_frequency_bands {
/** 2.4 GHz band. */
WIFI_FREQ_BAND_2_4_GHZ = 0,
/** 5 GHz band. */
WIFI_FREQ_BAND_5_GHZ,
/** 6 GHz band (Wi-Fi 6E, also extends to 7GHz). */
WIFI_FREQ_BAND_6_GHZ,
/** Number of frequency bands available. */
__WIFI_FREQ_BAND_AFTER_LAST,
/** Highest frequency band available. */
WIFI_FREQ_BAND_MAX = __WIFI_FREQ_BAND_AFTER_LAST - 1,
/** Invalid frequency band */
WIFI_FREQ_BAND_UNKNOWN
};
Best regards,
Simon
Hi
Can you explain what exactly you want to use the nRF7002 for on an ESP32 board (that already supports Wi-Fi AFAIK).
1. It should definitely be possible to connect the nRF7002 to the ESP32 over SPI, but we do not have any drivers available for communication between the ESP32 and nRF7002, as we focus on using our own SoCs as hosts. But it should be possible to use the drivers in the NCS as reference to communicate with the nRF7002 from the ESP32.
2. This would be through SPI/QSPI, but since we don't have specific drivers for this, you would need to provide support for it on your own. I would recommend checking out the Device Commissioning and Characterization to see how you should communicate with the nRF70 series.
3. I think you should see the two links above for what you need.
4. Yes, you can set the frequency band with
/**
* @brief IEEE 802.11 operational frequency bands (not exhaustive).
*/
enum wifi_frequency_bands {
/** 2.4 GHz band. */
WIFI_FREQ_BAND_2_4_GHZ = 0,
/** 5 GHz band. */
WIFI_FREQ_BAND_5_GHZ,
/** 6 GHz band (Wi-Fi 6E, also extends to 7GHz). */
WIFI_FREQ_BAND_6_GHZ,
/** Number of frequency bands available. */
__WIFI_FREQ_BAND_AFTER_LAST,
/** Highest frequency band available. */
WIFI_FREQ_BAND_MAX = __WIFI_FREQ_BAND_AFTER_LAST - 1,
/** Invalid frequency band */
WIFI_FREQ_BAND_UNKNOWN
};
Best regards,
Simon
Thanks , Now We are clear and we are planning to use nRF 5340 as host and nRF 7002 (for wifi / ble). In that we having below queries.
1. In nRF 7002 thread and WiFi will working simultaneously ?
2. In nRF 5340 , can we run free rtos projects?
3. Is there thread library sdk support available? sample example for verifying ?
4. Is there Firmware over Air upgrade support available ?
5. hope we can communication with cellular module through UART using AT command interface?
Hi
1. Yes, Wi-Fi and Thread can run simultaneously. Please note that the nRF5340 will be what is running the Thread here.
2. No, the nRF Connect SDK is built on the Zephyr RTOS, so FreeRTOS will not be an option.
3. Yes, please check out the nRF Connect SDK. We have Thread samples available here: https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/samples/thread.html
4. Yes, this is also available in the nRF Connect SDK. https://developer.nordicsemi.com/nRF_Connect_SDK/doc/latest/nrf/device_guides/working_with_nrf/nrf53/nrf5340.html#fota-updates
5. This should also be possible, yes. The nRF5340 has 4 UART instances that can be used for whatever you'd like.
Best regards,
Simon
Thanks, I check Uart communication between nRf5340 to cellular module. We are referring data sheet (section9 Hardware and Layout). We are not seeing any pin assignment for UART. Please let us know which pins we need to configure for UART and I2C.
