Community news, upcoming events and general discussions
Threads: 31 Posts: 81
Get technical support from the community
Threads: 1084 Posts: 5978
Threads: 16 Posts: 55
Tell us how to make XDK better!
Threads: 35 Posts: 117
Share and discuss community member projects
Threads: 49 Posts: 242
I am trying to run the DataLogger code provided by Bosch. I have updated it a little by removing lines that I don't intend to use. When I build the code, I get the following error:
C:\XDK-Workbench\XDK\make\mingw32-make.exe -C C:\XDK-Workbench\XDK\SDK/xdk110/Common -f application.mk debug new_bootloader mingw32-make: Entering directory 'C:/XDK-Workbench/XDK/SDK/xdk110/Common' mingw32-make: Leaving directory 'C:/XDK-Workbench/XDK/SDK/xdk110/Common' application.mk:390: *** multiple target patterns. Stop. Makefile:41: recipe for target 'debug' failed mingw32-make: *** [debug] Error 2
Can you please provide assistance? In addition, I also get the error "FR_OK could not be resolved." I have read through the previous threads on that and followed the instruction, however, had no success.
Just wanted to provide an update. I am still getting debug error but not the multiple target one. The descripition is below:
Assembling startup_efm32gg.S Creating .out C:/Users/siddh/XDK-Workspace/GestureRecognitionFinal/debug/GestureRecognitionFinal.out C:/Users/siddh/XDK-Workspace/GestureRecognitionFinal/debug/objects/GestureRecognitionFinal.o: In function `init': C:/Users/siddh/XDK-Workspace/GestureRecognitionFinal/source/GestureRecognitionFinal.c:235: undefined reference to `UINT8_c' collect2.exe: error: ld returned 1 exit status application.mk:391: recipe for target 'C:/Users/siddh/XDK-Workspace/GestureRecognitionFinal/debug/GestureRecognitionFinal.out' failed mingw32-make: *** [C:/Users/siddh/XDK-Workspace/GestureRecognitionFinal/debug/GestureRecognitionFinal.out] Error 1 mingw32-make: Leaving directory 'C:/XDK-Workbench/XDK/SDK/xdk110/Common' Makefile:41: recipe for target 'debug' failed mingw32-make: *** [debug] Error 2
Thank you for your response. I as able to resolve that error. However, the error "symbol 'FR_OK' could not be resolved " still persists. Can you please provide assistance with that?
Regarding the previous errors that I had mentioned, I made a silly mistake when I was including all the application source files, I am using, in the makefile. Basically, just syntax error; had forgotten to include "/". However, I did notice that cleaning and building the project over and over got rid of some errors automatically. I am not sure why is there such inconsistancy in the workbench.
I have followed these steps multiple times now but the error still persists. Is there any other solution availble?
In addtion, I get this following message when I flash the updated version of data logger code:
INFO | Connection to port 'COM5' established INFO | XDK DEVICE 1: config.bma280_enabled: 0 INFO | XDK DEVICE 1: config.bma280_bandwidth: 0 INFO | XDK DEVICE 1: config.bma280_range: 0 INFO | XDK DEVICE 1: config.bma280_sampling_rate_timer_ticks: 0 INFO | XDK DEVICE 1: config.bmg160_enabled: 0 INFO | XDK DEVICE 1: config.bmg160_bandwidth: 0 INFO | XDK DEVICE 1: config.bmg160_sampling_rate_timer_ticks: 0 INFO | XDK DEVICE 1: config.bmm150_enabled: 0 INFO | XDK DEVICE 1: config.bmm150_data_rate: 0 INFO | XDK DEVICE 1: config.bmm150_sampling_rate_timer_ticks: 0 INFO | XDK DEVICE 1: config.bme280_enabled: 0 INFO | XDK DEVICE 1: config.bme280_oversampling: 0 INFO | XDK DEVICE 1: config.bme280_filter_coefficient: 0 INFO | XDK DEVICE 1: config.bme280_sampling_rate_timer_ticks: 0 INFO | XDK DEVICE 1: bad filename in logger.ini
Can you please tell me why do I get bad filename in logger.ini?
// @suppress("Field cannot be resolved")
I am using 64-bit operating system with Windows 10 Home edition. Just fyi I have already followed the instructions to check for extensions and hidden files.
I am using the same format of the logger.ini file provided with the Data Logger example. However, I only need to record the data in json format so I have removed the part of the code corresponding to csv and custom from the example provided. The beginning part is as below:
[general] ; Specify filename in sprintf format filename=log-%04i.json ; Output file format: [csv, json, custom] fileformat=json ; Output data format: [raw, unit] dataformat=unit
I made the changes in a separate file. The original Data Logger demo is untouched. When I ran that, I got the same issue.
The data is being finally recorded. Thank a lot for your help!
I have another question. I would now like to send this saved file on SD card to the app via MQTT. What would you recommend for that?
So, for the user case, basically, I would like to be able control the XDK somehow from the app. For example, I should be able to send a message indiciating that I am interested in using, say, Acc and Gyro sensor, which then could be put into a format similar to the logger.ini file. Similarly, a message indicating that I want to conclude my session and de-initilaize the sesnors. All this happening over MQTT would be prefered. Please guide keeping this in mind.
In addition, I have been trying to test the provided example SendDataOverMqtt and get the following error:
INFO | XDK DEVICE 1: This is a CC3100R device INFO | XDK DEVICE 1: CHIP 0x4000000 INFO | XDK DEVICE 1: MAC 220.127.116.11.2 INFO | XDK DEVICE 1: PHY 18.104.22.168 INFO | XDK DEVICE 1: NWP 22.214.171.124 INFO | XDK DEVICE 1: ROM 0x3333 INFO | XDK DEVICE 1: HOST 126.96.36.199 INFO | XDK DEVICE 1: WLANPersonalWPA2Connect : Connecting to MARRS INFO | XDK DEVICE 1: WLANPersonalWPA2Connect : Error in WlanConnect_WPA INFO | XDK DEVICE 1: AppControllerEnable : Failed INFO | XDK DEVICE 1: Error in WLAN package. INFO | XDK DEVICE 1: Package ID: 10 Module ID: 2 Severity code: 2 Error code: 67 INFO | XDK DEVICE 1: asserted at Filename C:/Users/siddh/XDK-Workspace/SendDataOverMQTT/source/AppController.c , line no 419
Please provide assistance.