Hi Nxp,
After reaching the limit of the ESP32S3 that doesn't support ble long range in a multiconnect way, i would like to fully redesign th product with RW612 based module.
The RW612 will be:
- ble central :connected to maximum 4 peripherals in ble long range ( full coded phy).
- Run simultaneously the one peripheral role to be connected to a smatphone (to switch in wifi )
- Wifi Access point to get datalog files from an SD card
- Ota via our Mobile app
- Display informations on a 320*240 rgb screen ( lvgl v9)
- Use RTC with back up batterie to save time when main power is off.
RW612 seems to be a good candidate to replace our esp32s3. The module from insight sip ISP5261-WX seems to be appropriate too.
From developpement point of view, MCUXpresso SDK example can be a good starting point.
My questions are:
1 - Is wifi_cli_over_ble_wu the best starting point, or should i start from ota_mcuboot_server ?
2 - With esp32 Nimble stack, the problem was the multiconnect that requires vendor hci command that were not implemented into not accessible low level host controller command for long range.
I didn't find any example with central and peripheral + multi connect several peripheral in examples. Can you confirm it is possible in long range ble ?
3 - May be i can avoid the rw612 to be peripheral by letting wifi ON all the time, but it is a bit a pitty to do so if 99,9% of the time wifi is off. I would prefer to avoid to disturb radio with wifi if it is not used... And just switch wifi on when needed via ble.
4 - Most examples uses freertos ( like i did with esp32). But should i consider zephyr too. Does zephyr supports better the ble coded phy ? What is the ble stack used in nxp product ?
5 - Is Vs code more recommended now to developp? I really miss debug feature with esp32...
Hope you will have enough information to guide me i the best possible way
Thank you !
