Hi,
Every BLE-related example in this repository (application_projects/r19an0417/BLE_PXP_application, application_projects/r19an0527/BLE_Codeless_application, and the WiFi/BLE coexistence example) targets EK-RA6W2 specifically. There is no BLE example anywhere in the repo for RA6W1.
This is a real gap: our shipped module, RRQ61051-009, is a Wi-Fi 6 + BLE combo module built on RA6W1 (per the module datasheet, part R7SA6W1CEDZDD), not RA6W2. So the only customers who can actually use these BLE examples as a direct reference are ones with the RA6W2 evaluation board itself; anyone bringing up BLE on the actual shipped RRQ61051 module has no matching official example to build from or validate against.
Discrepancy worth clarifying: what hardware does EK-RA6W2 actually debug against?
Searching this repo for RRQ61051 turns up 26 files, all .launch debug configs in other ek_ra6w2 example/application projects (e.g. example_projects/ek_ra6w2/adc_ek_ra6w2_ep, wifi_https_server_ek_ra6w2, wifi_mqtt_client_dpm_ek_ra6w2, wifi_ota_ek_ra6w2_ep, application_projects/r19an0438/Matter_Wifi_Lock_Application/matter_wifi_ble_lock_ek_ra6w2, and 22 others), all specifying:
com.renesas.cdt.core.targetDevice = "RRQ61051"
But application_projects/r19an0417/BLE_PXP_application/wifi_ble_pxp_reporter_ek_ra6w2 — the one BLE reference project, in both the current release and the v2.0.1 release we originally checked — instead specifies:
com.renesas.cdt.core.targetDevice = "R7JA6W2DE"
R7JA6W2DE does not appear anywhere in the RRQ61051 module datasheet; only R7SA6W1CEDZDD/R7SA6W1BEDZDD/R7SA6W1AEDZDD are listed there as the Wi-Fi MCU used in RRQ61051 modules. So within your own repo, the large majority of ek_ra6w2 examples debug against a device named RRQ61051, while the BLE example debugs against a differently-named device that doesn't match any part number in the RRQ61051 datasheet.
We can't tell from the outside whether RRQ61051 and R7JA6W2DE are just two J-Link device-database aliases for the same physical debug port, or whether these are actually two different pieces of hardware — which would materially change what "the EK-RA6W2 BLE reference" is even running on. Could you clarify this directly?
What we're asking for
Is an RA6W1 BLE example planned, or does one exist that isn't published in this repo?
What hardware does wifi_ble_pxp_reporter_ek_ra6w2 actually debug against — is R7JA6W2DE a bare RA6W2 chip, an RRQ61051 module, or something else — and why does it differ from the RRQ61051 device target used in the other 26 ek_ra6w2 examples?
If no RA6W1 BLE example exists, could one be added — even a minimal GTL/PXP-style reference for RA6W1 + DA14531 — since that's the actual combination shipping in the RRQ61051-009 module today?
Context / why this matters concretely
We're bringing up BLE on an RRQ61051-009 module (RA6W1 + DA14531, dedicated antenna) and have been unable to get any response at all from the DA14531 — no boot-ROM STX, no pad activity of any kind, confirmed via cycle-accurate on-chip signal capture, across every reset polarity/timing/sequence variant, including your own driver's documented wake-pulse-before-reset step. When we opened a support ticket, the reply pointed us to wifi_ble_pxp_reporter_ek_ra6w2 — which, per the discrepancy above, we can't even confirm targets the same silicon as our module. An official, unambiguous RA6W1 example would let us directly compare our bring-up against known-working reference code and configuration on the exact same silicon, rather than adapting a project we can't fully verify is comparable.
Please, try help me with this issue.
I'm stuck at this stage with no BLE promotion during the bring up.
Thanks,
Hananya
Hi,
Every BLE-related example in this repository (application_projects/r19an0417/BLE_PXP_application, application_projects/r19an0527/BLE_Codeless_application, and the WiFi/BLE coexistence example) targets EK-RA6W2 specifically. There is no BLE example anywhere in the repo for RA6W1.
This is a real gap: our shipped module, RRQ61051-009, is a Wi-Fi 6 + BLE combo module built on RA6W1 (per the module datasheet, part R7SA6W1CEDZDD), not RA6W2. So the only customers who can actually use these BLE examples as a direct reference are ones with the RA6W2 evaluation board itself; anyone bringing up BLE on the actual shipped RRQ61051 module has no matching official example to build from or validate against.
Discrepancy worth clarifying: what hardware does EK-RA6W2 actually debug against?
Searching this repo for RRQ61051 turns up 26 files, all .launch debug configs in other ek_ra6w2 example/application projects (e.g. example_projects/ek_ra6w2/adc_ek_ra6w2_ep, wifi_https_server_ek_ra6w2, wifi_mqtt_client_dpm_ek_ra6w2, wifi_ota_ek_ra6w2_ep, application_projects/r19an0438/Matter_Wifi_Lock_Application/matter_wifi_ble_lock_ek_ra6w2, and 22 others), all specifying:
com.renesas.cdt.core.targetDevice = "RRQ61051"
But application_projects/r19an0417/BLE_PXP_application/wifi_ble_pxp_reporter_ek_ra6w2 — the one BLE reference project, in both the current release and the v2.0.1 release we originally checked — instead specifies:
com.renesas.cdt.core.targetDevice = "R7JA6W2DE"
R7JA6W2DE does not appear anywhere in the RRQ61051 module datasheet; only R7SA6W1CEDZDD/R7SA6W1BEDZDD/R7SA6W1AEDZDD are listed there as the Wi-Fi MCU used in RRQ61051 modules. So within your own repo, the large majority of ek_ra6w2 examples debug against a device named RRQ61051, while the BLE example debugs against a differently-named device that doesn't match any part number in the RRQ61051 datasheet.
We can't tell from the outside whether RRQ61051 and R7JA6W2DE are just two J-Link device-database aliases for the same physical debug port, or whether these are actually two different pieces of hardware — which would materially change what "the EK-RA6W2 BLE reference" is even running on. Could you clarify this directly?
What we're asking for
Is an RA6W1 BLE example planned, or does one exist that isn't published in this repo?
What hardware does wifi_ble_pxp_reporter_ek_ra6w2 actually debug against — is R7JA6W2DE a bare RA6W2 chip, an RRQ61051 module, or something else — and why does it differ from the RRQ61051 device target used in the other 26 ek_ra6w2 examples?
If no RA6W1 BLE example exists, could one be added — even a minimal GTL/PXP-style reference for RA6W1 + DA14531 — since that's the actual combination shipping in the RRQ61051-009 module today?
Context / why this matters concretely
We're bringing up BLE on an RRQ61051-009 module (RA6W1 + DA14531, dedicated antenna) and have been unable to get any response at all from the DA14531 — no boot-ROM STX, no pad activity of any kind, confirmed via cycle-accurate on-chip signal capture, across every reset polarity/timing/sequence variant, including your own driver's documented wake-pulse-before-reset step. When we opened a support ticket, the reply pointed us to wifi_ble_pxp_reporter_ek_ra6w2 — which, per the discrepancy above, we can't even confirm targets the same silicon as our module. An official, unambiguous RA6W1 example would let us directly compare our bring-up against known-working reference code and configuration on the exact same silicon, rather than adapting a project we can't fully verify is comparable.
Please, try help me with this issue.
I'm stuck at this stage with no BLE promotion during the bring up.
Thanks,
Hananya