nrf9160 using pin 29 as spi chip select

RE: nrf9160 using pin 29 as spi chip select

Mike Jongen — Mon, 18 Jan 2021 13:54:14 GMT

No, it is a standard spi nor flash, and doesn't require a specific driver. I just needed to set SPI_NOR.

This is the final conf:

CONFIG_STDOUT_CONSOLE=y
CONFIG_SPI=y
CONFIG_SPI_NOR=y
CONFIG_FLASH=y

# enable printing
CONFIG_SERIAL=y
CONFIG_PRINTK=y
CONFIG_CONSOLE=y
CONFIG_STDOUT_CONSOLE=y

# Enable log
CONFIG_LOG=y

# Enable rtt
CONFIG_USE_SEGGER_RTT=y

# Enable rtt shell
CONFIG_SHELL=y
CONFIG_SHELL_BACKEND_RTT=y

# Switch console to rtt, for print statements
CONFIG_UART_CONSOLE=n
CONFIG_RTT_CONSOLE=y

The flash example now works, thanks for the help!

RE: nrf9160 using pin 29 as spi chip select

Øyvind — Mon, 18 Jan 2021 10:21:32 GMT

[quote user="Mike Jongen"]Small note, I had to use ${CMAKE_CURRENT_LIST_DIR} instead of $(CMAKE_CURRENT_LIST_DIR), in case anyone has issues with the CMake.[/quote]

Thanks for the note! That's one detail that went right past me in my last reply.

[quote user="Mike Jongen"]The flash example still gives the same output, so I'll have to see if something else is wrong. [/quote]

Assuming you mean it prints the output "SPI flash driver S25FL128L was not found!"? Or do you mean the output on pin 29?

Have you actually added the drivers for this device? I am not able to find this device in Zephyr

RE: nrf9160 using pin 29 as spi chip select

Mike Jongen — Fri, 15 Jan 2021 12:13:58 GMT

Thank you, I am now able to control the pins as gpio. The flash example still gives the same output, so I'll have to see if something else is wrong.

Small note, I had to use ${CMAKE_CURRENT_LIST_DIR} instead of $(CMAKE_CURRENT_LIST_DIR), in case anyone has issues with the CMake.

RE: nrf9160 using pin 29 as spi chip select

Øyvind — Fri, 15 Jan 2021 07:48:44 GMT

Can you try this instead:

cmake_minimum_required(VERSION 3.13.1)

set(spm_CONF_FILE
    prj.conf
    $(CMAKE_CURRENT_LIST_DIR)/spm.conf
    )
    
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
project(spi_flash)

FILE(GLOB app_sources src/*.c)
target_sources(app PRIVATE ${app_sources})

RE: nrf9160 using pin 29 as spi chip select

Mike Jongen — Thu, 14 Jan 2021 12:56:53 GMT

I have tried the solution without success.

My CMakeLists.txt is now:

cmake_minimum_required(VERSION 3.13.1)
find_package(Zephyr REQUIRED HINTS $ENV{ZEPHYR_BASE})
project(spi_flash)

set(spm_CONF_FILE
    prj.conf
    $(CMAKE_CURRENT_LIST_DIR)/spm.conf
    )

FILE(GLOB app_sources src/*.c)
target_sources(app PRIVATE ${app_sources})

spm.conf is:

CONFIG_SERIAL=n
CONFIG_STDOUT_CONSOLE=n
CONFIG_LOG=n
CONFIG_BOOT_BANNER=n
CONFIG_PRINTK=n

CONFIG_SPM_BOOT_SILENTLY=y

This is the waveform that is send over pin 29 at startup:

devzone.nordicsemi.com/.../pin_5F00_29_5F00_waveform.zip

I have tried the flash example, and tried to toggle pin 29 as gpio. both failed.

RE: nrf9160 using pin 29 as spi chip select

Øyvind — Wed, 13 Jan 2021 09:28:21 GMT

You were right, this is the SPM causing issues on UART0.

Have a look at this solution:
https://devzone.nordicsemi.com/f/nordic-q-a/55667/nrf9160-disable-bootloader-and-spm-uart-console-print

RE: nrf9160 using pin 29 as spi chip select

Mike Jongen — Tue, 12 Jan 2021 16:32:32 GMT

Here is the zephyr.dts:
devzone.nordicsemi.com/.../zephyr.dts

The board is a custom board.

RE: nrf9160 using pin 29 as spi chip select

Øyvind — Tue, 12 Jan 2021 13:58:55 GMT

Thanks for updating with that information. The overlay file looks good. I agree that it seems that pin 29 might be configured to something else. Can you provide zephyr.dts from the build folder? Are you running a custom board, or the nRF9160 DK or Thingy:91?

-Øyvind

RE: nrf9160 using pin 29 as spi chip select

Mike Jongen — Tue, 12 Jan 2021 12:52:36 GMT

Yes, see line 7 of the overlay I have included.

RE: nrf9160 using pin 29 as spi chip select

Øyvind — Tue, 12 Jan 2021 11:10:01 GMT

Hi,

Have you configured the CS pin in your overlay file?

Kind regards,
Øyvind