• State Verified Answer
  • Replies 20 replies
  • Subscribers 74 subscribers
  • Views 4526 views
  • Users 0 members are here
Attachments (1) Download All
Nordic Case Info
  • Case ID: 284894
Options

Connecting ds18b20 to nrf9160dk

nrffan18

Hi, 

I am looking to connect the ds18b20 sensor to the nrf9160dk. I followed this post, but when I tried running it, I was getting a "create_nordic_project.py failed (1)" saying "error: cmake failed". 

I am a complete beginner when using the development kit so please bear with my questions. 

I have added "CONFIG_GPIO" in the prj.conf file, is there anything else I should be adding. 

Additionally, should I be making changes to the cmake file? The link above only mentioned the .c and .h file so I wasn't sure what else should be changed. 

If anyone could help me with this or could point me to resources that will help me solve this, I would really appreciate it. 

Update : The code is now running without any build errors but not printing any values. I had been using the hello_world sample to run it before which was giving the error, but then I tried switching to the blinky sample and running on that and it's building and running without any errors. (Would anybody know why this is).

My issue now is that it is not printing any values or anything to the Debug terminal on SES or the LTE Link Monitor. Does anyone know why this may be?

Parents
  • 0

    Hello Nandini,

    nrffan18 said:

    So now I know why it was sending me wrong values but I have no idea how to fix it. Can anyone please provide some guidance on what I can do to make the delays in my code execute more accurately without so much delay in switching between setting the pin High/Low?

    Is the issue that the clock is too slow? Or is there something else I should be doing?

    Here are my suggestions:

    • Debug through the driver layer of your code and see if you can find something suspicious. For this, I recommend you to use nRF Connect for VS Code.
    • Use the blinky sample as reference and connect the probe to the pin controlling the LED. Do you see the same delay there?

    Regards,

    Markus

  • 0 in reply to Albrecht Markus Schellenberger

    Hi , 

    I tried running the blinky code that access info directly from the devicetree while placing a 2000us delay after setting on and a 1000 us delay after setting it off. When doing the delay in ms, there is not much delay, but when doing in us, there is a delay of 50 us when going high, and 100 us when going low. 

    I also noticed that the delay increases when I increase the clock speed to 25 kHz. Do you know why that is? And I also noticed that it briefly goes low when its high sometimes. (3rd screenshot below) Does anyone know why that is too?

    I also didn't notice anything weird when I debugged through the code. 

    I am approaching my deadline for my project really soon so any help would be really appreciated. Thank you!

Reply
  • 0 in reply to Albrecht Markus Schellenberger

    Hi , 

    I tried running the blinky code that access info directly from the devicetree while placing a 2000us delay after setting on and a 1000 us delay after setting it off. When doing the delay in ms, there is not much delay, but when doing in us, there is a delay of 50 us when going high, and 100 us when going low. 

    I also noticed that the delay increases when I increase the clock speed to 25 kHz. Do you know why that is? And I also noticed that it briefly goes low when its high sometimes. (3rd screenshot below) Does anyone know why that is too?

    I also didn't notice anything weird when I debugged through the code. 

    I am approaching my deadline for my project really soon so any help would be really appreciated. Thank you!

Children
No Data
Related
Terms of service