• State Not Answered
  • Replies 6 replies
  • Subscribers 68 subscribers
  • Views 113 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 335875
Options

Thingy91 and buttons

fmfernandez

Hi! I'm using a Thingy91 and following the Nordic Academy course. The blinky example works fine, but when I try the second exercise, it seems like the buttons aren’t responding as expected. Since the Thingy91 has unique requirements, I’m compiling the code in VSCode and using nRF Connect to flash it. I’ve configured mcuboot according to the instructions on https://devzone.nordicsemi.com/guides/cellular-iot-guides/b/getting-started-cellular/posts/how-to-program-any-project-to-the-thingy-91-with-dfu and I’m uploading the app_signed.hex file. I’ve tried using button references from sw0 to sw3, but the output is always the same, no response.

Parents
  • 0

    If you are building with board target nrf9160dk_nrf9160_ns, then all the buttons and LEDs will point to the wrong place. You should build with the board target: thingy91/nrf9160/ns (or thingy91_nrf9160_ns if you are not using v2.7.0 or v2.8.0.)

    When you are building for the nrf9160dk_nrf9160_ns, none of the pins that are connected to buttons on the DK are connected to the GPIO that is connected to the button on the Thingy91.

    But as I mentioned, I really recommend that you get some sort of DK (development kit) instead of the Thingy for application development. It will be a lot easier for you to see the logs, debug and flash the applications.

    Best regards,

    Edvin

Reply
  • 0

    If you are building with board target nrf9160dk_nrf9160_ns, then all the buttons and LEDs will point to the wrong place. You should build with the board target: thingy91/nrf9160/ns (or thingy91_nrf9160_ns if you are not using v2.7.0 or v2.8.0.)

    When you are building for the nrf9160dk_nrf9160_ns, none of the pins that are connected to buttons on the DK are connected to the GPIO that is connected to the button on the Thingy91.

    But as I mentioned, I really recommend that you get some sort of DK (development kit) instead of the Thingy for application development. It will be a lot easier for you to see the logs, debug and flash the applications.

    Best regards,

    Edvin

Children
  • 0 in reply to Edvin

    Hi Edvin,

    Thank you! It seems I was working with an earlier SDK version that didn’t include the correct configuration for the Thingy91. After switching to the appropriate setup, everything is functioning as expected.

    As for the development kit suggestion, I understand its advantages. However, I’m specifically working with the Thingy91 because my focus is on IoT applications using cellular connectivity.

    Thank you again for your support!

    Best regards,
    Fátima

  • 0 in reply to fmfernandez

    I understand that it is nice with the sensors and all that, but the nRF91DK also has cellular connectivity, and it has a debugger making application development a lot easier. When you are done, you can port the application to run on the thingy instead. But that is just a suggestion Slight smile

    Best regards,

    Edvin

Related