RE: Changing Eddystone beacon frame type and data

Slay — Fri, 10 Apr 2020 12:57:42 GMT

OK, I think I have figured it out myself:

Looking at the code for configure_slot in es_slot.c, it starts copying the data at

    uint8_t * p_data_after_ranging_data = ((uint8_t *)(&m_reg.slots[slot_no].adv_frame.frame) +
                                           RANGING_DATA_INDEX + RANGING_DATA_LENGTH);

This is 2 bytes from the frame-start. And the actual copying is done like:

        case ES_FRAME_TYPE_URL:
            memcpy(p_data_after_ranging_data, &p_frame_data[1], length - 1);

Which means that my TestData is one byte too long and should not include the Tx-Power. If I leave this byte out and pass a length of 19, no Fatal error occurs and the data is sent as should be. So apparently the es_slot_on-write does require a little different frame format as one (or at least I) would expect. For completeness the final (working) code:

static const uint8_t TestDataUid[19] = {
	APP_ES_UID_FRAME_TYPE,
	0x33, 0x33, 0x44, 0x44, 0x55, 0x55, 0x44, 0x44, 0x33, 0x33,		//10-byte UID namespace
	0x07, 0x07, 0x07, 0x07, 0x07, 0x07,								//6-byte UID ID
	0x00, 0x00
};

static void button_evt_handler(uint8_t pin_no, uint8_t button_action)
{
    if (button_action == APP_BUTTON_PUSH && pin_no == BUTTON_1) {
//        nrf_ble_es_on_start_connectable_advertising();
		es_slot_on_write(0, 19, TestDataUid);
    }
}

Hope this could help someone else. Regards