Trying to see DongleBLE in linux with NCS

[Piwy]

Hello,

I want to see my dongle BLE with command lsusb with NCS. I succed to see it with a FTDI USB to UART but i want to succed with only USB.

I succed only USB just with the old SDK connectivity by using a patch whitch came from pc-ble-driver. I tried to developp a pc-ble-driver version NCS with shell command but for commercialisation i can't have a FTDI on my board. can you help me ?

I use for my tests a dongle BLE nrf52840.

Regards,

Pierre-Yves

[Piwy]

Hi,

I relance this post, i use the exact same board as descibed in this post but i have a bt840xe instead of nrf52840 and i'm not able to see the device in /dev//tty or with lsusb and i don't know why..

I'm always in wait the dtr with the bt840xe and not with the nrf52840

.

[Håkon Alseth]

Could you share details about your build:

1. What board are you building for?

2. Which example are you targeting?

3. Can you share the full log?

4. Does the bt840xe module have D+/D- routed to a new USB connector?

 

Kind regards,

Håkon

[Piwy]

1) Here is the board :

2) I use example thaét use shell module with usb, the project attach to this post

3) My full log :

00> [00:00:00.000,000] <dbg> usb_cdc_acm: cdc_acm_init: Device dev 0x65440 dev_data 0x20000bb4 cfg 0x200018b4 added to devlist 0x20005f50
00> [00:00:00.000,762] <dbg> usb_nrfx: usb_dc_ep_check_cap: ep 0x81, mps 16, type 3
00> [00:00:00.000,762] <dbg> usb_nrfx: usb_dc_ep_check_cap: ep 0x82, mps 64, type 2
00> [00:00:00.000,793] <dbg> usb_nrfx: usb_dc_ep_check_cap: ep 0x01, mps 64, type 2
00> *** Booting Zephyr OS build v3.0.99-ncs1  ***
00>
00>
00>  My_device_ID: ebd9c439fa33a65f
00>
00> [00:00:00.000,976] <dbg> usb_nrfx: usb_dc_ep_enable: EP enable: 0x00
00> [00:00:00.001,007] <dbg> usb_nrfx: usb_dc_ep_enable: EP enable: 0x80
00> Wait for dtr !
00>
I add all dbg that i could

4) i had the same board with nrf52840 and it's working very well , the only difference is that there is a bt840 xe instead

[Håkon Alseth]

Hi,

 

Piwy said:

00> Wait for dtr !

You will need to open the device (ie. the ttyACM device) for the firmware to continue after this.

Is there anything in dmesg that shows any issues or errors?

 

Kind regards,

Håkon

[Piwy]

there is nothing in dmesg that show the device, i can't see it with lsusb or in /dev/ also

[Håkon Alseth]

Have you ohmed the connection from the device USB connector to the D+/D- pins on the board itself? Could the cable be the problem?

 

Could you share the .hex file, so I can try to run it on a DK?

 

Kind regards,

Håkon

[Piwy]

Yes it's ohmed and the board is not connected with a cable but directly.

My project work well with the same board with nrf52840 instead of the bt840xe.

the hex file :

,2210.zephyr.hex

[Piwy]

i use this config, you have the DK to test it ?

# Disable DCDC and use 32k RC

CONFIG_BOARD_ENABLE_DCDC=n

CONFIG_BOARD_ENABLE_DCDC_HV=y

CONFIG_CLOCK_CONTROL_NRF_K32SRC_RC=y

# disable nrf5 bootloader

CONFIG_BOARD_HAS_NRF5_BOOTLOADER=n

[Håkon Alseth]

Piwy said:

Yes it's ohmed and the board is not connected with a cable but directly.

My project work well with the same board with nrf52840 instead of the bt840xe.

the hex file :

,2210.zephyr.hex

I tested this, and the USB enumerates as expected on a nRF52840-DK here:

[1729349.003717] usb 1-9: New USB device found, idVendor=1915, idProduct=c00a, bcdDevice= 3.00
[1729349.003721] usb 1-9: New USB device strings: Mfr=1, Product=2, SerialNumber=3
[1729349.003722] usb 1-9: Product: nRF52 Connectivity
[1729349.003724] usb 1-9: Manufacturer: Nordic Semiconductor
[1729349.003725] usb 1-9: SerialNumber: FE4BD24741C65D87
[1729349.009528] cdc_acm 1-9:1.0: ttyACM0: USB ACM device
[1729351.044419] usb 1-4: reset high-speed USB device number 4 using xhci_hcd

Opening the ttyACM interface shows this log:

[00:00:00.005,218] <dbg> usb_nrfx: usbd_work_process_pwr_events: USB Suspend state

[00:00:00.005,249] <dbg> usb_cdc_acm: cdc_acm_dev_status_cb: cfg 0x200018c4 status 5

[00:00:00.005,249] <inf> usb_cdc_acm: Device suspended


baud_rate = 115200


Wait for dtr !

--- 628 messages dropped ---
[00:00:00.147,888] <dbg> usb_nrfx: usbd_event_handler: RESUMING from suspend

[00:00:00.147,918] <dbg> usb_nrfx: usbd_work_handler: USBD reset event
...

 

Kind regards,

Håkon