USBD write

RE: USBD write

Regio — Tue, 06 Apr 2021 10:11:40 GMT

Hi Dmitry,

Thak you for your interest for my problem.

The problem was interrupts.

Best regards,

Regio

RE: USBD write

Regio — Mon, 05 Apr 2021 21:40:44 GMT

Hi Edvin,

I am grateful for your time.

The problem i solved was in iterruptions.

Best regards,

Regio

RE: USBD write

Regio — Thu, 01 Apr 2021 02:27:08 GMT

Hi Dmitry, thanks for the reply,

Yes you are right in the given code ret is missing, but in the app it is. I apologize. lost in rewriting.

Yes of course I check ret.

ret = 0 when making a write,

ret = 17 when busy, loading data from FDS

ret = 8 when PuTTy terminal is not available ... .

The logic of the code is simple after pressing the button the FDS output is activated.

My code is in draft. contains more alternatives. I'll make a simple version and send.

RE: USBD write

Regio — Thu, 01 Apr 2021 02:20:36 GMT

Hi Edvin, thanks for the reply,

Edvin's side:

what is sizeof(read_data) ini this case? Try printing it to the log. Is it the length that you expect it to be? What do you expect it to be, and what was it?

Yes it is exactly the length i expect.

Edvin side:

Also, you may want to look into the sprintf() call. Try debugging and see if m_tx_buffer[] is what you expect it to be after line 21 is executed (set a breakpoint on line 23).

Yes in m_tx_buffer [] is the expected value.

In another part of the code, I continuously read the values via BLE, app_usbd_cdc_acm_write works OK. Lists all values.

For FDS, only the last value. NRF_ERROR_BUSY reports when reading data from FDS.

RE: USBD write

Dmitry — Wed, 31 Mar 2021 16:41:46 GMT

I mean, if you're going to check the result of app_usbd_cdc_acm_write(), there should be an assignment:

ret = app_usbd_cdc_acm_write(...)

Also it's hard to understand the complete logic of your code by these snippets, please post the whole code relevant to USB handling (cut out any app logic if there's something confidential).

RE: USBD write

Regio — Wed, 31 Mar 2021 13:37:29 GMT

ret assigns 0

RE: USBD write

Regio — Wed, 31 Mar 2021 13:25:44 GMT

This is what I expect

app_usbd_cdc_acm_write(&m_app_cdc_acm,
                          m_tx_buffer,      
                              (12)+2);

RE: USBD write

Dmitry — Wed, 31 Mar 2021 12:59:47 GMT

if(ret == NRF_ERROR_BUSY)

where does your ret assigns something?

RE: USBD write

Regio — Wed, 31 Mar 2021 12:54:55 GMT

Hi Dmitry,

thank you for your response.

if(new_usb_packet > 0 && usb_busy == false)
	   {
		   sprintf(&m_tx_buffer[12], "\r\n");
          
       app_usbd_cdc_acm_write(&m_app_cdc_acm,
                                 m_tx_buffer,      
                    (sizeof(read_data)*2)+2);      
 					
		      if(ret == NRF_ERROR_BUSY)
		      {
		      NRF_LOG_INFO("usb_busy = true");
		      usb_busy = true;
		      }
		      else if(ret != NRF_SUCCESS)
		      {
		      NRF_LOG_INFO("USB ret != NRF_SUCCESS");
		      }
		      else
		      {
		      new_usb_packet--;
          }
      }

I've already done that and it didn't help to see the code

RE: USBD write

Edvin — Wed, 31 Mar 2021 12:38:32 GMT

          app_usbd_cdc_acm_write(&m_app_cdc_acm,
                                    m_tx_buffer,      
                       (sizeof(read_data)*2)+2);

what is sizeof(read_data) ini this case? Try printing it to the log. Is it the length that you expect it to be? What do you expect it to be, and what was it?

Also, you may want to look into the sprintf() call. Try debugging and see if m_tx_buffer[] is what you expect it to be after line 21 is executed (set a breakpoint on line 23).

Best regards,

Edvin

RE: USBD write

Dmitry — Wed, 31 Mar 2021 12:14:44 GMT

Hi,

app_usbd_cdc_acm_write() has no internal buffering, you should wait for APP_USBD_CDC_ACM_USER_EVT_TX_DONE event after sending an item.

RE: USBD write

Regio — Wed, 31 Mar 2021 11:48:43 GMT

app_usbd_cdc_acm_write from the sent code lists only the last item in the list. How to edit the code to list all items from the list?

RE: USBD write

Regio — Tue, 30 Mar 2021 14:46:47 GMT

HI Edvin,

Thank you for your response

The data in the FDS is read and displayed correctly.

NRF_LOG_INFO("Start searching... \r\n");
	
	while (fds_record_find(read_file_id, relevant_record_key, &record_desc, &ftok) == NRF_SUCCESS)
	{
		err_code = fds_record_open(&record_desc, &flash_record);
		if ( err_code != NRF_SUCCESS)
		{
			return err_code;		
		}
	
	  memcpy(read_data, flash_record.p_data, flash_record.p_header->length_words * sizeof(uint32_t));
	  NRF_LOG_HEXDUMP_INFO(read_data, sizeof(read_data));	

               for (int i = 0; i < 6 ; i++)       
               {
         
                sprintf(&m_tx_buffer[i*2], "%02x", read_data[i]);
        
               }

          sprintf(&m_tx_buffer[12], "\r\n");   

          app_usbd_cdc_acm_write(&m_app_cdc_acm,
                                    m_tx_buffer,      
                       (sizeof(read_data)*2)+2);     
            
      	  err_code = fds_record_close(&record_desc);
	      if (err_code != NRF_SUCCESS)
	      {
		return err_code;	
	      }
	}

RE: USBD write

Edvin — Tue, 30 Mar 2021 13:41:07 GMT

It is a bit difficult to say without knowing anything about your implementation of the fds or the usb. Perhaps you can share something?

Typical pitfalls:

FDS not done reading/writing before you use it. Wait for the callbacks.

How do you pass it to the usb?