• State Verified Answer
  • Replies 17 replies
  • Subscribers 74 subscribers
  • Views 748 views
  • Users 0 members are here
Attachments (0)
Nordic Case Info
  • Case ID: 342320
Options

Adding SPI to a project

Tony

I am running VSCode with the latest nRF extension. I am on v2.9.1 of the SDK

I created a new app and copied the bluetooth_st_ble_sensor sample project.

I would like to add SPI to this project.

I don't know how.

I tried using KConfig GUI, but it doesn't come up. I have another ticket here for that one.

Parents Reply Children
  • 0 in reply to AHaug

    Hi again,

    ETA seems to be "in a few weeks", so hopefully it will be on the closer end of "few" than the farther end of "few"

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    Hopefully. I can use it sooner rather than later. I am right in the middle of trying to figure out how to add a custom driver. i am following the old version tutorial, but it isn't the same.

  • 0 in reply to AHaug

    I am working on this right now, so since there isn't a tutorial I will need some direct help.

    This is the directory structure in the old tutorial:

    I have my app in a new west workspace using 2.9.1. What is the directory structure in the new system?

    It then says to add a new zephyr,customer-bme280.yaml file with some information in it. Do I need the same file in the new system and where does it go?

    It then says to create a new folder in drivers/sensor called custom_bme280 and put the 3 files in it. Do I do that same thing and if so where do I create it and does it contain the exact same files with the exact same things as in the old tutorial?

    I could go on, but basically can someone go through the old tutorial and reply to this ticket with answers to if things stay the same or if they have changed and what those changes are.

    I am glad the new tutorial will be done in the next few weeks, but I am working on this today and am stuck until I have answers.

    If there is another resource that I could use to get these answers, just point the way...

  • 0 in reply to Tony

    Typically it looks like something like this:

    The biggest difference is that there are no child_image folder any more where you keep configurations for child images (such as MCUboot for instance). This is now located inside of the sysbuild folder instead, where you can either have an overlaying or overwriting approach of configuring companion components (the replacement terminology for child_images). https://academy.nordicsemi.com/courses/nrf-connect-sdk-intermediate/lessons/lesson-8-sysbuild/topic/sysbuild-explained/ goes through this and explains it very well (in my opinion atleast). 

    In addition you can have your board folder with <yourboard>.conf and <yourboard>.overlay, as previous and your drivers, dts and includes should be the same as far as I can see.

    Let me know if the sysbuild lesson allows you to get some further insight and confidence towards the implementation and if you have any follow ups I will revisit the topic and this case early next week

    Kind regards,
    Andreas

  • 0 in reply to AHaug

    I created this application using the "copy a sample" option in VSCode. It doesn't have a sysbuild.conf or sysbuild folder. The sample I copied was the Bluetooth Peripheral sample.

    Is that an issue?

    Can I add a custom driver to an application copied from that sample. If so, what are the details of doing that?

    I will do that tutorial on sysbuild as an additional thing so I understand sysbuild better as well.

Related
Terms of service