Hi, we switched from your competition to your platform. I know you wrote somewhere that you cannot provide examples for every sensor out there. But your Nordic Dev Zone is a bit messy, information cluttered everywhere. And soon, information is also outdated by your own updates.
If we would talk about motion sensors, I know there are like only two manufacturers: Invensense & Bosch.
Your competition has better community and also the owners themselves care more and provide basic examples on everything. I'm not asking you to do so. Just motion sensors, there is not many vendors and you have 50+ similar questions about motion sensors. It would be good, responsible, western EU style behavior, if your management would get some feedback from community managers. If so many people asking about issues or examples. You can have better ROI and save resources here, if you would, by all the years, provide some, even basic example. You have MPU in your documentation, but that does not stand for motion processing unit, it is some memory protection unit instead (only adds to confusion when googling).
We have met on CES at Las Vegas, you ask for some feedback, how to get better than competition. Your competition have better examples of how easy is to use their product. How good is time to market. Here I see only messy forum and customer rant about the same thing again & again and it is more than 1 year.
And before you will send here the unofficial Michael's github, I want to say that it was for SDK14. Not for SDK15. Next it does not use Invensense DMP driver.
I want to use eDMP motion driver by Invensense. Read quaternion (4D vector) and use their pipeline and configuration. Because, unlike Bosch with second ARM coprocessor, Invensense requires to load their driver in your firmware memory, in order to get these data. You can find many examples on Sparkfun, Adafruit, not to mention Arduino community itself. Also other ARM vendors provide at least one example.
I'm not asking you provide examples on every sensor out there. Just, when it comes to market share, there is only Invensense and Bosch with MPUs. That would be quite basic bluetooth beacon example in 2019.
So my question is: can I get SDK15 working with MPU9250 using DMP? On various boards including ESP, NXP, Arduino, it is really a matter of minutes and then companies, your customers, can focus on developing the product and time to market is acceptable. Here with Nordic, my experience so far, is that the community is not exchanging projects as it should and Nordic company is not doing anything to bring more customers on their platform. What took me one day on other platforms, is impossible to accomplis on SDK15.
I think it is start of 2019 and time to rethink this whole community / customer / startup / manufacturers strategy.
Reasons why this exists http://embeddedsoftdev.blogspot.com/2018/02/bluetooth-le-with-nordic-nrf51-nrf52.html The easy way!
Xin chào Hoang! Việt Nam Quê Hương Tôi :-D Do you have some link for Invensense with NRF52840?
Chao cyberluke, I have some that are still in the works. The MPU-9250 is end of life. The ICM-20948 is the replacement. They are not compatible so complete re-work is needed.
Ok, I'm looking into it. Looks quite complex. I like it is using Eclipse. Better than Segger Embedded Studio. I will try to run EHAL and hopefully there might be some collaboration from startup I'm working on now. We could help to update some parts. Yes, we should definitely switch to ICM-20948
Ok, I have fonctional code that are not yet pushed. I'll push them for you tonight. It is object oriented design. The driver is split into 2 part. Sensor is the low level sensor access (access, gyro, ...) and the Imu is the fusion part where you get the quat, euler, step,... Device access via I2C or SPI is fully functional.