Issues with writing my own project that communicates with a computer over USB.

RE: Issues with writing my own project that communicates with a computer over USB.

ryerye120 — Thu, 26 Mar 2020 18:45:26 GMT

Yea, that gave me some other issues. Since I really only care about the bits, I've switched to calculating a 32 bit value from the rx_buff and outputting that. While this fixed some string related null character handling, I'm still outputting nothing over the LOG and the actual (expected) number over USB, so I wonder if there's an order of operations issue. I'll step through with the debugger.

Thanks for your help!

RE: Issues with writing my own project that communicates with a computer over USB.

Hung Bui — Tue, 24 Mar 2020 10:51:41 GMT

I don't think using the buffer as a string is a good idea here. A char array can be a string if the end of the array has a NULL character '/0' which you don't have.

To copy from one array to another array you can use memcpy instead.

What I can see is that your rx buffer is only 4 bytes, I dont know how you can get "comes_from_spi_mastr" as in the log.

Please get familiar with debugging, try to put a break point and view the buffer to see what you have there.

RE: Issues with writing my own project that communicates with a computer over USB.

ryerye120 — Mon, 23 Mar 2020 17:45:52 GMT

Hi Hung,

I've attached my main.c and sdkconfig.h. I'm using nRF5 SDK v16.0.0.

As fare as how data is being passed from the SPI to the USB, I'm just taking the SPI_rx buffer and sprintf-ing it into the USB_tx buffer (corresponding lines copied below):

        size_t size = sprintf(m_tx_buffer, "Hello USB CDC demo: %s\r\n", (uint32_t)spi_rx_buf);
        app_usbd_cdc_acm_write(&m_app_cdc_acm, m_tx_buffer, size);

devzone.nordicsemi.com/.../4532.main.c devzone.nordicsemi.com/.../6685.sdk_5F00_config.h

RE: Issues with writing my own project that communicates with a computer over USB.

Hung Bui — Mon, 23 Mar 2020 14:28:47 GMT

Hi,
Please post your code, and state which SDK you are using.
Please track down on how you pass the data from SPI to USB.

RE: Issues with writing my own project that communicates with a computer over USB.

ryerye120 — Fri, 20 Mar 2020 19:50:33 GMT

Okay, the problem was that I wasn't running app_usbd_event_queue_process() to actually process any USB events. I must have accidentally forgotten to copy it over. I have a new issue though.

I've set up two dev kits, a SPI master & a SPI slave. The Master sends a message "comes_from_spi_mstr" to the slave, which then pipes it to my desktop via USB. What's weird is that the message makes its way to my computer (I see "comes_from_spi_mstr" on computer from the USB's COM port)... but when I print the SPI's rx buffer through the logger it comes up empty.

Here are photos to show what's happening:

SPI logger output:

USB output:

Any idea why it's not coming up in the logger, despite being there (as shown by making its way all the way through the USB).

Thanks,

Ryan

RE: Issues with writing my own project that communicates with a computer over USB.

ryerye120 — Fri, 20 Mar 2020 17:50:37 GMT

I think it has to do with something in my sdk_config.h. I've removed most of the SPI code now. Aside from defining the SPI handler and enabling the SPI in the SDK_config, the SPI isn't doing anything (i.e. no SPI code in my main). I have the same issue.

I took a look at the properties tab and there are two events. I've copied both below:

The first one (Driver name is 'null' which seems like a problem. The drivers should be installed!):

Device USB\VID_1915&PID_520C\000000000000 was configured.

Driver Name: null
Class Guid: {00000000-0000-0000-0000-000000000000}
Driver Date: 
Driver Version: 
Driver Provider: 
Driver Section: 
Driver Rank: 0x0
Matching Device Id: 
Outranked Drivers: 
Device Updated: false
Parent Device: USB\VID_045E&PID_0944\6&15ba3093&0&1

The second one:

Device USB\VID_1915&PID_520C\000000000000 was not migrated due to partial or ambiguous match.

Last Device Instance Id: USB\VID_0403&PID_6010\003017A40B1B
Class Guid: {36fc9e60-c465-11cf-8056-444553540000}
Location Path: PCIROOT(0)#PCI(1400)#USBROOT(0)#USB(1)#USB(1)#USB(2)
Migration Rank: 0xF000FFFFFFFF0123
Present: false
Status: 0xC0000719

So it seems maybe I'm messing up some USB params in my sdk_config.h? I'll take a more extensive look through it right now.

RE: Issues with writing my own project that communicates with a computer over USB.

Hung Bui — Fri, 20 Mar 2020 13:25:40 GMT

Hi Rye,

Could you check what's the issue with the nRF52 USB Product (right click and click properties)
I would suggest to comment out the SPI functionality part by part until you see the USB work again, this way we can track down what caused the issue.