NRF52833 USB HID KEYBOARD

RE: NRF52833 USB HID KEYBOARD

Hieu — Fri, 02 Aug 2024 05:59:17 GMT

No problem. I'm glad to hear you got it figured out. I just want to add that we recommend the nRF Connect SDK for all new projects. For further information, see: (+) nRF Connect SDK and nRF5 SDK statement - Blogs - Nordic Blog - Nordic DevZone (nordicsemi.com).

Otherwise, please feel free to close this case at your convenience.

RE: NRF52833 USB HID KEYBOARD

zbxiong — Fri, 02 Aug 2024 02:58:29 GMT

Hi Hieu

After tracing the above problems, it is found that when a key value error occurs, the pointer of the app_usbd_hid_generic_in_report_set(&m_app_hid_kbd,report,sizeof(report)) function points to a change in the report buffer address.

key_report is defined as static so that there are no key-value errors.

static report_keyboard_t key_report={0};

It was a small mistake that caused a lot of trouble.

Thank you for your reply.

RE: NRF52833 USB HID KEYBOARD

Hieu — Wed, 31 Jul 2024 17:34:01 GMT

Hi zbxiong,

What is the value of sizeof(*report) in your usb_kbd_keys_send() function? Depends on the organization of the code, it might not work like you think it would.

Another point to look out is check if your H key is properly debounced. You might want to check if your report queue is working correctly, see if the "3" and "E" coincide with when m_report_pending is set.

RE: NRF52833 USB HID KEYBOARD

zbxiong — Tue, 30 Jul 2024 01:24:41 GMT

Hi Hieu

thanks for your reply！

APP_USBD_CLASS_TYPEDEF(app_usbd_hid_generic, \
APP_USBD_HID_GENERIC_CONFIG(0, (NRF_DRV_USBD_EPIN1, NRF_DRV_USBD_EPOUT1)), \
APP_USBD_HID_GENERIC_INSTANCE_SPECIFIC_DEC, \
APP_USBD_HID_GENERIC_DATA_SPECIFIC_DEC \
);

void usb_kbd_keys_send(report_keyboard_t *report)  
{
    ret_code_t err_code;

    if (!NRF_USBD->ENABLE)
    {
        return;
    }
    if (!usb_started){
        return;
    }

    if(!kbd_report_queue_is_empty())
    {
        NRF_LOG_INFO("usb buffer in");
        memcpy(kbd_report_queue[kbd_report_queue_wp], report, KEYBOARD_REPORT_SIZE);
        kbd_report_queue_wp++;
        kbd_report_queue_wp %= KBD_REP_QUEUE_LEN;
        kbd_key_buffer_send();
        return;
    }
    if (m_report_pending)
    {
        NRF_LOG_INFO("usb buffer in");
        memcpy(kbd_report_queue[kbd_report_queue_wp], report, KEYBOARD_REPORT_SIZE);
        kbd_report_queue_wp++;
        kbd_report_queue_wp %= KBD_REP_QUEUE_LEN;
    }
    else
    {         
         
        err_code =app_usbd_hid_generic_in_report_set(    //app_usbd_hid_generic_in_report_set
               &m_app_hid_kbd,
               report,
               sizeof(*report)); 
                 
        if(err_code == NRF_SUCCESS)
            m_report_pending = true;  

        if(err_code == NRF_ERROR_BUSY){
            NRF_LOG_INFO("usb buffer in");
            memcpy(kbd_report_queue[kbd_report_queue_wp], report, KEYBOARD_REPORT_SIZE);
            kbd_report_queue_wp++;
            kbd_report_queue_wp %= KBD_REP_QUEUE_LEN;
        }
        else if(err_code == NRF_SUCCESS){
        m_report_pending = true;        
        }
        else{
           APP_ERROR_CHECK(err_code);
        }
    }
}

‘H’ is I pressed the key 50 times ‘3’ and ‘E’ are random displays.

RE: NRF52833 USB HID KEYBOARD

Hieu — Mon, 29 Jul 2024 15:02:35 GMT

Hi zbxiong,

usb_kbd_keys_send() is not a function in our SDK, so it is not possible for me to tell what is wrong here.

Please give me some more information about your implementation.

Also, please use the Insert > Code feature to send code snippets.

Hieu