Hi Lm,
On Sun, Mar 26, 2017 at 07:45:37AM +0000, Lm Chew wrote:
> I also tried setting up a nrf52 DK with blehci app + BlueZ as explained in
> this tutorial(with a few changes).
>
> - http://mynewt.apache.org/latest/os/tutorials/blehci_project/
>
> - Use this to connect with btattach instead: sudo btattach -B /dev/ttyACM0 -S
> 1000000 -P h4
>
> - Skip the btmgmt step since in BlueZ 5.44 we no longer need to set the
> static-address manually and newtmgr will handle the rest.
>
> - Used the nrf52 DK onboard USB to UART bridge, did not use a FTDI USB TTL
> Serial Cable.
>
>
> But unfortunately I can't get it to work either, in fact it is one step
> backward.
When you use the USB virtual COM port on an nRF board, there are two
things you will want to do:
1. Disable mass storage device capability on your board (from JLinkExe):
MSDDisable
2. Reduce the BLE_ACL_BUF_SIZE setting to 128 (default=255) (in your
target's syscfg.yml file):
syscfg.vals:
BLE_ACL_BUF_SIZE: 128
Both of these changes prevent the virtual COM port's buffer from
overflowing.
For 1: nRF boards normally reserve a large portion of the buffer
for mass storage device functionality. By disabling this functionality,
the entire buffer is made available to UART opertaions.
For 2: The buffer can overflow if the host floods the controller with
large ACL data packets, especially at high baud rates. Reducing the
maximum transmission size down to 128 solved this problem for me.
I don't know if these will solve your problem, though. If you still
have issues, could you please send the entire btmon log?
Thanks,
Chris
