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
i need to have an access to file descriptor to send command
I will try to describe the best that i can.
As i say, there isn't log in my issue...
Firt of all, I experimented a custom board nrf52840 with a FT232 Bridge USB to UART. My firware use Bluetooth Shell commands and others shell commands. This device will be used as a central. I succed to use this device with a raspberry pi and to command it with an external program in my rasspberry ( using sockets).
I use a modified version of bluetooth shell. I comunicateed with this board with Uart.
I succed to connect with putty in windows and with minicom in linux.
But this was just an experimentation, now i need to custom board without the FT232 bridge, i need to use only USB. We create another custom card based on the Dongle BLE and i try to do the same as before with the USB.
The custom board is powered by the usb , the old custom boad with FT232 was powered by a battery.
I do all this thing to have a pc-ble-driver's like with NCS. It's even better because i can customise shell commands and use more functionnalities.
I provided you also my prj.conf and my main.c.
After i first try to add usb enable by using cdc_acm sample in my software. And I try to use it with dongle BLE from nordic. As i said before, it was a succes. But not with my custom board. The HW is really the same as the Dongle BLE. the only difference beetween them is the bootloader that's all and i don't understand why this isn't working
I will try to describe the best that i can.
As i say, there isn't log in my issue...
Firt of all, I experimented a custom board nrf52840 with a FT232 Bridge USB to UART. My firware use Bluetooth Shell commands and others shell commands. This device will be used as a central. I succed to use this device with a raspberry pi and to command it with an external program in my rasspberry ( using sockets).
I use a modified version of bluetooth shell. I comunicateed with this board with Uart.
I succed to connect with putty in windows and with minicom in linux.
But this was just an experimentation, now i need to custom board without the FT232 bridge, i need to use only USB. We create another custom card based on the Dongle BLE and i try to do the same as before with the USB.
The custom board is powered by the usb , the old custom boad with FT232 was powered by a battery.
I do all this thing to have a pc-ble-driver's like with NCS. It's even better because i can customise shell commands and use more functionnalities.
I provided you also my prj.conf and my main.c.
After i first try to add usb enable by using cdc_acm sample in my software. And I try to use it with dongle BLE from nordic. As i said before, it was a succes. But not with my custom board. The HW is really the same as the Dongle BLE. the only difference beetween them is the bootloader that's all and i don't understand why this isn't working
Hi,
I understand that you want this to enumerate in your operating system as a COM port device, ie. a cdc_acm device.
When firmware is the problematic component, you need to focus on that.
What you need to do is to enter debug mode on your device, and see where it gets stuck. Similarly, if you do not have a uart pinout, you can use RTT to see what the log output is.
Piwy said:I provided you also my prj.conf and my main.c.
Always share your full project, not only two files.
If your firmware worked before when transmitting shell over uart, and the only change that you did was the kconfig and device-tree overlay as I described in this answer:
RE: Trying to see DongleBLE in linux with NCS
Then it will route your shell to use USB instead of UART. You can try to add this to for instance the shell_module sample in zephyr (../ncs/zephyr/samples/subsys/shell/shell_module)
Kind regards,
Håkon
I tried to use debug RTT but when i put my fireware in my custom device i can't connect to it after that unfortunatly.... that's why i can't have log output.
Now i will only use the shell module from Zephyr. I build it with overlay-usb.conf and i have always the same issue, when i put the software in dongle_ble nordic=> no issue, this work.
But not in my custom device..., there is a difference beetween them and it's not hw
Hi,
Piwy said:Now i will only use the shell module from Zephyr. I build it with overlay-usb.conf and i have always the same issue, when i put the software in dongle_ble nordic=> no issue, this work.
What do you mean by "no issue, this works"? Please share logs or similar showing the working behavior.
Piwy said:But not in my custom device..., there is a difference beetween them and it's not hw
As previously mentioned, you must configure a project for a nRF52840 custom device without DFU, and this is done by adding:
CONFIG_BOARD_HAS_NRF5_BOOTLOADER=n
Since you can program a device, you shall also be able to debug it with VSCode, have you tried this?
Could you share the schematic of your custom device?
Kind regards,
Håkon
