We really want to work with Nordic, but they makes it hard.

[Bndit]

It seems like a really great company, but after exploring and asking , and searching for a good BLE solution, I just can't find a good fit.

So you want a GOOD processor, and BLE . If you go with the nrf8001 and external MCU you get a pretty old BLE solution, nobody knows if its going to be here next year, AND it requires so many components around it including 2 crystals, which summed up to a price of a BLE module ( around 6$)

If you go with the more advanced solutions such as nrf51 series, you find out that the processors are just there to say : hey we have an ARM inside.

1. No DAC option ( any new ARM has it)
2. No RTC
3. No flash emulator to save stuff between resets / eeprom.

and the list is pretty long, and thats not including long development time.

This is not a rant, quite the opposite, it seems like a great company (and its not from China/ Thailand or whatever) , but every solution you check has at least 1 huge drawback .

Am I completely wrong here ?

[endnode]

Your summary for nRF51 seems to be inaccurate, can you elaborate with some examples what you lack in points 1/2/3 and which competition can offer it? Chip has many HW peripherals, has RTC and TIMER (several of them) and has 256kB of flash. Also why you don't consider nRF52 which is more power effective, has more flash/RAM/peripherals and cost difference is small? To be honest I haven't met better low-power Bluetooth processor on the market, can you hint what can give you more then nRF52?

[Bndit]

Thank you, maybe I am really wrong here. Any new ARM processor has DAC, and really advanced PWM options(not just frq and d.c but phase control and more) , check the SAMD21, a popular one, or any STM, they all have built in DAC, touch processors, full RTC with real dates, and much more options when it comes it I/O . Memory is not the issue, its about what it can do and the supported libraries. How is the new series solves these problems?