Thanks for all of the suggestions, everyone. I tried bleprph and that works fine. I wasn’t committed to bletiny, it, well, just sounded tiny. :)
As for what I’d like to do with the stack, I’d like to port it to a research OS I’m working on, called Tock, which we’re actively working on nRF51822 support for: https://github.com/helena-project/tock The core kernel of Tock is in Rust, so I’ll need to break the stack into a kernel portion (port to Rust) and a process (which can be in C). Phil > On Jul 13, 2016, at 1:34 PM, Christopher Collins <[email protected]> wrote: > > Hi Philip, > > On Wed, Jul 13, 2016 at 12:56:19PM -0700, Philip Levis wrote: >> First off, I’m super excited about mynewt: an open-source BLE stack is >> tremendously valuable. Great work! > > Good to hear! > >> But I’ve run into a problem: I’m trying to get started and build >> bletiny for the nrf51dk. When it links bletiny.elf, it says that .text >> won’t fit in FLASH, it’s overflowing by 2392 bytes. So two questions: > > It's a tight fit, but the nRF51dk should be able to accommodate bletiny. > Are you using Mynewt 0.9.0? > > Here are a few things to check: > > * Make sure your target is configured to use the "optimized" build > profile; "debug" is too large. > > * Have you enabled any additional logging or other debug features in > your build target (e.g., by setting the LOG_LEVEL symbol)? > > If these suggestions don't solve your problem, could you please send > the output of "newt target show" to the list? > > Thanks, > Chris
