Hi Chris, Thanks. I'm getting closer.
Using the 'LightBlue Explorer' app: - I can see the nimble-bleprh device - nim-bleprh appears to be advertising no services. - When I try and connect to the nRF52, the app times out. Below is what is output from the serial port during this exchange 13285:[ts=13285000ssb, mod=4 level=1] host_hci_data_rx(): handle=1 pb=2 len=7 data=0x03 0x00 0x04 0x00 0x02 0x9e 0x00 13293:[ts=13293000ssb, mod=4 level=1] host_hci_data_rx(): handle=1 pb=2 len=27 data=0x3b 0x00 0x3a 0x00 0x01 0x39 0x02 0x14 0x01 0x00 0x02 0x0f 0x63 0x6f 0x6d 0x2e 0x61 0x70 0x70 0x6c 0x65 0x2e 0x42 0x54 0x2e 0x54 0x53 13313:[ts=13313000ssb, mod=4 level=1] host_hci_data_rx(): handle=1 pb=1 len=27 data=0x01 0x22 0x02 0x00 0x01 0x1d 0x63 0x6f 0x6d 0x2e 0x61 0x70 0x70 0x6c 0x65 0x2e 0x42 0x54 0x4c 0x45 0x53 0x65 0x72 0x76 0x65 0x72 0x2e 13333:[ts=13333000ssb, mod=4 level=1] host_hci_data_rx(): handle=1 pb=1 len=9 data=0x63 0x6c 0x61 0x73 0x73 0x69 0x63 0x00 0x01 13345:[ts=13345000ssb, mod=4 level=1] host_hci_data_rx(): handle=1 pb=2 len=11 data=0x07 0x00 0x3a 0x00 0x09 0x05 0x01 0x00 0x00 0x00 0x00 28165:[ts=28165000ssb, mod=4 level=1] Disconnection Complete: status=0 handle=1 reason=19 - After I connect once, it takes a couple of minutes, before the nimble device will show up in my app, I thought it was supposed to be instant. Is this the expected behavior? Cheers James On Mon, May 16, 2016 at 3:21 PM, chris collins <[email protected]> wrote: > Hi James, > > Yes, there are two ways. The easier of the two is to use the "virtual COM > port" that is exposed via the USB port. The other way is to attach a three > wire serial cable to the appropriate pins on the nRF52. Either way, you > will need the FTDI driver on your machine and a terminal emulator that is > capable of attaching to a tty device (e.g., minicom or screen). If you are > using a mac, it should already come with the FTDI driver. There may be a > configuration step that I have forgotten about; please feel free to reply > back if you run into issues. > > On a mac, I attach to the virtual COM device as follows (I use the dterm > program, but the procedure should be the same with a different tool): > > dterm /dev/tty.usbmodem145121 115200 8 n 1 > > Alternatively, to connect to the 3-wire serial port, I would run dterm like > this: > > dterm /dev/tty.usbserial-A6009JND 115200 8 n 1 > > > There is one other means of debugging these issues: you can run the app in > gdb. To do this, use the "newt run" command: > > newt run perph 0 > > Chris > > > On Mon, May 16, 2016 at 3:10 PM, James Howarth <[email protected]> > wrote: > > > Hi Chris, > > Is there a way to hook up to the device while it is running to see the > > debug messages? So that I can diagnose some of these problems myself? > > CheersJames > > > > > > > > > > > > > > On Mon, May 16, 2016 at 12:38 PM -0700, "Christopher Collins" < > > [email protected]> wrote: > > > > > > > > > > > > > > > > > > > > > > Hi James, > > > > On Mon, May 16, 2016 at 10:49:10AM -0700, James Howarth wrote: > > > Hi, > > > > > > I am trying to get the bleprph example up and running on a Nordic nRF52 > > > PDK. But I can't seem to see the device using the LightBlue app > running > > on > > > my iPhone. > > [...] > > > > Hi James, > > > > I'm pretty sure I know what the problem is - the application task's > > stack is overflowing right out the gate. I'm afraid I have to take the > > blame for this one; the default logging settings use a lot of stack, and > > I don't often test with them. > > > > The fix is simple: increase the application stack size from 200 to 288 > > words. You can do this by changing apps/bleprph/src/main.c as follows: > > > > #define BLEPRPH_STACK_SIZE (OS_STACK_ALIGN(288)) > > > > This change has already been made to the development branch, but it > > didn't make it into the previous release. Using the develop branch > > instead of fixing the bug yourself is also an option; you can do so by > > changing your project.yml as follows: > > > > FROM: > > > > repository.apache-mynewt-core: > > type: github > > vers: 0-latest > > user: apache > > repo: incubator-mynewt-core > > > > TO: > > > > repository.apache-mynewt-core: > > type: github > > vers: 0-dev > > user: apache > > repo: incubator-mynewt-core > > > > (change the "vers" field). > > > > Then upgrade your packages with "newt upgrade", e.g., > > > > [ccollins@iori:~/tmp/myproj]$ newt upgrade > > apache-mynewt-core > > Would you like to upgrade repository apache-mynewt-core from > > 0.7.9-none to 0.0.0-none ? [Yn] y > > > > Naturally, this branch is quite unstable! > > > > Chris > > > > > > > > > > > > >
