SDK15 Invensense MPU9250

[cyberluke]

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.

[Jørgen Holmefjord]

Hi,

Thank you for your feedback, I will forward it to the relevant departments. 

In general, we get good feedback on the support we provide, and the information available in the community. If you have specific issues with integrating a driver with the SDK, we will help you as best we can. What we normally will not do is to fully integrate any driver with the SDK on request from a customer, without the customer doing any effort to do some work himself.

Like you say, Martin's examples on GitHub is written for SDK 14.2.0, but it should not be difficult to port these to run with SDK 15.2.0 (I have done this myself in the past).

The DPM driver is used in the Thingy:52 firmware, but this is based on SDK 13.0.0 (again, should not be difficult to port to SDK 15.2.0).

I would recommend that you post a new case with the specific issues you are facing by integrating the driver with SDK 15.2.0, and one of our application engineers will help you solve your issues.

Best regards,
Jørgen

[cyberluke]

Ok, code snippet inserted. Uploading image still not working. I'm on Google Chrome / Windows 10. I hit File Upload. Choose file (jpg screenshot) from my PC. It will not save it in the form and it automatically reopens Choose file window in infinite way. Looks like JavaScript issue on your website.

[Nguyen Hoan Hoang]

It's a lot simpler to develop custom Thingy firmware based on this Eclipse native project https://github.com/IOsonata/IOsonata/tree/master/ARM/Nordic/nRF52/nRF52832/exemples/BlueIOThingy/Eclipse  

[cyberluke]

Yes, after yesterday's pain I know. This was meant to be feedback for Nordic. Because I cannot imagine, some of their engineers study university, got bachelor or master degree. And then he setup one time example projects in Keil or Segger with 300 directories, one by one, mouseclicking. More professional approach would be to write some script that would scan directories and output these dependencies, which then can be copy-pasted to Keil or Segger. But as none of such scripts exists in NRF SDK. I was interested in official response, how they can create some project. Like they cannot compete even Arduino with this approach. It should be big feedback for them to change their mindset completely. Because next time, I don't want to get stuck with such company if this happens :-D

[cyberluke]

1. Included Eclipse BlueIOThingy project includes macros: NRF51, NRF SDK 12

2. Included Eclipse project, when imported, includes only one file BlueIOThingy.cpp. Others had to be added manually.

Oh, now I think I found the issue. During the import, there was a problem with several projects under the same name. Therefore it imported only nRF51. How to solve it?

3. Directive MPUxxxx required for Invensense libraries were missing. Had to add it in C compiler directives.

4. ../../../../../../../external/MPL/core/driver/include/mpu.h:22:2: error: '__u16' does not name a type; did you mean '._316'?
__u16 address;
^~~~~
._316

Additional info: nRF52840 does not have BlueIOThingy example. Only NRF52. So I will try to setup this one, instead of NRF51.

[cyberluke]

NRF52 project looks better. It uses external/NRF5_SDK folder instead of hardcoded NRF5_SDK_12. But now linker cannot find MPL libraries:

arm-none-eabi-g++ -mcpu=cortex-m4 -mthumb -Og -fmessage-length=0 -fsigned-char -ffunction-sections -fdata-sections -g3 -T "../src/gcc_nrf52_thingy_xxaa.ld" -Xlinker --gc-sections -L"../../../../../../../external/BSEC/algo/bin/Lite_version/gcc/Cortex_M4" -L"../../../../../../../external/MPL/lib/m4nfp" -L"C:/Users/Lukas/eclipse-workspace/SatinSensor/EHAL/ARM/Nordic/nRF52/exemples/BlueIOThingy/../../CMSIS/Debug" -L"C:/Users/Lukas/eclipse-workspace/SatinSensor/EHAL/ARM/Nordic/nRF52/exemples/BlueIOThingy/../../EHAL/Debug" -Wl,-Map,"BlueIOThingy.map" --specs=nano.specs --specs=rdimon.specs -Wl,--start-group -lgcc -lc -lm -lrdimon -Wl,--end-group -o "BlueIOThingy.elf" ./src/mllite/data_builder.o ./src/mllite/hal_outputs.o ./src/mllite/message_layer.o ./src/mllite/ml_math_func.o ./src/mllite/mlmath.o ./src/mllite/mpl.o ./src/mllite/results_holder.o ./src/mllite/start_manager.o ./src/mllite/storage_manager.o ./src/eMPL-hal/eMPL_outputs.o ./src/eMPL/inv_mpu.o ./src/eMPL/inv_mpu_dmp_motion_driver.o ./src/BlueIOTcs.o ./src/BlueIOTes.o ./src/BlueIOThingy.o ./src/BlueIOTms.o ./src/BlueIOTuis.o -lEHAL -llibmplmpu -lalgobsec
c:/program files (x86)/gnu tools arm embedded/8 2018-q4-major/bin/../lib/gcc/arm-none-eabi/8.2.1/../../../../arm-none-eabi/bin/ld.exe: cannot find -lEHAL
c:/program files (x86)/gnu tools arm embedded/8 2018-q4-major/bin/../lib/gcc/arm-none-eabi/8.2.1/../../../../arm-none-eabi/bin/ld.exe: cannot find -llibmplmpu

[cyberluke]

Oh, solved this. Did not know I have to open referenced project. Now ld.exe: cannot find -lCMSIS ...but I guess it will be similar solution like previous two.