Yes that did it. And it looks like that patch is upstreamed in there. Sadly looks like flash and ram grew a good bit and Im going to have to fight that for a while again.
On Tue, Dec 27, 2016 at 10:02 PM, Christopher Collins <[email protected]> wrote: > Hi Jacob, > > You will need to upgrade newt as well. You can do that as follows: > > cd $GOPATH && > git checkout develop && > git pull && > go install > > Hopefully that fixes the compile problem. Please report back if you > encounter any issues. > > Thanks, > Chris > > > On Tue, Dec 27, 2016 at 04:40:34PM -0700, Jacob Rosenthal wrote: > > Thanks for the quick replies. I changed to > > repository.apache-mynewt-core: > > type: github > > vers: 0-latest > > user: apache > > repo: incubator-mynewt-core > > > > Jacobs-MacBook-Air:mynewt-hr-observer jacobrosenthal$ newt run > > nrf51822xxaa_blecenthr 0.0.0 > > Compiling main.c > > Compiling misc.c > > Compiling peer.c > > Archiving blecenthr.a > > Error: In file included from aes.c:29:0: > > /Users/jacobrosenthal/Downloads/mynewt-hr-observer/ > repos/apache-mynewt-core/ > > crypto/mbedtls/include/mbedtls/config.h:2522:10: error: #include expects > > "FILENAME" or <FILENAME> > > #include MBEDTLS_USER_CONFIG_FILE > > > > > > Is upstream dev broken atm? or is there some quick config file fix? Or > > whats another quick way to move to something other than latest? Id just > > apply that one patch but looks like its based on a bunch of changes I > dont > > have in latest. > > > > > > Hrm.. also I cant find that in the github mirror.. It was closed there > not > > merged, does that mean it was merged somewhere on the apache side? > > > > @Andrzej Kaczmarek Ah, I see that error in the logs, though it looks like > > (this older) version of ble_gattc_disc_svc_by_uuid calls back (once) > > to BLE_HS_EDONE, > > even though the error exists. But who cares what this version does, out > > with the old. > > > > > > > > > > > > On Tue, Dec 27, 2016 at 3:28 PM, Christopher Collins < > [email protected]> > > wrote: > > > > > > > > Could you show the code you are using? I haven't noticed any issues > > > with the discover primary services by UUID operation. > > > > > > > 2357:[ts=18414036ss >
