Radio transmit and receive in timeslot

RE: Radio transmit and receive in timeslot

user116508 — Mon, 06 Jun 2022 05:30:16 GMT

hi,

I got the code working by resetting radio register in radio callback case.

    // Disable and enable the Radio to reset the RADIO registers, needed from S1xx v8.x
    NRF_RADIO->POWER = ((RADIO_POWER_POWER_Disabled << RADIO_POWER_POWER_Pos) & RADIO_POWER_POWER_Msk);
    NRF_RADIO->POWER = ((RADIO_POWER_POWER_Enabled << RADIO_POWER_POWER_Pos) & RADIO_POWER_POWER_Msk);

thanks for your support and timely responses.

RE: Radio transmit and receive in timeslot

user7377 — Fri, 03 Jun 2022 12:33:25 GMT

Do you see this error if you keep all the low-level radio code but remove the SoftDevice and timeslot related code, so that you always have full access to the radio etc? If not (or in any case), can you check if this issue also happens if you do everything in a single timeslot?

RE: Radio transmit and receive in timeslot

user116508 — Fri, 03 Jun 2022 06:23:15 GMT

/**@brief Request next timeslot event in earliest configuration
 */
uint32_t request_next_event_earliest(void) {
  m_slot_length = 50000;
  m_timeslot_request.request_type = NRF_RADIO_REQ_TYPE_EARLIEST;
  m_timeslot_request.params.earliest.hfclk = NRF_RADIO_HFCLK_CFG_XTAL_GUARANTEED;
  m_timeslot_request.params.earliest.priority = NRF_RADIO_PRIORITY_NORMAL;
  m_timeslot_request.params.earliest.length_us = m_slot_length;
  m_timeslot_request.params.earliest.timeout_us = 1000000;
  return sd_radio_request(&m_timeslot_request);
}

/**@brief Configure next timeslot event in earliest configuration
 */
void configure_next_event_earliest(void) {
  m_slot_length = 50000;
  m_timeslot_request.request_type = NRF_RADIO_REQ_TYPE_EARLIEST;
  m_timeslot_request.params.earliest.hfclk = NRF_RADIO_HFCLK_CFG_XTAL_GUARANTEED;
  m_timeslot_request.params.earliest.priority = NRF_RADIO_PRIORITY_NORMAL;
  m_timeslot_request.params.earliest.length_us = m_slot_length;
  m_timeslot_request.params.earliest.timeout_us = 1000000;
}

/**@brief Configure next timeslot event in normal configuration
 */
void configure_next_event_normal(void) {
  m_slot_length = 50000;
  m_timeslot_request.request_type = NRF_RADIO_REQ_TYPE_NORMAL;
  m_timeslot_request.params.normal.hfclk = NRF_RADIO_HFCLK_CFG_XTAL_GUARANTEED;
  m_timeslot_request.params.normal.priority = NRF_RADIO_PRIORITY_HIGH;
  m_timeslot_request.params.normal.distance_us = 1000000;
  m_timeslot_request.params.normal.length_us = m_slot_length;
}

/**@brief Timeslot signal handler
 */
void nrf_evt_signal_handler(uint32_t evt_id) {
  uint32_t err_code;

  switch (evt_id) {
  case NRF_EVT_RADIO_SIGNAL_CALLBACK_INVALID_RETURN:
    //No implementation needed
    break;
  case NRF_EVT_RADIO_SESSION_IDLE:
    //No implementation needed
    break;
  case NRF_EVT_RADIO_SESSION_CLOSED:
    //No implementation needed, session ended
    break;
  case NRF_EVT_RADIO_BLOCKED:
    //Fall through
  case NRF_EVT_RADIO_CANCELED:
    err_code = request_next_event_earliest();
    APP_ERROR_CHECK(err_code);
    break;
  default:
    break;
  }
}
uint32_t timeslot_sd_init(void) {
  uint32_t err_code;

  err_code = sd_radio_session_open(radio_callback);
  if (err_code != NRF_SUCCESS) {
    return err_code;
  }

  err_code = request_next_event_earliest();
  if (err_code != NRF_SUCCESS) {
    (void)sd_radio_session_close();
    return err_code;
  }
  return NRF_SUCCESS;
}

RE: Radio transmit and receive in timeslot

user7377 — Tue, 31 May 2022 12:29:26 GMT

Hi,

That is unexpected. Do the two transmits (the first successful and second failing) happen in the same timeslot? Or could it be that the SoftDevice is using the radio in the meantime. It does not look like that from the code snippets but perhaps they do not shot the full picture. Can you share more of your code so that I get a fuller picture of what is happening?

Also, can you check with a debugger if execution is really halted in the while waiting loop and not just check if something afterwards is happening or not (without it, there could theoretically be another problem somewhere else with higher priority that prevents this code snippet from running, so it would be good to know with certainty that you see that execution is "stuck" in this waiting loop.)

RE: Radio transmit and receive in timeslot

user116508 — Tue, 31 May 2022 04:18:42 GMT

Hi,

I removed all printf and checked using 2 devices. In one device the above code (transmission and time slot combined ) and in other the radio receiver example code. And put two devices in debugging mode. I found that only one packet is received in the receiving side. I have checked and confirmed that one transmission is working and for the second transmission, the lines after while loop in the send_packet() function are not functioning. So the code is getting stuck in that while loop.

RE: Radio transmit and receive in timeslot

user7377 — Mon, 30 May 2022 12:54:32 GMT

Hi,

I see. EVENTS_READY should come some time after you trigger the TXEN task, and there are no other requirements (see figure 8 in the Radio chapter in the PS). How did you verify that it blocks here? What happens if you remove the printf statement?

RE: Radio transmit and receive in timeslot

user116508 — Fri, 27 May 2022 15:39:20 GMT

Hi,

Sorry. I was not in that while .. it is in events ready while loop. while (NRF_RADIO->EVENTS_READY == 0U) . I tested by debugging.

RE: Radio transmit and receive in timeslot

user7377 — Fri, 27 May 2022 13:50:19 GMT

Hi,

[quote user=""]I think its getting stuck in this while loop. while (NRF_RADIO->EVENTS_DISABLED == 0U) [/quote]

I do not immediately see how it could be stuck here (you should get the DISABLED event shortly after writing to the DISABLE task. As you write "think" I wonder if you have actually verified with a debugger that this is the case? If not, can you do it?

If it is indeed the case, then the only reason that comes to mind is if this triggers an interrupt or for some other reason a higher priority piece of code runs before your loop and sets EVENTS_DISABLED to 0 again. That is just an hypothesis, though.