• State Verified Answer
  • Replies 13 replies
  • Subscribers 63 subscribers
  • Views 6770 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 225507
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

Can't get logs to work and compile successfully.

cemerick

Been stuck for a few days on error related to logging. Have tried SDK 15.0 to 15.3 and get same error. Have deadline tomorrow and can't work on code. Ran out of ideas.  Seems to be related to macros expansion but not sure of anything anymore. Is Segger SES 4.12. 

Original problem occurred when I tried to enable logging. Logging had worked in the past so not sure what happened. Was stuck in cycle where when logging was enabled, during link phase there was an error that m_nrf_log_app_log_dataconst was not defined. Could not resolve that or find any reference to indicate a missing setting in sdk_config. So days later out of desperation i tried to define it to see if I would learn something else about the problem. All I learned is that you can waste a great deal of time chasing problems. Need help please. Have demo on Monday and just needed to add finishing touches to custom board that is doing active scanning of beacons and sending data via wifi soc to backend. Was needing logging to debug the wifi interface but have not added that code to the project yet. Using S132 and scan module only to gather the beacon info. Will be up in a few hours trying to complete this so I hope there is some guidance/wisdom when I wake up.

Parents
  • 0

    First, thanks for the feedback. I looked for an active beacon scanner example but did not find any. So I took a ble central example from the sdk and added the scanner module and bits and pieces from others. The scanner works fine and I could send the results I wanted out the usb serial to a pc to send over wifi for testing. I am using CMSIS when ever possible but find there is no sdk_config I ever found with all the options in the one sdk_config for reference. So just had to find bits and pieces and hope I found the right dependencies in the code. I ran the scanner code on the nrf52832 and nrf52840 DKs successfully before porting to the custom board. While I ran into some issues initially with getting the softdevice to enable, I use the logging to resolve those issues. I am using the HFFXO and the lfclock source is sythn. All that is working fine and I was getting a flood of clean data from the ~15 beacons sending advs every 200 ms. A ble dongle sniffer and wireshark trace indicated I was getting all the same advs and scan replies as seen by the ble sniffer and matched the expected amount for those beacons in a 10 second sample window accepting some collisisions. So very happy with that part. But something in the process of adding  code and testing sdk versions and trying to add an interface to a simplelink CC3100 soc trigger this loop of none-loggnig I can't seem to get out off. Was trying to determine if there was an optimal match of sdk version and softdevice for the nrf52832 (and later 840) that provided the fastest and most stable results. Should mention that somewhere in that process I discovered that the Segger SES was grabbing files between the versions. I caught that by looking at the SES project file and edited out those problems until there was no cross sdk issues. So many touches but valuable learning just not enough to resolve even after many hours of research.  

Reply
  • 0

    First, thanks for the feedback. I looked for an active beacon scanner example but did not find any. So I took a ble central example from the sdk and added the scanner module and bits and pieces from others. The scanner works fine and I could send the results I wanted out the usb serial to a pc to send over wifi for testing. I am using CMSIS when ever possible but find there is no sdk_config I ever found with all the options in the one sdk_config for reference. So just had to find bits and pieces and hope I found the right dependencies in the code. I ran the scanner code on the nrf52832 and nrf52840 DKs successfully before porting to the custom board. While I ran into some issues initially with getting the softdevice to enable, I use the logging to resolve those issues. I am using the HFFXO and the lfclock source is sythn. All that is working fine and I was getting a flood of clean data from the ~15 beacons sending advs every 200 ms. A ble dongle sniffer and wireshark trace indicated I was getting all the same advs and scan replies as seen by the ble sniffer and matched the expected amount for those beacons in a 10 second sample window accepting some collisisions. So very happy with that part. But something in the process of adding  code and testing sdk versions and trying to add an interface to a simplelink CC3100 soc trigger this loop of none-loggnig I can't seem to get out off. Was trying to determine if there was an optimal match of sdk version and softdevice for the nrf52832 (and later 840) that provided the fastest and most stable results. Should mention that somewhere in that process I discovered that the Segger SES was grabbing files between the versions. I caught that by looking at the SES project file and edited out those problems until there was no cross sdk issues. So many touches but valuable learning just not enough to resolve even after many hours of research.  

Children
No Data
Related