• State Verified Answer
  • Replies 5 replies
  • Subscribers 86 subscribers
  • Views 1292 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 274504
Options
This post is older than 2 years and might not be relevant anymore
More Info: Consider searching for newer posts

unexpected behavior of the example project's code after I commenting one line, build project, and then uncommenting it again

SergeiAseev

Hi, I have a bit strange problems with example project "pwm_library". At first I compiled with segger embedded studio and ran the project on my NRF52-DK board, and it worked fine. Then i commented the line "#include "app_pwm.h"" just for the heck of it, to see what can happen, and tried to build the project. Obviously it failed. But then I uncommented the "#include "app_pwm.h"" line to restore my project and expected to see right behavior of the code. And it was completely unexpected, I got the same list of errors as before. Could you please tell me, what had happened to code, and how can I restore this example code. Thanks ahead.

Parents
  • 0

    Hi

    I just tested this on my end, and I'm not able to reproduce it here on my end. Can you provide details on what versions of SES and J-Link drivers you have on your computer? Also, if you open the nRF_Libraries folder in SES, you should see a file called app_pwm.c, and under it a folder of Dependencies and one for Output files. Can you confirm whether that's the case or not?

    Best regards,

    Simon

  • 0 in reply to Simonr

    Hey! thanx a lot for your post. I really appreciate it. I'm afraid, that situation is hopeless. But, I guess I partly understood what's happened to my code.
    The thing is that before I started to explore the "PWM library" example in such a way I explained above,
    I had been trying to combine two examples of SDK (SDK 17 and SES for ARM 4.12 by the way) "BLE_UART" and "PWM library".
    And, to be honest, I completely muddled up about all this stuff.
    That's why I decided to go back to the "PWM library" example" to try to understand what components of the project need to be added to the "BLE_UART" project to make it work together with "PWM library".
    But when I rebuilt my "PWM library" example project, it got previously corrupted shared files from SDK. I think it's too complicated for me to realize what exactly was broken.
    So, I ended up taking a new copy of the SDK and tried to combine these two examples again using all the new information I got surfacing the internet, and now this combination works well.
    I believe my first mistake was that I paid little attention to the configuration file, and then started to make stupid BS.
    I should've reported this earlier so as not to waste your time.

Reply
  • 0 in reply to Simonr

    Hey! thanx a lot for your post. I really appreciate it. I'm afraid, that situation is hopeless. But, I guess I partly understood what's happened to my code.
    The thing is that before I started to explore the "PWM library" example in such a way I explained above,
    I had been trying to combine two examples of SDK (SDK 17 and SES for ARM 4.12 by the way) "BLE_UART" and "PWM library".
    And, to be honest, I completely muddled up about all this stuff.
    That's why I decided to go back to the "PWM library" example" to try to understand what components of the project need to be added to the "BLE_UART" project to make it work together with "PWM library".
    But when I rebuilt my "PWM library" example project, it got previously corrupted shared files from SDK. I think it's too complicated for me to realize what exactly was broken.
    So, I ended up taking a new copy of the SDK and tried to combine these two examples again using all the new information I got surfacing the internet, and now this combination works well.
    I believe my first mistake was that I paid little attention to the configuration file, and then started to make stupid BS.
    I should've reported this earlier so as not to waste your time.

Children
Related
Terms of service