Working NRF9160 SD Card Example on SDK 1.9.0

[Jupyter1336]

First off, It's great you guys are setting a high pace with development and improving the SDK but I and I think many other people would like it if you change a full version of the SDK provide low-level examples, Like basic uart,spi,i2c, things that matter for most hardware developers. We currently have no reference again how with the changed infrastructure of 1.9.0 we can make certain peripherals work.

Now the problem at hand. I have tried to setup a SD card on the 1.9.0 SDK but have zero activity on Pins I have selected. I am using a custom board but for testing now I am using a devkit with the SPI pins one of the older devkits. To check if anything is happening on the SPI I/O I have attached a logic analyser but It shows zero action. If I am correct CS pin should at least be held high. I have added the current file I am using and I have referred to the following existing forum posts in hopes of getting anything out of the FAT FS example.

https://devzone.nordicsemi.com/f/nordic-q-a/84784/sample-fat_fs

https://devzone.nordicsemi.com/f/nordic-q-a/67320/unsupported-pin-error-when-using-pins-on-port-1-of-the-nrf52840dongle/275624#275624

https://devzone.nordicsemi.com/f/nordic-q-a/84784/sample-fat_fs/353427#353427

https://devzone.nordicsemi.com/f/nordic-q-a/75093/need-a-working-example-of-using-an-sd-card-with-fat-filesystem-on-the-nrf9160

I am also new to the whole VC environment maybe I am building it wrong that's why I also included the current version I build. sdcard.zip

[Øyvind]

Hello, 

provide low-level examples, Like basic uart,spi,i2c, things that matter for most hardware developers.

Thanks for your valuable feedback. There are many basic samples available in the Zephyr repo's samples and demos. 

Now the problem at hand. I have tried to setup a SD card on the 1.9.0 SDK but have zero activity on Pins I have selected.

Your .overlay file uses the incorrect build target, i.e. nrf9160dk_nrf9160ns.overlay should be nrf9160dk_nrf9160_ns.overlay. Can you please test and see if this helps?

Kind regards,
Øyvind

[Jupyter1336]

Øyvind said:

Thanks for your valuable feedback. There are many basic samples available in the Zephyr repo's samples and demos. 

They don't work without input and added changes made by programmers. You know that just as well as I do.

Øyvind said:

Your .overlay file uses the incorrect build target, i.e. nrf9160dk_nrf9160ns.overlay should be nrf9160dk_nrf9160_ns.overlay. Can you please test and see if this helps?

Yup that works, why the heck did the overlay naming change after 8 whole versions? These are the problems I was referring to how could I have known this? It builds, It compiles & It programs without error.

[Øyvind]

Jupyter1336 said:

why the heck did the overlay naming change after 8 whole versions?

From the release notes of nRF Connect SDK v1.7.0

• The nrf9160dk_nrf9160ns and the nrf5340dk_nrf5340_cpuappns boards have been renamed respectively to nrf9160dk_nrf9160_ns and nrf5340dk_nrf5340_cpuapp_ns, in a change inherited from upstream Zephyr.

Remember that our SDK is based on Zephyr and must comply with changes made upstream.

[Øyvind]

Please note that we have just released the Nordic Developer Academy, which can be a good starting point. 

[Jupyter1336]

You cant expect your programmers to read the whole of the release notes from the last version they worked on hoping they find their issue. Maybe add correct and fully working error checking/debugging.  Or include all files needed to program your devkits at the least from the Zephyr examples.